There's a discussion thread in the mailing list as well
https://lists.apache.org/thread/nlqgk3cb8z9v7gnrw3kkqxpp3v4y80j5
Your best bet is to reply to the JIRA to bring some traction back to that
option.
Jan
> 27. mai 2024 kl. 23:18 skrev Christos Malliaridis :
>
> Thanks for the reply,
>
>
Thanks for the reply,
Both options you mentioned may work under certain circumstances. In the
current scenario, giving the application (Flink jobs) that needs the
collection the responsibility would not work without additional workarounds
that handle synchronization of multiple instances for lets
Hi
You are correct that you'll use the ordinary Solr APIs to provision collections.
Normally I'd recommend that the application that needs the collection should
also have the responsibility of bootstrapping its config set and collection.
Another popular option is to have an init container with
Hello everyone,
I am a new adopter of Solr and I am working on a Kubernetes cluster setup
where I run a helm chart for installing and configuring multiple components
of a backend, including Apache Kafka, Flink and Solr.
Most components come with their own operator and CRDs which I install with
a
