RE: Updating Expired Certificate

Hello, How do we update a certificate in a SOLR Cloud without downtime? We have a SOLR cloud cluster with three nodes. SSL is enabled for use with SiteCore. We currently have a certificate in the "solr-ssl.keystore.jks". This certificate expired so we imported a new certificate into the

Re: Solr 7.7 - Few Questions

Hi Rahul, In addition to the wise advice below: remember in Solr, a 'document' is just the name for the thing that would appear as one of the results when you search (analagous to a database record). It's not the same conceptually as a 'Word document' or a 'PDF document'. If your source

RE: Sql entity processor sortedmapbackedcache out of memory issue

with 18 cores in it. Each core is in sync by running full-import on SortedMapBackedCache entities with WHERE clause based on timestamp(last index time) on child entities. -Original Message- From: Shawn Heisey Sent: 09 April 2019 13:27 To: solr-user@lucene.apache.org Subject: Re: Sql

Re: Solr 7.7 - Few Questions

Manisha, In addition to what Shawn has mentioned above, I would also like you to reevaluate your use case. Do you *need to* index the whole document ? eg: If it's an email, the body of the email *might* be more important than any attachments, in which case you could choose to only index the email

Re: Authentication for each collection

https://lucene.apache.org/solr/guide/8_6/authentication-and-authorization-plugins.html *Authentication* is global, but *Authorization* can be configured to use rules that restrict permissions on a per collection basis...

Re: Non Deterministic Results from /admin/luke

On 10/1/2020 4:24 AM, Nussbaum, Ronen wrote: We are using the Luke API in order to get all dynamic field names from our collection: /solr/collection/admin/luke?wt=csv=0 This worked fine in 6.2.1 but it's non deterministic anymore (8.6.1) - looks like it queries a random single shard. I've

Re: Solr 7.7 - Few Questions

On 10/1/2020 6:57 AM, Manisha Rahatadkar wrote: We are using Apache Solr 7.7 on Windows platform. The data is synced to Solr using Solr.Net commit. The data is being synced to SOLR in batches. The document size is very huge (~0.5GB average) and solr indexing is taking long time. Total

Re: Solr client in JavaScript

On 10/1/2020 3:55 AM, Sunil Dash wrote: This is my javascript code ,from where I am calling solr ,which has a loaded nutch core (index). My java script client ( runs on TOMCAT server) and Solr server are on the same machine (10.21.6.100) . May be due to cross domain references issues OR

RE: advice on whether to use stopwords for use case

-solr.PatternReplaceCharFilterFactory -Original message- > From:Walter Underwood > Sent: Thursday 1st October 2020 18:20 > To: solr-user@lucene.apache.org > Subject: Re: advice on whether to use stopwords for use case > > I can’t think of an easy way to do this in Sol

Re: advice on whether to use stopwords for use case

I can’t think of an easy way to do this in Solr. Do a bunch of string searches on the query on the client side. If any of them match, make a “no hits” result page. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Sep 30, 2020, at 11:56 PM, Derek

RE: Solr 7.7 - Few Questions

I apologize for sending this email again, I don't mean to spam the mailbox but looking out for the urgent help. We are using Apache Solr 7.7 on Windows platform. The data is synced to Solr using Solr.Net commit. The data is being synced to SOLR in batches. The document size is very huge

Re: Solr 7.6 query performace question

harjags wrote > Below errors are very common in 7.6 and we have solr nodes failing with > tanking memory. > > The request took too long to iterate over terms. Timeout: timeoutAt: > 162874656583645 (System.nanoTime(): 162874701942020), >

Re: Transaction not closed on ms sql

First of all, I’d just use a stand-alone program to do your processing for a number of reasons, see: https://lucidworks.com/post/indexing-with-solrj/ 1- I suspect your connection will be closed eventually. Since it’s expensive to open one of these, the driver may keep it open for a while.

Re: advice on whether to use stopwords for use case

Yes, the requirements (for now) is not to return any results. I think they may change the requirements,pending their return from the holidays. If so, then check for those words in the query before sending it to Solr. That is what I think so too. Thinking further, using stopwords for this,

Re: advice on whether to use stopwords for use case

Hi Alex The business requirement (for now) is not to return any result when the search keywords are cigarette related. The business user team will provide the list of the cigarette related keywords. Will digest, explore and research on your suggestions. Thank you. On 30/9/2020 10:56 am,

