[
https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092497#comment-14092497
]
Varun Thacker commented on SOLR-6342:
-------------------------------------
Slightly unrelated but maybe we could also fix the problem pointed out by
[~andyetitmoves] here -
http://mail-archives.apache.org/mod_mbox/lucene-dev/201401.mbox/%3ccadmuoewdzjg3bke3m_2fxtkvha3ua_6kjy_isjt9wxv3ixy...@mail.gmail.com%3E
> 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
>
> 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]
