Re: querying on field of type string doesn't work as expected

The only thing that works is this: {!term f=MyCustomField}Some Text Thanks On Thu, Nov 15, 2018 at 7:13 PM Erick Erickson wrote: > Well, there's little likelihood that Solr will be changed this way. If > your field were a text-based field that had a lowercase as part of > it's analysis chain,

Re: querying on field of type string doesn't work as expected

That’s correct - the original source of my data which I was crawling had 160 as space. This took a while to find. :) Solr is working fine. Thank you ! On Tue, 20 Nov 2018 at 1:28, Shawn Heisey wrote: > On 11/19/2018 3:31 PM, Angel Todorov wrote: > > the *real* issue is that SOLR expects a

Re: Question about elevations

one more thing to add, if there are fqs, they will be evaluated as well. Edward Ribeiro 于2018年11月19日周一 下午1:24写道： > Just complementing Alessandro's answer: > 1. the elevateIds are inserted into the query, server side (a query > expansion indeed); > 2. the query is executed; > 3. elevatedIds (if

Re: querying on field of type string doesn't work as expected

You can always replace String type with Text type and KeywordAnalyzer definition. That keeps the whole input as one token, but still allows to modify (e.g. normalize spaces with PatternReplaceCharFilterFactory) or even one of the ICU filters (warning: ICU is dark magic...) Regards, Alex. On

Re: querying on field of type string doesn't work as expected

the *real* issue is that SOLR expects a character with a code of 160 for space, while the standard space as typed from a keyboard has a code of 32. Both appear exactly the same. Here's where the issue comes from. If i generate the 160 space, and copy paste it, it works fine for string even like

Re: querying on field of type string doesn't work as expected

On 11/19/2018 3:31 PM, Angel Todorov wrote: the *real* issue is that SOLR expects a character with a code of 160 for space, while the standard space as typed from a keyboard has a code of 32. Both appear exactly the same. Here's where the issue comes from. If i generate the 160 space, and copy

Error:Missing Required Fields for Atomic Updates

Hi, Using Solr 7.5.0. While performing atomic updates on a document on Solr Cloud using SolJ getting exceptions "Missing Required Field". Please let me know the solution, would not want to update the required fields during atomic updates. Thanks Rajeswari

Re: Error:Missing Required Fields for Atomic Updates

What’s your update query? You need to provide the unique id field of the document you are updating. Rahul On Mon, Nov 19, 2018 at 10:58 PM Rajeswari Kolluri < rajeswari.koll...@oracle.com> wrote: > Hi, > > > > > > Using Solr 7.5.0. While performing atomic updates on a document on Solr >

Re: Error:Missing Required Fields for Atomic Updates

What is the Router name for your collection? Is it "implicit" (You can know this from the "Overview" of you collection in the admin UI) ? If yes, what is the router.field parameter the collection was created with? Rahul On Mon, Nov 19, 2018 at 11:19 PM Rajeswari Kolluri <

Able to search with indexed=false and docvalues=true

I am using SolrCloud 7.2.1. My understanding is that setting docvalues=true would optimize faceting, grouping and sorting; but for a field to be searchable it needs to be indexed=true. However I was dumbfounded today when I executed a successful search on a field with below configuration: However

Re: Able to search with indexed=false and docvalues=true

I've noticed this too, but I think it's more a side effect than something usable for the reasons you outlined. Searching a docValues field is akin to a "table scan", the uninverted structure is totally unsuited for searching. It works, but as you've found out it's unusably slow for any decent

Re: Error:Missing Required Fields for Atomic Updates

Update Handler expect all the required fields to be passed in even for the atomic update request payload. https://github.com/apache/lucene-solr/blob/branch_7_5/solr/core/src/java/org/apache/solr/update/DocumentBuilder.java Hope this helps! // Now validate required fields or add default values

Re: Solr query response time analysis

Hi Rajdeep, For production-deployment at my company, we are using prometheus exporter, https://github.com/noony/prometheus-solr-exporter. You can start the exporter along with solr server and the exporter will collect important metrics from solr. By the way, you need to install and configure

RE: Error:Missing Required Fields for Atomic Updates

Hi Rahul Below is part of schema , entityid is my unique id field. Getting exception missing required field for "category" during atomic updates. entityid Thanks Rajeswari -Original Message- From: Rahul Goswami

Re: Solr Cloud - Store Data using multiple drives

On 11/19/2018 6:44 AM, Tech Support wrote: 1. If the disk free space is completed, is it possible to configure another drive? Which means, if C drive free space is over need to configure the D drive. I need to read the data from both C and D drives. There is no automated way to do this.

Re: Phrase query as feature in LTR not working

