Re: Case sensitive synonym value

Yes, Ignore case is set to true and it is working fine On 10-Aug-2017 12:43 AM, "Erick Erickson" wrote: You set ignoreCase="true" though, right? On Wed, Aug 9, 2017 at 8:39 AM, Aman Deep Singh wrote: > Hi Erick, > I tried even before going

Re: identifying source of queries

Suresh If you have a web app in front of Solr and it or Apache logs all requests then you should be able to match the log entries to the solr.log entries. That would tell you a source IP, but it might not help if the users are behind a nat firewall. But yes, you could look at the nat firewall

Re: Case sensitive synonym value

You set ignoreCase="true" though, right? On Wed, Aug 9, 2017 at 8:39 AM, Aman Deep Singh wrote: > Hi Erick, > I tried even before going to lowercase factory value is in lowercase > > this is the analysis tab result for the query iwatch > where

SolrServerException: No live SolrServers available to handle this request

We occasionally (frequently for some searches) see this exception. All replicas appear up and stable when viewed from the SolrAdmin Console The problem seems to be intermittent, but too frequent by far! It's happening more for our Indian developers than for the US devs. We're hitting the same

Building Solr index from AEM using and ELB

I am looking for lessons learned or problems seen when building a Solr index from AEM using a Solr cluster with content passing through an ELB. Our configuration is AEM 6.1 indexing to a cluster of Solr servers running version 4.7.1. When building an index with a smaller data set - 4 million

Re: identifying source of queries

There is no need to change anything related to query parsers. A search component should be enough. On Wed, Aug 9, 2017 at 9:56 PM, suresh pendap wrote: > Thanks Shalin for the reply. > Do I need to also update the query parsers in order to handle the new query > param? >

Re: identifying source of queries

Thanks Shalin for the reply. Do I need to also update the query parsers in order to handle the new query param? I can build a custom component but dabbling with query parsers would be way too much for me to handle. Thanks Suresh On Tue, Aug 8, 2017 at 9:49 PM, Shalin Shekhar Mangar <

Re: Case sensitive synonym value

Hi Erick, I tried even before going to lowercase factory value is in lowercase this is the analysis tab result for the query iwatch where {"iwatch":["iWatch","appleWatch"]} is configured in managed synonym ST iwatch SF *applewatch* *iwatch* PRF applewatch iwatch PRF applewatch iwatch WDF

Re: Highlighting Performance improvement suggestions required - Solr 6.5.1

Have you attached JVisualVM or a similar tool for sampling when Solr is answering the requests with highlight? What relevant methods are coming up? On Wed, Aug 9, 2017 at 11:26 AM, sasarun wrote: > Hi Amrit, > > Thanks for the response. I did went through both and that is how

Re: JSON Logs in SOLR 5.x

Jackson should be in core/lib. find . -name "*.jar* | grep -i jackson ;) On Tue, Aug 8, 2017 at 3:44 PM, John Bickerstaff wrote: > I'm running Solr 5.x and have the need to push logs into AWS's kinesis > firehose. > > As I understand it, I need the logs to be in JSON

Re: Highlighting Performance improvement suggestions required - Solr 6.5.1

Hi Amrit, Thanks for the response. I did went through both and that is how I landed up with unified method for highlighter Thanks, Arun -- View this message in context:

Re: response time degradation with matchall queries / changin from SOLR 4.10 -> 6.x

Two questions: 1> did you completely re-index under 6x? My guess is "yes", since you jumped two major versions and 6x won't read a 4x index. If not you may be getting some performance degradation due to back-compat.. 2> Try turning =timing. that breaks down the time spent in each component and

Re: Case sensitive synonym value

Admin/analysis is a good place to start figuring this out. For instance, do you have lowerCaseFilter configured in your analysis chain somewhere that's doing the conversion? Best, Erick On Wed, Aug 9, 2017 at 5:34 AM, Aman Deep Singh wrote: > Hi, > I'm trying to use

Re: Highlighting Performance improvement suggestions required - Solr 6.5.1

Pardon I didn't go through details in configs and I guess you have already went through the recent talks on highlighters, still sharing if not: https://www.slideshare.net/lucidworks/solr-highlighting-at-full-speed-presented-by-timothy-rodriguez-bloomberg-david-smiley-d-w-smiley-llc

Highlighting Performance improvement suggestions required - Solr 6.5.1

Hi All, I found quite a few discussions on the highlighting performance issue. Though I tried to implement most of them, performance improvement was negative. Currently index count is really low with about 922 records . But the field on which highlighting is done is quite large data. Querying

TIKA-2440 Remove Furigana/phonetic as default for xlsx?

Solrians, We have a request to drop phonetic strings from xlsx as the default in Tika. I'm not familiar enough with Japanese to know if users would generally expect to be able to search on these as well as the original. The current practice is to include them. Any recommendations? Thank

Case sensitive synonym value

Hi, I'm trying to use the ManagedSynonyms with *ignoreCase=true* It is working fine for the identifying part but the problem comes in synonym value Suppose i have a synonym *iwatch ==>appleWatch,iWatch* If the user query is *iwatch (in any case)* it was identifying the synonym and replace the

Re: How many collections in a solrcloud are too many, how to determine this?

On Tue, 2017-08-08 at 13:35 -0500, Webster Homer wrote: > We have a Solrcloud environments that have 4 solr nodes and a 3 node > Zookeeper ensemble. All of the collections are configured to have 2 > shards with 2 replicas. Quick sanity check: Why 2 shards/collection? There is a non-trivial

Re:SOLR Learning to Rank Questions

Hello Joao! re: your first question, at present there is no direct way to use document hits in an external SQL database in a feature. Having said that, Solr has a so-called "ExternalFileField" type and using that in combination e.g. with the "FieldValueFeature" feature class should work, I

Re: How many collections in a solrcloud are too many, how to determine this?

I have a cluster (12 nodes) with 664 collection, 12 shards each and replication factor 2 The main bottleneck will be the zookeeper, it’s too easy overflow the overseer queue when a node ejects due a GC pause. Other problem is that the time to restart a node will increase from seconds to

response time degradation with matchall queries / changin from SOLR 4.10 -> 6.x

Hi, we are updating our SOLR infrastructure from version 4.10.2 to the latest 6.6. We realize a significant degradation of the response time while running match-all queries with facets (query in [1]) With version 4.x these kind of queries never took longer than 2000 ms. Now all of these queries