Ahmet, They included at 5x patch on the JIRA here: https://issues.apache.org/jira/secure/attachment/12782146/SOLR-8542-branch_5x.patch (it's one of the files attached to the Jira). The JIRA has two patches included on it, one for master (approximately 6.0), and the one I just linked to for the 5x branch.
Assuming you checkout branch 5x (which should be approximately the same code 5.5.0), then I would assume the Bloomberg patch would work. I've personally also back-ported it to 5.4.1, which required a fair number of changes related to iterator changes on Scorers, but wasn't too much trouble. Hopefully the patch above gives you what you need. Trey Grainger SVP of Engineering @ Lucidworks Co-author, Solr in Action On Wed, Apr 6, 2016 at 6:21 PM, Shawn Heisey <apa...@elyograg.org> wrote: > On 4/6/2016 1:55 PM, Ahmet Anil Pala wrote: > > Hi Michael, thanks for answering and sorry for the late reply. > > > > By 5.x branch build, do you mean this > > -> https://github.com/bloomberg/lucene-solr/tree/branch_5x > > > > It seems that LTR is not merged onto it and I doubt it is mergable > > without changes as this is exactly what I have tried and failed. As > > for your pull request SOLR-8542, it is supposed to be merged to the > > master branch which is already the version 7.0.0. Is the LTR plugin > > originally developed only compatible with Solr-6x and later or am I > > missing something here? > > I think that something like this will not make it into 5.x. With the > 6.0.0 release just around the corner (probably a matter of days), 5.x > goes into maintenance mode, and 4.x basically goes dormant. Maintenance > mode basically means that no significant changes will happen, especially > changes that might affect stability. A strict interpretation of this is > "no new features", and this is typically the stance that most committers > adopt for the previous major version. It also means that only *major* > bugs will be fixed, especially as time goes on. > > You've indicated that you couldn't merge it cleanly to branch_5x. If > the change requires significant work just to merge, and the > functionality is already present in a later release, it's probably not > going to happen. > > There are some important bugfixes that have already been committed to > 5x, which should result in a 5.5.1 release in the near future, and it is > entirely possible that somebody will volunteer to release 5.6.0, > although the current changelog for 5.6.0 only has two issues, and > neither is particularly interesting for most users. > > If somebody wants to volunteer to do the work, then what I've said might > not apply at all. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
