Re: OR query working on Leader Node only

2018-08-09 Thread Shawn Heisey
On 8/9/2018 7:31 PM, tapan1707 wrote: I believe correct formats for OR search query are the following: id:(id1 or id2) id:id1 or id:id2 The correct form for an OR query is an uppercase "OR".  The lowercase "or" won't do the same thing -- typically it will be interpreted as just another search

Re: Solr Multiple Hostnames

2018-08-09 Thread Shawn Heisey
On 8/9/2018 8:37 PM, Kelly Rusk wrote: Is it possible to have mutiple hostnames for a single Solr node, akin to an IIS Website with multiple host headers? Solr doesn't pay attention to any host header in the HTTP request.  If Solr receives the traffic on its TCP port, it will answer, no matte

Solr Multiple Hostnames

2018-08-09 Thread Kelly Rusk
Hello all, Is it possible to have mutiple hostnames for a single Solr node, akin to an IIS Website with multiple host headers? My scenario is that I have a Master/Slave configuration with a load balancer in front. The Master has a url of https://master-solr.mydomain.com and the Slave a url of

OR query working on Leader Node only

2018-08-09 Thread tapan1707
I believe correct formats for OR search query are the following: id:(id1 or id2) id:id1 or id:id2 When I tried searching with "id:id1 or id2", it is parsing the query into "id:id1 or _text_:id2" where _text_ is the field from solr's default config set. Also, for this, I need to add the _text_ fiel

Re: Sort by payload field desc fails

2018-08-09 Thread Anurag Nilesh
I was seeing the issue with payload sort on SOLR 6.6.0 version. This issue resolved when we started using 7.4.0 version. On Tue, Jul 3, 2018 at 5:34 PM, Anurag Nilesh wrote: > Hi, > I was trying out extracting the payload field value for a payload field > type and then doing a sort based on that

4 days and no solution - please help on Solr

2018-08-09 Thread ☼ R Nair
Dear all, I have tried my best to do it - searched all Google. But I an=m unsuccessful. Kindly help. We have a solo environment. Its secured with userid and password. I used CloudSolrClient.Builder(solrURLs).withHttpClient(mycloseablehttpclient) method to access it. The url is of the form http:/

RE: sharding and placement of replicas

2018-08-09 Thread Oakley, Craig (NIH/NLM/NCBI) [C]
Okay, I've tried again with two nodes running Solr7.4 on different hosts. Before SPLITSHARD, collectest2_shard1_replica_n1 was on the host nosqltest22, and collectest2_shard1_replica_n3 was on the host nosqltest11 After running SPLITSHARD (on the nosqltest22 node), only collectest2_shard1_0_rep

Re: Leader is stuck on offline node

2018-08-09 Thread Erick Erickson
REBALANCELEADERS and related do not force a leader to be elected, rather it tries to respect the preferredLeader property if it's been set in the replica's properties. Really that's only intended for situations where there are many 10s of leaders (perhaps hundreds) that happen to be on the same hos

RE: [External] [Solr 7.1.0] spellcheck.maxCollationTries > 0 no results

2018-08-09 Thread agorriz
Thanks James, I found a solution for my problem, using spellcheck.q=spellcheck_en:halogan%20balbs seems to work. But I would expect it to work without needing to set the spellcheck field on the query (it is already configured on solrconfig.xml) text_spell default

Re: [elevated] document transformer doesn't work with 7.4 version

2018-08-09 Thread Alexandre Rafalovitch
Did you use new schema definitions? Perhaps this is related: https://issues.apache.org/jira/browse/SOLR-11770 Otherwise, perhaps it has been fixed by https://issues.apache.org/jira/browse/SOLR-11865 (in upcoming 7.5, you could do a build from source to test it). Regards, Alex. On 9 August 201

[elevated] document transformer doesn't work with 7.4 version

2018-08-09 Thread Georgy Khotyan
Hello. I've found the problem: Request with fl=[elevated] returns NullPointerException when Solr 7.4 used. It works with all older versions. Example: http://localhost:8983/solr/my-core/select?q=*:*&enableElevation=true&elevateIds=1,2,3&forceElevation=true&fl=[elevated] Is it a bug of 7.4 version

RE: [External] [Solr 7.1.0] spellcheck.maxCollationTries > 0 no results

2018-08-09 Thread Dyer, James
It doesn't appear to me that the collator works with "spellcheck.q". Looking at the unit test (SpellCheckCollatorTest.java), this is not a use-case that is being tested. I opened https://issues.apache.org/jira/browse/SOLR-12650 to track this bug. As a workaround, you can remove "spellcheck.q"

Re: Json Facets in version 7

2018-08-09 Thread Chris Ulicny
I missed the change previously when looking at v7.3 release notes. The fix for SOLR-12064 should be the solution. Will upgrade to more recent release and retest. On Thu, Aug 9, 2018 at 8:39 AM Chris Ulicny wrote: > Additionally, the "limit: -1"

Re: Json Facets in version 7

2018-08-09 Thread Chris Ulicny
Additionally, the "limit: -1" seems to work as expected if we are only doing a single aggregation in the nested facet: "...facet:{sum_val1:"sum(value1)"}}}" On Thu, Aug 9, 2018 at 8:24 AM Chris Ulicny wrote: > Hi all, > > We are in the process of upgrading from version 6.3.0 to version 7.2.1 and

Json Facets in version 7

2018-08-09 Thread Chris Ulicny
Hi all, We are in the process of upgrading from version 6.3.0 to version 7.2.1 and have found something that doesn't seem to work with the json facets any more. The query is below /select?q=*:*&wt=xml&indent=off&rows=0&fq=groupid:(4572 4573)+AND+gmttimestamp:[2018-08-05T00:00:00Z+TO+2018-08-07T00

Atomic update deletes deduplication signature

2018-08-09 Thread Thomas Eckart
Hello, I am having trouble when doing atomic updates in combination with SignatureUpdateProcessorFactory (on Solr 7.2). Normal commits of new documents work as expected and generate a valid signature: curl "$URL/update?commit=true" -H 'Content-type:application/json' -d '{"add":{"doc":{"id":

Leader is stuck on offline node

2018-08-09 Thread Bernd Fehling
Something strange happened, in my Solr 6.6.5 cloud (1 collection, 5 shards, 3 replica) the leader is stuck on offline node for shard3. I already tried setting property preferredLeader to true on the active core_node5 and called REBALANCELEADERS but nothing happened. In the response of REBALANCELE