[jira] [Commented] (SOLR-6342) Solr should mention CHANGES from Lucene which have side effects in Solr
[ https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099185#comment-14099185 ] ASF subversion and git services commented on SOLR-6342: --- Commit 1618281 from hoss...@apache.org 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6342) Solr should mention CHANGES from Lucene which have side effects in Solr
[ https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14099212#comment-14099212 ] ASF subversion and git services commented on SOLR-6342: --- Commit 1618284 from hoss...@apache.org in branch 'dev/branches/branch_4x' [ https://svn.apache.org/r1618284 ] SOLR-6342: build.xml clones lucene/CHANGES.txt as LUCENE_CHANGES.txt in solr releases; changes2html hotlinks LUCENE_CHANGES.txt when found (merge r1618281) 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6342) Solr should mention CHANGES from Lucene which have side effects in Solr
[ https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6342) Solr should mention CHANGES from Lucene which have side effects in Solr
[ https://issues.apache.org/jira/browse/SOLR-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14091461#comment-14091461 ] Hoss Man commented on SOLR-6342: I'm so use to dealing with source releases, it didn't even occur to me until now that the binary releases wouldn't include the Lucene CHANGES.txt file -- but given the package structure of course that makes sense. bq. 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 ). for really major things we usually note these in the Upgrading section, but no matter hw dillegent we may be, i still think it's a good idea that all solr users should have a copy of hte lucene CHANGES.txt as well I think a build.xml addition that copies ../lucene/CHANGES.txt into the dist dir as LUCENE_CHANGES.txt and a one line note about it at the top of Solr's CHANGES.txt would make a lot of sense. 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
