Except I just finished helping a contributor with a feature that touches both and I know for a fact that it was developed for his customer who was using solr (payload inequalities)... and have another in the works (the AQP).... Not being able to enhance lucene to support a feature in solr is an issue IMHO.
On Thu, Feb 25, 2021 at 6:05 PM Mike Drob <[email protected]> wrote: > It is possible to publish snapshots into the Apache Nexus repository. That > said, I think it is a bad idea for Solr to depend on Lucene snapshots > because that constrains the ability to do releases. Either you have to wait > for a Lucene release and then you can cut over, or you have to figure out > what changes you need to roll back. > > Features today rarely touch both fronts anyway, they usually land in > Lucene first and then percolate into Solr. For an easy example, we can see > how WAND was developed recently. > > On Thu, Feb 25, 2021 at 5:02 PM Houston Putman <[email protected]> > wrote: > >> Once the projects are on separate release cadences there wont be an >> ability to “add on both fronts” anymore. You will have to add to lucene, >> wait for a release, then add to Solr once Solr upgrades its lucene >> dependency to that new version. I dont imagine that we are going to keep >> Solr master/main, or even 8x, 9x, etc, depending on Lucene snaphsots in >> perpetuity. After it becomes possible (when lucene 9.0 is released) we >> should only be using released lucene versions as dependencies for every >> version branch in Solr. >> >> On Thu, Feb 25, 2021 at 5:49 PM Gus Heck <[email protected]> wrote: >> >>> Until the first feature that wants to add something on both fronts... Is >>> it possible for Lucene to publish nightly snapshots? I know there is some >>> level of support for snapshots in central, though I don't know what >>> their usage policies are. If that's too restricted is there an artifact >>> repo controlled by the ASF that could be used? (An implementation of Apache >>> Archiva?) This would have the added benefit of allowing solr to detect when >>> Lucene breaks something before its released. >>> >>> On Thu, Feb 25, 2021 at 4:50 PM Houston Putman <[email protected]> >>> wrote: >>> >>>> Hey everyone, >>>> >>>> Currently there is discussion going on, in SOLR-14762 >>>> <https://issues.apache.org/jira/browse/SOLR-14762>, regarding the >>>> split of the lucene-solr repo into individual repos for Solr and Lucene. >>>> There seems to be agreement that we shouldn't wait for a Lucene release to >>>> do the split, and instead split now and release whenever that happens. >>>> >>>> The biggest issue that arises there is that Solr's master branch is >>>> obviously based on Lucene's master branch, since they are currently the >>>> same. So when the split happens, Solr master will have to depend on Lucene >>>> 9.0-SNAPSHOT. We can have solr merely depend on the lucene snapshot, but >>>> that will result in inconsistent builds, depending on whatever cached >>>> dependencies each dev has locally. Personally, I think that will cause a >>>> bunch of build errors and headaches for everyone trying to maintain Solr. >>>> >>>> There is another option though. We could instead do an *alpha* >>>> "release" of lucene-solr 9.0 right before the repo is split. Therefore Solr >>>> can reliably depend on a stable version of lucene until 9.0 is truly >>>> released. (And lucene can use a stable version of Solr, if it sees a need >>>> for that). There would be no guarantees for using this alpha release, and >>>> we don't have to advertise it at all. >>>> >>>> It's not perfect, but I think it would be preferable to depending on an >>>> ever-changing SNAPSHOT lucene. >>>> >>>> - Houston >>>> >>> >>> >>> -- >>> http://www.needhamsoftware.com (work) >>> http://www.the111shift.com (play) >>> >> -- http://www.needhamsoftware.com (work) http://www.the111shift.com (play)
