[
https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-6342.
----------------------------
Resolution: Fixed
Fix Version/s: 4.10
5.0
Assignee: Steve Rowe
Committed on sarowe's behalf per IRC disucssion.
Committed revision 1618281.
Committed revision 1618284.
also spun off an idea he had for an improvement that came up during my testing:
SOLR-6384
> Solr should mention CHANGES from Lucene which have side effects in Solr
> -----------------------------------------------------------------------
>
> Key: SOLR-6342
> URL: https://issues.apache.org/jira/browse/SOLR-6342
> Project: Solr
> Issue Type: Bug
> Reporter: Varun Thacker
> Assignee: Steve Rowe
> Fix For: 5.0, 4.10
>
> Attachments: SOLR-6342.patch, SOLR-6342.patch
>
>
> This is the problem that I faced - A user upgraded Solr from 4.0 to 4.9 and
> the queries being formed were behaving differently.
> I tracked it down to LUCENE-5180 ( which I believe is the correct thing to do
> ) . The problem is since Solr does't ship with the Lucene CHANGES.txt file
> and we didn't record this under the the Solr CHANGES.txt file also, a user is
> not aware of such changes when upgrading.
> I can think of two options -
> 1. Duplicate the changes which have side effects in Solr under Solr's
> CHANGES.txt file also ( not sure if we do this already and that we missed
> this one ).
> 2. Be conservative and ship Solr binaries with the Lucene CHANGES.txt file
> also
> We should address this problem
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
