Payloads for each term

Hi Lucene Devs, I have a need to store a sparse feature vector on a per term basis. The total number of possible dimensions are small (~50) and known at indexing time. The feature values will be used in scoring along with corpus statistics. It looks like payloads

Re: 8.6.3 Release

I don't think the status of any page should be in the name of the page -- it breaks links when it changes. The status can be at the top of the content. ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Thu, Oct 22, 2020 at 10:55 AM Ishan Chattopadhyay

Re: 8.7 Release Blockers

If we get down to just SOLR-14067 holding us up, I think it could be moved to the next release. I’ve made a lot of progress, but it may still take a few more days to get to done done. > On Oct 22, 2020, at 4:35 PM, Adrien Grand wrote: > > Can someone help review this PR to get the above block

Re: 8.7 Release Blockers

Can someone help review this PR to get the above blocker resolved? https://github.com/apache/lucene-solr/pull/2019 On Thu, Oct 22, 2020 at 4:11 PM Atri Sharma wrote: > Reminder: This is still a blocker for 8.7: > > https://issues.apache.org/jira/browse/SOLR-14354 > > On Tue, Oct 20, 2020 at 1:02

Re: 8.6.3 Release

I guess some convention due to MoinMoin? On Thu, 22 Oct, 2020, 7:25 pm Jason Gerlowski, wrote: > On the topic - is there a particular reason behind the convention of > having the page titles be named without spaces or periods? As is they > look more like Java classnames than page titles. e.g. >

Re: 8.7 Release Blockers

Reminder: This is still a blocker for 8.7: https://issues.apache.org/jira/browse/SOLR-14354 On Tue, Oct 20, 2020 at 1:02 PM Atri Sharma wrote: > > Hi All, > > Below are the issues marked as release blockers for 8.7. Can the > owners please resolve or move at the earliest? > > https://issues.apac

Re: 8.6.3 Release

On the topic - is there a particular reason behind the convention of having the page titles be named without spaces or periods? As is they look more like Java classnames than page titles. e.g. "ReleaseNote852" vs "Release Notes: 8.5.2" vs. "8.5.2 Release Notes" On Thu, Oct 22, 2020 at 9:50 AM Jas

Re: 8.6.3 Release

I added that "DRAFT-" prefix mostly for the reason Atri mentioned: to indicate that the page was a WIP. I thought it might also have the side benefit of catching the eye of any committers who had Confluence open and a few minutes to review the content. The page still has "DRAFT-" because, as Cass

Re: 8.6.3 Release

Fair point -- I have changed accordingly. On Thu, Oct 22, 2020 at 7:09 PM Cassandra Targett wrote: > > That’s a fair thing to consider, but does it really matter if someone looks > at the draft notes pre-release? What would be the harm if users happen across > them before they’re done? > > (And

Re: 8.6.3 Release

That’s a fair thing to consider, but does it really matter if someone looks at the draft notes pre-release? What would be the harm if users happen across them before they’re done? (And to David’s point, it’s not in the RM steps to fix the page name after release, so it’s pretty easy to forget t

Re: 8.6.3 Release

I added it since it looked a safe way to indicate that the draft notes are in progress and should not be referred to in case somebody is surfing the release notes. Atri On Thu, Oct 22, 2020 at 6:23 PM David Smiley wrote: > > Jason: This is the first time I recall seeing release note pages in >

Re: 8.6.3 Release

Jason: This is the first time I recall seeing release note pages in Confluence with a "DRAFT-" prefix. And I also see that Atri has follow-ed suit (following your lead, no doubt) for 8.6. Why? Looking at the page navigation, it's clearly an oddity -- a change. And it's still DRAFT despite it b

Re: PointInSetQuery dose not terminate early if DocIdSetBuilder's bitSet is null

Hi, Adrien Grand Could we check the result after BKD.intersect() inner the PointInSetQuery.scorer(), if the result.build.iterator() the first next doc is already NO_MORE_DOCS ? We need not to build scorer with new ConstantScoreScorer() , just return null. In this way, the BooleanQuery for AND

Re: Seeking Inputs for Release Highlights

Thanks, I added some entries to the Lucene release notes. On Thu, Oct 22, 2020 at 1:23 PM Atri Sharma wrote: > Hi Adrien, > > Please find below: > > https://cwiki.apache.org/confluence/display/SOLR/DRAFT-ReleaseNote87 > https://cwiki.apache.org/confluence/display/LUCENE/DRAFT-ReleaseNote87 > > O

Re: Seeking Inputs for Release Highlights

Hi Adrien, Please find below: https://cwiki.apache.org/confluence/display/SOLR/DRAFT-ReleaseNote87 https://cwiki.apache.org/confluence/display/LUCENE/DRAFT-ReleaseNote87 On Thu, Oct 22, 2020 at 4:37 PM Adrien Grand wrote: > > Hi Atri, if you can create a page in the wiki, I'll be happy to add s

Re: Seeking Inputs for Release Highlights

Hi Atri, if you can create a page in the wiki, I'll be happy to add some items to the release highlights. I have the compression for stored fields improvements in mind as well as the speedups for queries sorted by a field indexed with points. On Thu, Oct 22, 2020 at 12:54 PM Atri Sharma wrote: >

Seeking Inputs for Release Highlights

Hi All, Can we come up with the items we wish to highlight in 8.7 release notes? Atri -- Regards, Atri Apache Concerted - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@luc