Re: How to Resolve : "The request took too long to iterate over doc values"?

raj.yadav wrote > In cases for which we are getting this warning, I'm not able to extract > the > `exact solr query`. Instead logger is logging `parsedquery ` for such > cases. > Here is one example: > > > 2020-09-29 13:09:41.279 WARN (qtp926837661-82461) [c:mycollection > s:shard1_0

Re: Master/Slave

ly safe to assume >> that Master/Slave replication will continue to be supported after all >> (since the assertion that it would be replaced by CDCR has been >> discredited)? In either case, are there other suggested implementations of >> having a read-only SolrCloud receive d

Re: Master/Slave

as been > discredited)? In either case, are there other suggested implementations of > having a read-only SolrCloud receive data from a read/write SolrCloud? > > > Thanks > > -Original Message- > From: Shawn Heisey > Sent: Tuesday, May 21, 2019 11:15 AM > To: s

Re: advice on whether to use stopwords for use case

I’m not clear on the requirements. It sounds like the query “cigar” or “cuban cigar” should return zero results. Is that right? If so, then check for those words in the query before sending it to Solr. But the stopwords approach seems like the requirement is different. Could you give some

Re: advice on whether to use stopwords for use case

You may also want to look at something like: https://docs.querqy.org/index.html ApacheCon had (is having..) a presentation on it that seemed quite relevant to your needs. The videos should be live in a week or so. Regards, Alex. On Tue, 29 Sep 2020 at 22:56, Alexandre Rafalovitch wrote: > >

Re: How to Resolve : "The request took too long to iterate over doc values"?

Hi, I went through other queries for which we are getting `The request took too long to iterate over doc values` warning. As pointed by Erick I have cross check all the fields that are being used in query and there is no such field against which we are searching and it as index=false and

Re: How to Resolve : "The request took too long to iterate over doc values"?

Hi, I went through other queries for which we are getting `The request took too long to iterate over doc values` warning. As pointed by Erick I have cross check all the fields that are being used in query and there is no such field against which we are searching and it as index=false and

Re: How to Resolve : "The request took too long to iterate over doc values"?

I went through other queries for which we are getting `The request took too long to iterate over doc values` warning. As pointed by Erick I have cross check all the fields that are being used in query and there is no such field against which we are searching and it as index=false and

Re: Slow Solr 8 response for long query

Increasing the number of rows should not have this kind of impact in either version of Solr, so I think there’s something fundamentally strange in your setup. Whether returning 10 or 300 documents, every document has to be scored. There are two differences between 10 and 300 rows: 1> when

Re: ApacheCon at Home 2020 starts tomorrow!

On 30/09/2020 05:14, Rahul Goswami wrote: > Thanks for sharing this Anshum. Day 1 had some really interesting sessions. > Missed out on a couple that I would have liked to listen to. Are the > recordings of these sessions available anywhere? The ASF will be uploading the recordings of all

Re: ApacheCon at Home 2020 starts tomorrow!

Thanks for sharing this Anshum. Day 1 had some really interesting sessions. Missed out on a couple that I would have liked to listen to. Are the recordings of these sessions available anywhere? -Rahul On Mon, Sep 28, 2020 at 7:08 PM Anshum Gupta wrote: > Hey everyone! > > ApacheCon at Home

Re: advice on whether to use stopwords for use case

I am not sure why you think stop words are your first choice. Maybe I misunderstand the question. I read it as that you need to exclude completely a set of documents that include specific keywords when called from specific module. If I wanted to differentiate the searches from specific module, I

Re: Slow Solr 8 response for long query

What do the debug versions of the query show between two versions? One thing that changed is sow (split on whitespace) parameter among many. It is unlikely to be the cause, but I am mentioning just in case.

Re: How to Resolve : "The request took too long to iterate over doc values"?

Hey Erick, In cases for which we are getting this warning, I'm not able to extract the `exact solr query`. Instead logger is logging `parsedquery ` for such cases. Here is one example: 2020-09-29 13:09:41.279 WARN (qtp926837661-82461) [c:mycollection s:shard1_0 r:core_node5

Re: Vulnerabilities in SOLR 8.6.2

Solr follows the ASF policy for reporting vulnerabilities, described in this page on our website: https://lucene.apache.org/solr/security.html. This page also lists known vulnerabilities that have been addressed, with their mitigation steps. Scanning tools are commonly full of false positives

Re: How to Resolve : "The request took too long to iterate over doc values"?

