I think it's important to be able to roll out changes to nodes in a way the
user controls (e.g. one node at a time), instead of only having an
all-at-once option. I really liked Tomas's explanation of the need. The
same need exists for collections, and Solr satisfies that today via
configSets.
I am pleased to announce the availability of Apache PyLucene 8.6.1.
Apache PyLucene, a subproject of Apache Lucene, is a Python extension for
accessing Apache Lucene Core. Its goal is to allow you to use Lucene's text
indexing and searching capabilities from Python. It is API compatible with
On Wed, 9 Sep 2020, Dawid Weiss wrote:
+1 to release, thanks Andi.
This vote has passed.
Thank you all who voted !
Andi..
Dawid
On Tue, Aug 25, 2020 at 1:56 AM Andi Vajda wrote:
The PyLucene 8.6.1 (rc1) release tracking the recent release of
Apache Lucene 8.6.1 is ready.
A release
I would agree that the docker-solr tests (soon to be the solr/docker tests)
do a fairly good job of testing bin/solr and general runtime logic. Once
that gets merged in, I think it would be great to use that test suite for
all of the additional "bin/solr" tests that we want to add. Once we get the
+1 for analysis within the PR workflow.
Le ven. 4 sept. 2020 à 06:38, David Smiley a écrit :
> Sounds great to me! I'm really glad to hear it works with the PR
> workflow, and only on the files touched in the PR.
>
> ~ David Smiley
> Apache Lucene/Solr Search Developer
>
+1 to release, thanks Andi.
Dawid
On Tue, Aug 25, 2020 at 1:56 AM Andi Vajda wrote:
>
>
> The PyLucene 8.6.1 (rc1) release tracking the recent release of
> Apache Lucene 8.6.1 is ready.
>
> A release candidate is available from:
>
