Hi,
We are planning to implement Solr Cloud 8.7.0, running in Kubernetes cluster,
with external Zookeeper 3.4.5 cdh 5.16.
Solr 8.7.0 seems to be matched with Zookeeper 3.6.2. Is there any issue using
Zookeeper 3.4.5 cdh 5.16?
Thanks in advance.
Regards,
Subhajit
Hi There,
I am planning to implement Solr cloud 8.7.0 with existing Zookeeper 3.4.5. This
is cloudera provided zookeeper.
Is there any red flags, for such configuration, as I couldn’t find any
compatibility matrix?
Many thanks in advance.
Regards,
Subhajit
that "request" method is called per request, make sure whatever
logic you have there is not super expensive.
On Wed, Mar 3, 2021 at 10:48 AM Subhajit Das
wrote:
> Hi Thomas,
>
> Thanks. Can you please also share a sample of code to configure the client
> with your worka
owse/SOLR-15155 to try to address this
issue in future releases.
On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das wrote:
>
> Hi There,
>
> Is there any way to programmatically set basic authentication credential
> on CloudSolrClient?
>
> The only documentation available is to use s
Hi There,
I am trying to create a rule based authorization for two types of user.
Role : Access
-
power-user : Everything except data change in collections/cores
ui-user : UI access to view all data. But no edit access except data change in
collections/cores
How to implement
...@zookeeper.apache.org
Subject: Re: Zookeeper 3.4.5 with Solr 8.8.0
On 3/1/2021 6:51 AM, Subhajit Das wrote:
> I noticed, that Solr 8.8.0 uses Zookeeper 3.6.2 client, while Solr 6.3.0 uses
> Zookeeper 3.4.6 client. Is this a client bug or mismatch issue?
> If so, how to fix this
Hi There,
Is there any way to programmatically set basic authentication credential on
CloudSolrClient?
The only documentation available is to use system property. This is not useful
if two collection required two separate set of credentials and they are
parallelly accessed.
Thanks in
Hi There,
I am setting up Solr 8.8.0 with Zookeeper 3.4.5.
There seems to an issue. EndOfStream issue is coming, saying client must have
closed the connection.
If same tried with Solr 6.3.0, the issue dosen’t come. This comes with newer
Solr only.
I noticed, that Solr 8.8.0 uses Zookeeper
tail", even though the tlog is not a text file, its
content can mostly be read using these commands.
You will have one document per line and should be able to see the fields
content.
I don't know is there is a Solr command which would give better display though.
Gaël
De : Subhajit Das
Envoyé : samed
Hi There,
I faced a issue, on a core, in multicore standalone instance.
Is there any way to read tlog contents as text files. This might help to
resolve the issue.
Thanks in advance.
olrClientBuilder();
>
> Now you have control of the CredentialsProvider and can have it return
> whatever credentials you wish, so long as you still have a reference
> to it.
>
> > On Wed, Mar 3, 2021 at 5:42 AM Subhajit Das
> wrote:
> >
> > >
> > > H
Hi there,
I am planning to use 8.8 line-up for production use.
But recently, a lot of people are complaining on 8.7 and 8.8. Also, there is a
clearly known issue on 8.8 as well.
Following trends of earlier versions (5.x, 6.x and 7.x), will 8.8 will also be
finalized?
For 5.x, 5.5.x was last
apa...@elyograg.org>
Sent: 17 February 2021 09:33 AM
To: solr-user@lucene.apache.org<mailto:solr-user@lucene.apache.org>
Subject: Re: Is 8.8.x going be stabilized and finalized?
On 2/16/2021 7:57 PM, Subhajit Das wrote:
> I am planning to use 8.8 line-up for production use.
>
> But rece
2021 at 2:45 PM Subhajit Das
wrote:
> Hi Joel,
>
> Thanks for response. But, is there any way to simulate the same?
>
>
> From: Joel Bernstein<mailto:joels...@gmail.com>
> Sent: 20 February 2021 01:13 AM
> To: solr-user@lucene.apache.org<mailto:solr-user@luc
Hi,
“{!graph ...}” goes to infinite depth by default. But “nodes()” stream does not
go to infinite depth.
Is there any way to go to infinite depth?
is designed for a stepwise graph walk. It doesn't do a full traversal.
Joel Bernstein
http://joelsolr.blogspot.com/
On Fri, Feb 19, 2021 at 4:47 AM Subhajit Das
wrote:
>
> Hi,
>
> “{!graph ...}” goes to infinite depth by default. But “nodes()” stream
> does not go to infinite depth.
16 matches
Mail list logo