Let’s see the query. My bet is that you are _searching_ against the field and have indexed=false. Searching against a docValues=true indexed=false field results in the equivalent of a “table scan” in the RDBMS world. You may use the docValues efficiently for _function queries_ to mimic some

Re: SOLR Cursor Pagination Issue

Hi Erick,"You still haven’t given an example of the results you’re seeing that are unexpected". I will give an example of the data I received. Before starting data update I have: solrCloud: Expected series criteria:386062 Collected series: 386062 Number of requests: 40 Collected unique series:

Re: Returning fields a specific order

Hi, If data are in json format, you should use jq -S https://stackoverflow.com/a/38210345/5998915 Regards Dominique Le lun. 28 sept. 2020 à 18:30, gnandre a écrit : > Hi, > > I have a use-case where I want to compare stored fields values of Solr > documents from two different Solr

Re: solr performance with >1 NUMAs

On 9/28/2020 12:17 PM, Wei wrote: Thanks Shawn. Looks like Java 11 is the way to go with -XX:+UseNUMA. Do you see any backward compatibility issue for Solr 8 with Java 11? Can we run Solr 8 built with JDK 8 in Java 11 JRE, or need to rebuild solr with Java 11 JDK? I do not know of any problems

Re: Solr storage of fields <-> indexed data

That's really good and helpful info, thank you. Perfect. Best wishes, Edd On Mon, 28 Sep 2020, 5:53 pm Shawn Heisey, wrote: > On 9/28/2020 8:56 AM, Edward Turner wrote: > > By removing the copyfields, we've found that our index sizes have reduced > > by ~40% in some cases, which is great!

Re: solr performance with >1 NUMAs

Thanks Shawn. Looks like Java 11 is the way to go with -XX:+UseNUMA. Do you see any backward compatibility issue for Solr 8 with Java 11? Can we run Solr 8 built with JDK 8 in Java 11 JRE, or need to rebuild solr with Java 11 JDK? Best, Wei On Sat, Sep 26, 2020 at 6:44 PM Shawn Heisey wrote: >

Re: Solr storage of fields <-> indexed data

On 9/28/2020 8:56 AM, Edward Turner wrote: By removing the copyfields, we've found that our index sizes have reduced by ~40% in some cases, which is great! We're just curious now as to exactly how this can be ... That's not surprising. My question is, given the following two schemas, if we

Re: Difference in q.op param behavior between Solr 6.3 and Solr 8.5.2

Thanks, this is helpful. I agree. q.op param should not affect fq parameter. I think this is a feature and not a bug. On Wed, Sep 23, 2020 at 4:39 PM Erik Hatcher wrote: > In 6.3 it did that? It shouldn't have. q and fq shouldn't share > parameters. fq's themselves shouldn't, IMO, have

Re: Solr storage of fields <-> indexed data

Fields are placed in the index totally separately from each other, so it’s no wonder that removing the copyField results in this kind of savings. And they have to be separate. Consider what comes out of the end of the analysis chain. The same input could produce totally different output. As a

Re: SOLR Cursor Pagination Issue

I said nothing about docId changing. _any_ sort criteria changing is an issue. You’re sorting by score. Well, as you index documents, the new docs change the values used to calculate scores for _all_ documents will change, thus changing the sort order and potentially causing unexpected results

Re: SOLR Cursor Pagination Issue

Hi, Erick I have a python script that sends requests with CursorMark. This script checks data against the following Expected series criteria: Collected series: Number of requests: Collected unique series: The request looks like this: select?indent=off=edismax=json={!key=NUM_DOCS}NOT

Re: Unable to upload updated solr config set

