Hi,
I'm proposing a process for every ticket which has a user facing
change. The changes could be
* A new command/end point
* A new request parameter
* A configuration (solr.xml, clusterprops.json, or any other file in ZK)
* A new file (part of file) in ZK
* A new file in file system
I may have
I am running precommit on the branch 8_x right now -- once it
completes, I will cut the branch 8.7.
--
Regards,
Atri
Apache Concerted
-
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail:
Hello,
I'm confused that master now has a non-empty 8.8 section in the Changelog
while branch_8_7 has not been cut yet, was it done by mistake?
--
Adrien
Opened https://issues.apache.org/jira/browse/SOLR-14941 w.r.t. the help file
update and with a question re: 'assemble' vs. 'dev' directory detail.
From: dev@lucene.apache.org At: 09/28/20 19:08:15To: Christine Poerschke
(BLOOMBERG/ LONDON ) , dev@lucene.apache.org
Subject: Re: bin/solr
Is there any reasons for this why PointInsetQuery return NO_MORE_DOCS instead
of NULL while NULL can terminate early.
hacker win7
hackersw...@gmail.com
> On Sep 29, 2020, at 11:59, hacker win7 wrote:
>
> Thanks Adrien Grand
>
> We store long numbers in our points, in our search service,
