[
https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14099185#comment-14099185
]
ASF subversion and git services commented on SOLR-6342:
-------------------------------------------------------
Commit 1618281 from [email protected] in branch 'dev/trunk'
[ https://svn.apache.org/r1618281 ]
SOLR-6342: build.xml clones lucene/CHANGES.txt as LUCENE_CHANGES.txt in solr
releases; changes2html hotlinks LUCENE_CHANGES.txt when found
> 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
> 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]