{ >> >> "responseHeader":{ >> >>"status":400, >> >>"QTime":51}, >> >> "error":{ >> >>"metadata":[ >> >> "error-class","org.apache.solr.common.SolrException

Re: Unable to upload updated solr config set

uot;org.apache.solr.common.SolrException", > > "root-error-class","org.apache.solr.common.SolrException"], > > "msg":"The configuration sampleConfigSet already exists in zookeeper", > > "code":400}} > > > how we re upload same config with few schema & solr config changes ? > > > > Thanks, > > Deepu >

Re: Corrupted records after successful commit

ta in it. > > Just id and version. > > > > 2. The second entry is really strange; this isn't a valid record at all > and > > I don't have any record of creating it. > > > > I've ruled out reindexing items both from my indexing script (I just > don't &

Re: Corrupted records after successful commit

the terminology right but would I be correct in > assuming that it is possible records are not being flushed from the buffer > when added? I'm assuming there is some kind of buffering or caching going > on before records are commttted? Is it possible they are getting corrupted > under higher t

Re: Corrupted records after successful commit

ng there is some kind of buffering or caching going on before records are commttted? Is it possible they are getting corrupted under higher than usual load? On Mon, 28 Sep 2020 at 20:41, Erick Erickson wrote: > There are several possibilities: > > 1> you simply have some process

Re: SOLR Cursor Pagination Issue

Define “incorrect” please. Also, showing the exact query you use would be helpful. That said, indexing data at the same time you are using CursorMark is not guaranteed do find all documents. Consider a sort with date asc, id asc. doc53 has a date of 2001 and you’re already returned the doc.

Re: Corrupted records after successful commit

There are several possibilities: 1> you simply have some process incorrectly updating documents. 2> you’ve changed your schema sometime without completely deleting your old index and re-indexing all documents from scratch. I recommend in fact indexing into a new collection and using coll

Re: What does current mean?

Hello, Wei-san Thank you for answering my question. That pretty makes sense to me. Sincerely, Kaya 2020年9月27日(日) 9:16 Wei : > My understanding is that current means whether there is data pending to be > committed. > > Best, > Wei > > On Sat, Sep 26, 2020 at 5:09 PM Kayak28 wrote: > > > Hello,

Re: Solr waitForMerges() causing leaderless shard during shutdown

Hi Ramsey, This is an interesting scenario, I vaguely remember someone (Cao Manh Dat?) on a similar issue - I’m not sure if newer versions of Solr already fixed that but it would be helpful to create a Jira issue to investigate it and verify that it’s indeed fixed in a more recent Solr

Re: solr performance with >1 NUMAs

On 9/26/2020 1:39 PM, Wei wrote: Thanks Shawn! Currently we are still using the CMS collector for solr with Java 8. When last evaluated with Solr 7, CMS performs better than G1 for our case. When using G1, is it better to upgrade from Java 8 to Java 11? From

Re: What does current mean?

My understanding is that current means whether there is data pending to be committed. Best, Wei On Sat, Sep 26, 2020 at 5:09 PM Kayak28 wrote: > Hello, Solr community: > > > > I would like to ask a question about the current icon on the core-overview > > under statistics. > > I thought

RE: Solr 8.6.2 UI issue

Thanks Alexandre. It was cache issue. Regards Manisha Rahatadkar -Original Message- From: Alexandre Rafalovitch Sent: Friday, September 25, 2020 6:12 PM To: solr-user Subject: Re: Solr 8.6.2 UI issue Sounds strange. If you had Solr installed previously, it could be cached Javascript

Re: solr performance with >1 NUMAs

Thanks Shawn! Currently we are still using the CMS collector for solr with Java 8. When last evaluated with Solr 7, CMS performs better than G1 for our case. When using G1, is it better to upgrade from Java 8 to Java 11? >From https://lucene.apache.org/solr/guide/8_4/solr-system-requirements.html,

Re: Delete from Solr console fails

You mention high CPU usage...Can you share the thread dump (using jstack) for both the delete by id and delete by query? Also, an output of /solr//schema executed on the host? Lastly, is this standalone Solr or SolrCloud? Attachments won’t make it to the list, so I would recommend sharing a link

Re: Delete from Solr console fails

Thanks Dominique! I just tried deleting a single document using its id. I tried this: id123 and this: id:id123 In each case, I still get the same "Solr connection lost" error. I checked that the Solr instance has enough RAM (it was using 73% of the RAM), but it was using 110% CPU. Could

Re: Solr queries slow down over time

Hi Mark, Thanks for confirming Dwane's advice from your own experience. I will shift to a streaming expressions implementation. Best Goutham On Fri, Sep 25, 2020 at 7:03 PM Mark H. Wood wrote: > On Fri, Sep 25, 2020 at 11:49:22AM +0530, Goutham Tholpadi wrote: > > I have around 30M documents

Re: Solr queries slow down over time

Thanks a ton, Dwane. I went through the article and the documentation link. This corresponds exactly to my use case. Best Goutham On Fri, Sep 25, 2020 at 2:59 PM Dwane Hall wrote: > Goutham I suggest you read Hossman's excellent article on deep paging and > why returning rows=(some large

Re: solr performance with >1 NUMAs

On 9/23/2020 7:42 PM, Wei wrote: Recently we deployed solr 8.4.1 on a batch of new servers with 2 NUMAs. I noticed that query latency almost doubled compared to deployment on single NUMA machines. Not sure what's causing the huge difference. Is there any tuning to boost the performance on

Re: solr performance with >1 NUMAs

Thanks Dominique. I'll start with the -XX:+UseNUMA option. Best, Wei On Fri, Sep 25, 2020 at 7:04 AM Dominique Bejean wrote: > Hi, > > This would be a Java VM option, not something Solr itself can know about. > Take a look at this article in comments. May be it will help. > >

Re: Solr 8.6.2 UI issue

Sounds strange. If you had Solr installed previously, it could be cached Javascript. Force-reload or try doing it in an anonymous window. Also try starting with an example (solr/start -e techproducts). Finally, if you are up to it, see if there are any serious errors in the Browser's developer

Re: Delete from Solr console fails

Hi Goutham, I agree with Rahul, avoid large deletebyquery. It you can, prefere one query to get all the ids first than use ids with deletebyid Regards Dominique Le ven. 25 sept. 2020 à 06:50, Goutham Tholpadi a écrit : > I spoke too soon. I am getting the "Connection lost" error again. > >

Re: solr performance with >1 NUMAs

Hi, This would be a Java VM option, not something Solr itself can know about. Take a look at this article in comments. May be it will help. https://blog.thetaphi.de/2012/07/use-lucenes-mmapdirectory-on-64bit.html?showComment=1347033706559#c229885263664926125 Regards Dominique Le jeu. 24

Re: Solr 8.6.2 text_general

. But even in that case, there may be other fields with different multiValued values. And if you sort, group, or facet on them when some have been indexed one way and some others, you’ll get errors. I strongly urge you to re-index all your data into a new collection and, perhaps, use collection aliasing

Re: Solr queries slow down over time

On Fri, Sep 25, 2020 at 11:49:22AM +0530, Goutham Tholpadi wrote: > I have around 30M documents in Solr, and I am doing repeated *:* queries > with rows=1, and changing start to 0, 1, 2, and so on, in a > loop in my script (using pysolr). > > At the start of the iteration, the calls

Re: Solr 8.6.2 text_general

It worked. I just added multiValued="true". Thanks for all your help. Regards, Anuj On Fri, 25 Sep 2020 at 18:08, Alexandre Rafalovitch wrote: > Ok, something is definitely not right. In those cases, I suggest > checking backwards from hard reality. Just in case the file you

Re: Solr 8.6.2 text_general

Ok, something is definitely not right. In those cases, I suggest checking backwards from hard reality. Just in case the file you are looking at is NOT the one that is actually used when collection is actually setup. Happened to me more times than I can count. Point your Admin UI to the collection

Re: Any blog or url that explain step by step configure grafana dashboard to monitor solr metrics

Hi, In case you decide to go with cloud solution, you can check how you can monitor Solr with Sematext: https://sematext.com/blog/solr-monitoring-made-easy-with-sematext/ Regards, Emir -- Monitoring - Log Management -

Re: Solr queries slow down over time

Goutham I suggest you read Hossman's excellent article on deep paging and why returning rows=(some large number) is a bad idea. It provides an thorough overview of the concept and will explain it better than I ever could

Re: Solr 8.6.2 text_general

Schema on both are the same Regards, Anuj On Thu, 24 Sep 2020 at 18:58, Alexandre Rafalovitch wrote: > These are field definitions for _text_ and text, your original > question was about the fields named "country"/"currency" and whatever > type they mapped to. > > Your

Re: Delete from Solr console fails

I spoke too soon. I am getting the "Connection lost" error again. I have never faced this problem when there are a small number of docs in the index. I was wondering if the size of the index (30M docs) has anything to do with this. Thanks Goutham On Fri, Sep 25, 2020 at 9:55 AM Goutham Tholpadi

Re: Delete from Solr console fails

Thanks for your response Rahul! Yes, all the fields I tried with were indexed=true, but it did not work. Btw, when I try to today, I am no longer getting the "Connection lost" error. The delete command returns with status=success, however the document is not actually deleted when I check in the

Re: Delete from Solr console fails

Goutham, Is the field you are trying to delete by indexed=true in the schema ? If the uniqueKey is indexed=true, does delete by id work for you? ( uniqueKey:value) Also, instead of "Solr Command" if you choose the Document type as "XML" does it make any difference? Rahul On Thu, Sep 24, 2020 at

Re: Index Deeply Nested documents and retrieve a full nested document in solr

It is yes to both questions, but I am not sure if they play well together for historical reasons. For storing/parsing original JSON in any (custom) format: https://lucene.apache.org/solr/guide/8_6/transforming-and-indexing-custom-json.html (srcField parameter) For indexing nested children (with

Re: Solr 8.6.2 text_general

These are field definitions for _text_ and text, your original question was about the fields named "country"/"currency" and whatever type they mapped to. Your text/_text_ field is not actually returned to the browser, because it is "stored=false", so it is most likely a catch-all copyField

Re: Solr 8.6.2 text_general

In both it is the same In Solr 8.0.0 In Solr 8.6.2 On Thu, 24 Sep 2020 at 18:33, Alexandre Rafalovitch wrote: > I think that means your field went from multiValued to singleValued. > Double check your schema. Remember that multiValued flag can be set > both on the field itself and on its

Re: Solr 8.6.2 text_general

I think that means your field went from multiValued to singleValued. Double check your schema. Remember that multiValued flag can be set both on the field itself and on its fieldType. Regards, Alex P.s. However if your field is supposed to be single-valued, maybe you should treat it as a

Re: Any blog or url that explain step by step configure grafana dashboard to monitor solr metrics

You can refer the below url https://lucene.apache.org/solr/guide/7_3/monitoring-solr-with-prometheus-and-grafana.html On Thu, 24 Sep, 2020, 8:25 am yaswanth kumar, wrote: > Can some one post here any blogs or url where I can get the detailed steps > involved in configuring grafana dashboard

Re: Difference in q.op param behavior between Solr 6.3 and Solr 8.5.2

In 6.3 it did that? It shouldn't have. q and fq shouldn't share parameters. fq's themselves shouldn't, IMO, have global defaults. fq's need to be stable and often uniquely specified kinds of constraining query parsers ({!terms/term/field,etc}) or rely on basic Lucene query parser syntax

Re: Difference in q.op param behavior between Solr 6.3 and Solr 8.5.2

Is there a way to set default operator as AND for fq parameter in Solr 8.5.2 now? On Tue, Sep 22, 2020 at 7:44 PM gnandre wrote: > In 6.3, q.op param used to affect q as well fq param behavior. E.g. if > q.op is set to AND and fq is set to id:(1 2 3), no results will show up but > if it is set

Re: Solr 8.6.2 - Solr loaded a deprecated plugin/analysis

On 9/22/2020 10:22 PM, Anuj Bhargava wrote: How to solve this issue? How to replace it? SolrResourceLoader Solr loaded a deprecated plugin/analysis class [solr.DataImportHandler]. Please consult documentation how to replace it accordingly. That is a generic message about using deprecated

Re: TimeAllowed and Partial Results

TimeAllowed stops looking when the timer expires. If it hasn’t found any docs with a non-zero score by then, you’ll get zero hits. It has to be this way, because Solr doesn’t know whether a doc is a hit until Solr scores it. So this is normal behavior, assuming that some part of the processing

Re: Many small instances, or few large instances?

Thanks, Erick. I should probably keep a tally of how many beers I owe you ;-) On 21/09/2020 14:50, Erick Erickson wrote: > In a word, yes. G1GC still has spikes, and the larger the heap the more > likely you’ll be to encounter them. So having multiple JVMS rather than one > large JVM with a

Re: How to use query function inside a function query in Solr LTR

This is solved by using local parameters. So {!func}sub(num_tokens_int,query({!dismax qf=field_name v=${text}})) works On Mon, Sep 21, 2020 at 7:43 PM krishan goyal wrote: > Hi, > > I have use cases of features which require a query function and some more > math on top of the result of the

Re: Autoscaling Rule for replica distribution across zones

Hi, I also tried this 2 rules and I still have all replicas of all shards of the collection created in one single zone curl 'http://localhost:8983/api/cluster/autoscaling' -H 'Content-type:application/json' -d '{ "set-policy": { "policyzone": [ {"replica": "#EQUAL", "shard": "#EACH",

Re: Many small instances, or few large instances?

In a word, yes. G1GC still has spikes, and the larger the heap the more likely you’ll be to encounter them. So having multiple JVMS rather than one large JVM with a ginormous heap is still recommended. I’ve seen some cases that used the Zing zero-pause product with very large heaps, but they

Re: Issues deploying LTR into SolrCloud

Not sure how solr cloud works but if your still facing issues, can try this 1. Deploy the features and models as a _schema_feature-store.json and _schema_model-store.json file in the right config set. 2. Can either deploy to all nodes (works for me) or add these files to confFiles in /replication

Re: Solr training

Hi Matthew & all, Why not? Try the code 'evenearlier' for a further discount! (Oh and we extended the earlybird period for another week). Cheers Charlie On 17/09/2020 21:00, matthew sporleder wrote: Is there a friends-on-the-mailing list discount? I had a bit of sticker shock! On Wed,

Re: NPE Issue with atomic update to nested document or child document through SolrJ

11 M 06 83 33 57 95 Efrank@reddata.nl<mailto:frank@reddata.nl> Van: Alexandre Rafalovitch Datum: donderdag, 17 september 2020 om 21:07 Aan: solr-user Onderwerp: Re: NPE Issue with atomic update to nested document or child document through SolrJ The missing unde

Re: NPE Issue with atomic update to nested document or child document through SolrJ

Met vriendelijke groet / Kind regards, Frank Vos Servicedesk medewerker T036 760 07 11 M 06 83 33 57 95 Efrank@reddata.nl<mailto:frank@reddata.nl> Van: Alexandre Rafalovitch Datum: donderdag, 17 september 2020 om 21:07 Aan: solr-user Onderwerp: Re: NPE Issue with

Re: Pining Solr

Your builder parameter should be up to the collection, so only "http://testserver-dtv:8984/solr/cpsearch;. Then, on your Query object, you set query.setRequestHandler("/select_cpsearch") as per

Re: Pining Solr

Well, this is doesn’t look right at all: /solr/cpsearch/select_cpsearch/select It should just be: /solr/cpsearch/select_cpsearch Best, Erick > On Sep 18, 2020, at 3:18 PM, Steven White wrote: > > /solr/cpsearch/select_cpsearch/select

Re: Pining Solr

Hi Erick, I'm on Solr 8.6.1. I did further debugging into this and just noticed that my search is not working too now (this is after I changed the request handler name from "select" to "select_cpsearch"). I have this very basic test code as a test which I think revailes the issue: try

Re: Pining Solr

This looks kind of confused. I’m assuming what you’re after is a way to get to your select_cpsearch request handler to test if Solr is alive and calling that “ping”. The ping request handler is just that, a separate request handler that you hit by going to http://sever:port/solr/admin/ping.

Re: Fetched but not Added Solr 8.6.2

Thanks Shawn, it worked. However, I am getting the message - *The solrconfig.xml file for this index does not have an operational DataImportHandler defined!* The following lines are inserted in the solrconfig.xml db-data-config.xml On Fri, 18 Sep 2020 at

Re: Fetched but not Added Solr 8.6.2

On 9/18/2020 1:27 AM, Anuj Bhargava wrote: In managed schema, I have Still getting the following error- org.apache.solr.common.SolrException: Document is missing mandatory uniqueKey field: id The problem is that the document that has been fetched with DIH does NOT have a field named id.

Re: How to remove duplicate tokens from solr

Hi all, I have found the below details in stackoverflow but not sure how to include the jar. Can any one help with this? I've created a new filter class from "FilteringTokenFilter". The task is pretty simple. I would check before adding into the list. I have created a simple plugin Eliminate

Re: Fetched but not Added Solr 8.6.2

In managed schema, I have Still getting the following error- org.apache.solr.common.SolrException: Document is missing mandatory uniqueKey field: id at org.apache.solr.update.AddUpdateCommand.getIndexedId(AddUpdateCommand.java:124) at

Re: Solr training

Is there a friends-on-the-mailing list discount? I had a bit of sticker shock! On Wed, Sep 16, 2020 at 9:38 AM Charlie Hull wrote: > > I do of course mean 'Group Discounts': you don't get a discount for > being in a 'froup' sadly (I wasn't even aware that was a thing!) > > Charlie > > On

Re: How to remove duplicate tokens from solr

But not sure why these type of search string is causing high cpu utilization. On Fri, 18 Sep, 2020, 12:49 am Rahul Goswami, wrote: > Is this for a phrase search? If yes then the position of the token would > matter too and not sure which token would you want to remove. "eg > "tshirt hat

<    5   6   7   8   9   10   11   12   13   14   >