I hear you and sympathize but "SolrCloud" has been used long enough that I
doubt the trouble is worth it. I guess that makes me "+0". That said, I
think it wouldn't hurt to formalize "standalone mode" as-such and perhaps
say more explicitly that SolrCloud == "cluster mode" even if we don't
elimin
I think it highly depends on how you want to do it. You could continue to run
4.6 and have another instance(a) with 8.2+. Then you just Index as you used to
do it until now on the new one. Once you have all the data indexed you switch
you lt application to 8.2. Of course you need to test it in d
Hi Shawn,
Any doc or links for re indexing process. We are using Lucene core 8.0.0.
Thanks,
Jyothsna
-Original Message-
From: Jyothsna Bavisetti
Sent: Thursday, September 26, 2019 11:51 PM
To: dev@lucene.apache.org
Subject: RE: Lucene index upgrade from 4.6 to 8 facing issue
Hi Shawn,
Raised https://issues.apache.org/jira/browse/SOLR-13808. Thanks, Jochen!
On Mon, Sep 30, 2019 at 4:26 PM Mikhail Khludnev wrote:
> Jochen, right! Sorry for didn't get your point earlier. {!bool filter=}
> means Lucene filter, not Solr's one. I suppose {!bool cache=true} flag can
> be easily ad
Hi, folks,
(Note: You're receiving this email because you're on the dev@ list for
one or more Apache Software Foundation projects.)
For ApacheCon North America 2019, we asked projects to participate in
the creation of project/topic specific tracks. This was very successful,
with about 15 projects
Thanks Andrzej, +1 for SOLR-13790 and SOLR-8241. Also, please provide
some guidance on SOLR-13677 and how can we resolve it.
On Tue, Oct 1, 2019 at 2:11 PM Andrzej Białecki wrote:
>
> I’m also working on SOLR-13790 (which is marked Critical, but depending on
> your POV it could be a Blocker - th
I’m also working on SOLR-13790 (which is marked Critical, but depending on your
POV it could be a Blocker - the functionality is broken as is).
If the feature freeze is next week then maybe I’ll also manage to finish
SOLR-8241, which would give users opportunity to test CaffeineCache performance