lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billy Morgan (JIRA)" <>
Subject [jira] Commented: (SOLR-1703) Sorting by function problems on multicore (more than one core)
Date Thu, 15 Apr 2010 22:12:48 GMT


Billy Morgan commented on SOLR-1703:

I believe this to be the cause of the problem I  am experiencing..

I start tomcat and everything works as normal. I then trigger a process which updates our
synonym files and tells each of the cores affected to reload to pickup the changes. Once reloaded
the fields used by the sort functions can no longer be found.

Restarting tomcat fixes the problem but isn't an option on our production servers. Any idea
when this bug will be ironed out or a possible work around for my situation in the meantime?

> Sorting by function problems on multicore (more than one core)
> --------------------------------------------------------------
>                 Key: SOLR-1703
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: multicore, search
>    Affects Versions: 1.5
>         Environment: Linux (debian, ubuntu), 64bits
>            Reporter: Rafał Kuć
> When using sort by function (for example dist function) with multicore with more than
one core (on multicore with one core, ie. the example deployment the problem doesn`t exist)
there is a problem with not using the right schema. I think there is a problem with this portion
of code:
> {code}
> public static FunctionQuery parseFunction(String func, IndexSchema schema) throws ParseException
>     SolrCore core = SolrCore.getSolrCore();
>     return (FunctionQuery) (QParser.getParser(func, "func", new LocalSolrQueryRequest(core,
new HashMap())).parse());
>     // return new FunctionQuery(parseValSource(new StrParser(func), schema));
> }
> {code}
> Code above uses deprecated method to get the core sometimes getting the wrong core effecting
in impossibility to find the right fields in index. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message