Re: Multivalue Field lookup

Thanks Edwin for the information. I will try highlighting.. On Sun, Apr 14, 2019 at 7:53 PM Zheng Lin Edwin Yeo wrote: > You need to set the field which you want to highlight in the hl.fl > parameter in your solrconfig.xml. > Highlighting can work in String field. > > Regards, > Edwin > > On

Re: Optimal RAM to size index ration

In linux the os will cache files in ram for quick reading. You can force the into ram by doing cat filename >/dev/null I do this with all my index files after a reboot and see better performance times on queries. Optimal ram is enough ram for all the indexes plus jvm plus 20 percent...

Mistake assert tips in FST builder ？

Hi， With current newest version, 9.0.0-snapshot，In Builder.UnCompileNode.addArc() function， found this line： assert numArcs == 0 || label > arcs[numArcs-1].label: "arc[-1].label=" + arcs[numArcs-1].label + " new label=" + label + " numArcs=" + numArcs; Maybe assert tips is ： assert numArcs

Re: Solr 8.0.0 Delta import add/delete data

Hi Anuj, I think it could be faster and cleaner to re-index, since the indexing takes only 4 minutes, and you require records to be deleted. Also, when you delete records in Solr, it only annotates them as deleted for the purpose of searching. The space used by those documents will be reclaimed

JSON Facet query to retrieve count all collections in Solr 8.0.0

Hi, I am using the below JSON Facet to retrieve the count of all the different collections in one query.

Re: Topic & Executor streaming expressions

This blog covers this topic is some depth: https://joelsolr.blogspot.com/2017/01/deploying-solrs-new-parallel-executor.html Joel Bernstein http://joelsolr.blogspot.com/ On Mon, Apr 15, 2019 at 11:19 AM Nazerke S wrote: > Hi everyone! > > Can anyone elaborate the topic and executor streaming

Solr 7 Nodes Suck in "Gone" State

Hi everyone, I ran into a situation in which a portion of the nodes in a Solr cluster were stuck in the GONE state (no ephemeral znode under /live_nodes) despite the Solr processes being alive and connected to the ZooKeeper tier. For context this a cluster running Solr 7.7.1 and ZooKeeper

Re: Highlighting

On 4/15/2019 11:36 AM, Mike Phillips wrote: I don't understand why highlighting does not return anything but the document id. I created a core imported all my data, everything seems like it should be working. From reading the documentation I expect it to show me highlight information for

Highlighting

I don't understand why highlighting does not return anything but the document id. I created a core imported all my data, everything seems like it should be working. From reading the documentation I expect it to show me highlight information for assetName around Potter, but I never get anything

Re: Optimal RAM to size index ration

All my queries from production environments, from real customers. I build query player that runs queries in the same time intervals like in PRODUCTION (all customers' queries with time intervals between them are saved in splunk). So all queries are distinct. -- Sent from:

Re: Optimal RAM to size index ration

To pile on a bit: Your *.fdt files contain “stored=true” data. By and large I ignore them for this discussion. Say I execute a query with “rows=10”. The fdt (and fdx) files are only accessed for the 10 docs returned so they have little impact on query time. Or rather, they have a reasonably

Topic & Executor streaming expressions

Hi everyone! Can anyone elaborate the topic and executor streaming expressions? What I understand from the Solr reference guide was that the topic allows for subscribing to a query. So that whenever I execute a query, it returns the tuples that are not seen yet ?? What about executor function?

Re: Optimal RAM to size index ration

I'm not that proficient with Solr.. I used it, but I'd yet have to fully dive into it, but this topic really interests me. In those 8 hour tests, does ALL information get accessed, or just partial? That could be a reason as to why you don't see any difference, that the test in that time period

Re: Shard and replica went down in Solr 6.1.0

Thanks for your reply. Get Outlook for Android From: Shawn Heisey Sent: Monday, April 15, 2019 12:40:59 AM To: solr-user@lucene.apache.org Subject: Re: Shard and replica went down in Solr 6.1.0 On 4/13/2019 9:29 PM, vishal patel

Re: Optimal RAM to size index ration

On 4/15/2019 7:25 AM, SOLR4189 wrote: I have a collection with many shards. Each shard is in separate SOLR node (VM) has 40Gb index size, 4 CPU and SSD. When I run performance checking with 50GB RAM (10Gb for JVM and 40Gb for index) per node and 25GB RAM (10Gb for JVM and 15Gb for index), I get

Re: Optimal RAM to size index ration

Hi, The recommendation to have RAM enough to place your entire index into memory is sort of worst case scenario (maybe better called the best case scenario) where your index is optimal and is fully used all the time. OS will load pages that are used and those that might be used to memory, so

CDCR - shards not in sync

Hi, I have a collection with 8 shards. 6 out of the shards are in sync but the other 2 are lagging behind by more than 10 plus hours. The tlog is only 0.5 GB in size. I have tried stopping and starting CDCR number of times but it has not helped. >From what i have noticed there is always a shard

Re: Optimal RAM to size index ration

No, I don't load index to RAM, but I run 8 hours queries, so OS must load necessary files (segments) to RAM during my tests. So in the case where I set 25GB for RAM, not all files will be loaded to RAM and I thought I'll see degradation in queries times, but I didn't -- Sent from:

Re: Filters and data cleansing

Hi Ken, What Solr returns is stored value which is original value. Analysis is applied and its result is stored as “index” and is used for searching. In order to get what you want, you have to move analysis at least one step earlier. It can be moved to update request processor chain where you

Re: Optimal RAM to size index ration

Do you load the index onto a RAM disk? I was under the impression that the JVM had everything contained that had to do with SOLR (I might be wrong), if thats the case and you are not loading the Index onto a ram disk then you won't see any difference. in either scenario, I don't think you would

Filters and data cleansing

hello experts. I have what is probably a simple question. Feels like it should be. i have some filters set up on INDEX. Lets say "lowercasefilterfactory" for instance. I understand the data will be indexed as lowercase but when i qry this same data its still in its original form. This works

Re: Set Basic Auth to CloudSolrStream

It may not be well supported Check out https://issues.apache.org/jira/browse/SOLR-9779 for some hints. Contributions welcome for improving how SolrJ can pass different auth credentials both for Streaming and search. -- Jan Høydahl, search

Optimal RAM to size index ration

Hi all, I have a collection with many shards. Each shard is in separate SOLR node (VM) has 40Gb index size, 4 CPU and SSD. When I run performance checking with 50GB RAM (10Gb for JVM and 40Gb for index) per node and 25GB RAM (10Gb for JVM and 15Gb for index), I get the same queries times

RE: Multivalue Field lookup

I use highlighting to get the list of "hits" from queries a multi-valued String fields. This works fine except when the query contains a range clause on that field. Even though the correct documents are found, the highlighted "hits" contain no data values. This is the reason for my Solr jira

NPE in CharsRefBuilder

Hello, I made a ConditionalTokenFilter filter and factory. Its Lucene based unit tests work really well, and i can see it is doing something, queries are differently analyzed based on some condition. But when debugging through the GUI i get the following: 2019-04-15 12:37:42.219 ERROR

Set Basic Auth to CloudSolrStream

Hi How can I set basic auth for CloudSolrStream? I couldn't find any documentation. Can someone please point me in the right direction? Thanks in advance, Navin

Re: nested documents performance

Hi Roi, I don’t know the details about your test, but trying to assume how it looks like and explain observed. With your flat test you are denormalising data, meaning creating data duplication so the resulting document set is larger. That means more fields/text for Solr/Lucene to analyse and to