Hi AshB, from what I see, this is the expected behavior. You pass this efi to your "isPook" feature : efi.query=thrones%20of%20game*. Then you calculate: { "name" : "isPook", "class" : "org.apache.solr.ltr.feature.SolrFeature", "params" : { "fq": ["{!type=edismax qf=*text*

Re: AW: Solr suggestions, best practices

I have done extensive work on auto suggestion, some additional resource from my company blog : https://sease.io/2015/07/solr-you-complete-me.html

Re: Question about elevations

As far as I remember the answer is no. You could take a deep look into the code, but as far as I remember the elevated doc Ids must be in the index to be elevated. Those ids will be added to the query built, a sort of query expansion server side. And then the search executed. Cheers -

Solr query response time analysis

Hi all, Please suggest, how can I analyze the time taken by a solr query? Is there any tool for analyzing the query response time.I f there is any way to do this please suggest.

Apache Tomcat version with an integrated jre version for Java 11

Hi Apache SOLR team, We belong to SAP Identity Manager Team in Accenture company. We are users of Solr that makes use of Apache Tomcat (our current version is Apache Tomcat 8.5.23). Every time there is a new Java version, to avoid vulnerabilities issues, we always update the Java Runtime

Re: Solr query response time analysis

Rajdeep, Not an external tool, but there is the option of using the "debug" parameter in the Solr query that can be used at least as a starting point for looking at the query timing. https://lucene.apache.org/solr/guide/6_6/common-query-parameters.html#CommonQueryParameters-ThedebugParameter

Re: Restrict search on term/phrase count in document.

I agree with Alexandre, it seems suspicious. Anyway, if you want to query for single term frequencies occurrence you could make use of the function range query parser : https://lucene.apache.org/solr/guide/6_6/other-parsers.html#OtherParsers-FunctionRangeQueryParser And the function: termfreq

Live publishing and solr performance optimization

Hi, We are in the process for live Publishing document in solr and the same time we have to maintain the search performance. Total existing docs : 120 million Expected data for live publishing : 1 million For every 1 hour, we will get 1m docs to publish in live to the hot solr collection, can

Re: Soft commits and new Searcher

Hi Walter, A searcher has an immutable (stale) view of the index of when it was created. Therefore, a soft commit always open a new searcher, because this new searcher will reflect the changes in the index since the last commit. When you are doing a hard commit you have the option of not opening

Re: Sort index by size

One more tidbit: are you really sure you need all 20 fields to be indexed and stored? Do you really need all those 20 fields? See this blog post, for example: https://www.garysieling.com/blog/tuning-solr-lucene-disk-usage On Mon, Nov 19, 2018 at 1:45 PM Walter Underwood wrote: > > Worst case is

Re: Apache Tomcat version with an integrated jre version for Java 11

On 11/19/2018 10:04 AM, Santolaya García, E. wrote: We belong to SAP Identity Manager Team in Accenture company. We are users of Solr that makes use of Apache Tomcat (our current version is Apache Tomcat 8.5.23). Every time there is a new Java version, to avoid vulnerabilities issues, we

Re: OR query strange results

Hello, any ideas on this? Thank you Danilo On 16/11/18 08:48, Danilo Tomasoni wrote: Thank you for your reply Erick. I've thought about termsquery but it doesn't support phrase search AFAIK, and I want to query for near words like "Mycobacterium tuberculosis" and also i would like to use

Sort index by size

Hello, I have a solr core with some 20 fields in it.(all are stored and indexed). For an environment, the number of documents are around 0.29 million. When I run the full import through DIH, indexing is completing successfully. But, it is occupying the disk space of around 5 GB. Is there a

Pagination with grouping in solr

Document structure of solr document is as mentioned below now i need to get the document having event_name="product view" and group it by email so that email is not duplicate.Now on listing the email how may paginate the unique email.As the query return total number of document not the count of

Re: Sort index by size

On 11/19/2018 2:31 AM, Srinivas Kashyap wrote: I have a solr core with some 20 fields in it.(all are stored and indexed). For an environment, the number of documents are around 0.29 million. When I run the full import through DIH, indexing is completing successfully. But, it is occupying the

Re: Sort index by size

Also a full import, assuming the documents were already indexed, will just double your index size until a merge/optimize is ran since you are just marking a document as deleted, not taking back any space, and then adding another completely new document on top of it. On Mon, Nov 19, 2018 at 10:36

Re: Sort index by size

Worst case is 3X. That happens when there are no merges until the commit. With tlogs, worst case is more than that. I’ve seen humongous tlogs with a batch load and no hard commit until the end. If you do that several times, then you have a few old humongous tlogs. Bleah. wunder Walter

Solr Cloud - Store Data using multiple drives

Hello Solr Team, I am using Solr 7.5. , Indexed data stored in the Solr Installation directory. I need the following features, Is it possible to achieve the following scenarios in SOLR Cloud? 1. If the disk free space is completed, is it possible to configure another drive? Which

Re: Solr Cloud - Store Data using multiple drives

This seems very similar to: https://lists.apache.org/thread.html/48b6dcb20058de29936616633b88d21e1b6f6a32bc968d161eae4a21@%3Csolr-user.lucene.apache.org%3E Regards, Alex. On Mon, 19 Nov 2018 at 11:15, Tech Support wrote: > > Hello Solr Team, > > > > I am using Solr 7.5. , Indexed data stored

Re: Question about elevations

Just complementing Alessandro's answer: 1. the elevateIds are inserted into the query, server side (a query expansion indeed); 2. the query is executed; 3. elevatedIds (if found) are popped up to the top of the search results via boosting; Edward On Mon, Nov 19, 2018 at 3:41 PM Alessandro