Hi all, I will work on SOLR-11771 <https://issues.apache.org/jira/browse/SOLR-11771> today, It is a simple fix and will be great if it get fixed in 7.2.1
On Fri, Jan 5, 2018 at 11:23 PM Erick Erickson <erickerick...@gmail.com> wrote: > Neither of those Solr fixes are earth shatteringly important, they've both > been around for quite a while. I don't think it's urgent to include them. > > That said, they're pretty simple and isolated so worth doing if Jim is > willing. But not worth straining much. I was just clearing out some backlog > over vacation. > > Strictly up to you Jim. > > Erick > > On Fri, Jan 5, 2018 at 6:54 AM, David Smiley <david.w.smi...@gmail.com> > wrote: > >> https://issues.apache.org/jira/browse/SOLR-11809 is in progress, should >> be easy and I think definitely worth backporting >> >> On Fri, Jan 5, 2018 at 8:52 AM Adrien Grand <jpou...@gmail.com> wrote: >> >>> +1 >>> >>> Looking at the changelog, 7.3 has 3 bug fixes for now: LUCENE-8077, >>> SOLR-11783 and SOLR-11555. The Lucene change doesn't seem worth >>> backporting, but maybe the Solr changes should? >>> >>> Le ven. 5 janv. 2018 à 12:40, jim ferenczi <jim.feren...@gmail.com> a >>> écrit : >>> >>>> Hi, >>>> We discovered a bad bug in 7x that affects indices created in 6x with >>>> Lucene54DocValues format. The SortedNumericDocValues created with this >>>> format have a bug when advanceExact is used, the values retrieved for the >>>> docs when advanceExact returns true are invalid (the pointer to the values >>>> is not updated): >>>> https://issues.apache.org/jira/browse/LUCENE-8117 >>>> This affects all indices created in 6x with sorted numeric doc values >>>> so I wanted to ask if anyone objects to a bugfix release for 7.2 (7.2.1). I >>>> also volunteer to be the release manager for this one if it is accepted. >>>> >>>> Jim >>>> >>> >> >> -- >> Lucene/Solr Search Committer, Consultant, Developer, Author, Speaker >> LinkedIn: http://linkedin.com/in/davidwsmiley | Book: >> http://www.solrenterprisesearchserver.com >> > >
