Hello there! I've been researching moving from Standalone Solr to k8s
SolrCloud setup and I'm wondering how you guys manage configsets and
collections when operating in k8s? It seems to me that the easiest
solution is to introduce some kind of an admin process (In a form of a
bash script) that will
Need to show limited rows, even if someone specifies more rows.
http://xxx.xx.xx.xx:8983/solr/regions/select?q=*:*&start=0&*rows=100*
In the above a person can specify any number of rows and can download all
the records. Anyway to restrict the search result to say 50
Regards,
Anuj
Hi! There is an official Solr project to manage Solr on kubernetes called “Solr
Operator”. You can also check it if you wish, instead of rolling your own
implementation.
Alternatively I used to build a custom docker image based on Solr image and put
configsets in there, and upload them on Solr
Hi Anuj, I believe this could work:
https://solr.apache.org/guide/solr/latest/configuration-guide/requesthandlers-searchcomponents.html#invariants
Regards
-ufuk yilmaz
—
> On 30 Jan 2024, at 13:39, Anuj Bhargava wrote:
>
> Need to show limited rows, even if someone specifies more rows.
>
>
I am not sure I get the question, but can't you add a check in the
search-API layer that says:
int maxAllowedRows = 50;
if (rows > maxAllowedRows){
rows = maxAllowedRows
}
Cheers
--
*Alessandro Benedetti*
Director @ Sease Ltd.
*Apache Lucene/Solr Committer*
*Apache Solr PM
Thank you! I’ve looked at Solr Operator and seems like it’s a good way to
go.
Regarding the upload from the script inside an image, did you implement
some kind of a locking mechanism or “assigned” one of the instances to do
the job?
Best regards,
Dmitrii Fitisov
On Tue, 30 Jan 2024 at 11:54, ufu
Hi,
the hnsw documentation for the Lucene HnswGraph and the SolR vector search is
not very verbose, especially in regards to the parameters hnswMaxConn and
hnswBeamWidth.
I find it hard to come up with sensible values for these parameters by reading
the paper from 2018.
Does anyone have experie
Hi! For uploading the scripts from inside the image, I didn't implement a
locking mechanism or assigned an instance 🤔 Since if configset was already
uploaded on the first ever run, on the subsequent runs it would just log an
error (configset already exists) and continue with the rest of the proc
Submitted PR: https://github.com/apache/solr/pull/2233
Open to further discussion on the JIRA/PR if more fields need to be added
to the handler output.
On Mon, Jan 29, 2024 at 8:03 AM Christine Poerschke (BLOOMBERG/ LONDON) <
cpoersc...@bloomberg.net> wrote:
> Wonderful. Please feel free to dir
Hi all,
I have an awesome position/ senior developer position @opensearch.org leading
query engineering/ lucene development to work with search at exabyte scale.
Please reach out if interested,
Ani
Hi Anirudha
Thank you for reaching out. I am interested in this position.
Attached is my resume
Regards,
Angad Sharma
On Tue, 30 Jan, 2024, 11:15 pm Anirudha Jadhav,
wrote:
> Hi all,
>
> I have an awesome position/ senior developer position @opensearch.org
> leading query engineering/ lucene
11 matches
Mail list logo
