lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Hatcher (JIRA)" <>
Subject [jira] [Commented] (SOLR-3648) The "/browse" Solritas GUI does not work under SolrCloud - 500 error
Date Sat, 28 Jul 2012 22:32:34 GMT


Erik Hatcher commented on SOLR-3648:

TODO: update VelocityResponseWriter wiki (it needs a cleanup anyway) with pertinent details.

What else do you think should be done here, Jan?  The one thing I didn't incorporate from
your patch was the "path" parameter to the SolrVelocityResourceLoader (but rather hardcoded
it), mainly for simplicity.  I don't think that multiple "path"'s capability should be done
that way here.  Either your way or my way here is a change in how it was done before by requiring
it look in a velocity/ sub"directory".  I doubt anyone has used it the way I was intending
it to be used, so not a big deal to break it I don't think.  My thinking with that, thankfully
quite useful in SolrCloud mode resource loader, was that plugins/contrib modules could ship
their own Velocity templates in their JAR files.  Anyone using it that way will now have to
put the templates in a velocity/ subdirectory inside the JAR.
> The "/browse" Solritas GUI does not work under SolrCloud - 500 error
> --------------------------------------------------------------------
>                 Key: SOLR-3648
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 4.0-ALPHA
>         Environment: RHEL 5.4, SolrCloud
>            Reporter: Nick Cotton
>            Assignee: Jan H√łydahl
>            Priority: Blocker
>              Labels: patch
>             Fix For: 4.0, 5.0
>         Attachments: SOLR-3648.patch, SOLR-3648.patch
> When run in a SolrCloud configuration the Velocity searchHandler responds to a /browse
request with an HTTP error 500 and a stack trace indicating
> ZkSolrResourceLoader does not support getConfigDir() 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message