Re: Single query to get the count for all individual collections

2019-01-21 Thread Joel Bernstein
Streaming Expressions can do this: plist(stats(collection1, q="*:*", count(*)), stats(collection2, q="*:*", count(*)), stats(collection2, q="*:*", count(*))) The plist function is a parallel list of expressions. It will spin each expression off in it's own thread and concatenate

Re: Get MLT Interesting Terms for a set of documents corresponding to the query specified

2019-01-21 Thread Joel Bernstein
You find the significantTerms streaming expressions useful: https://lucene.apache.org/solr/guide/7_6/stream-source-reference.html#significantterms Joel Bernstein http://joelsolr.blogspot.com/ On Mon, Jan 21, 2019 at 3:02 PM Pratik Patel wrote: > Aman, > > Thanks for the reply! > > I have

Re: Difference in queryString and Parsed query

2019-01-21 Thread Walter Underwood
There are many, many problems with this analyzer chain definition. This is a summary of the indexing chain: * WhitespaceTokenizerFilter * LowerCaseFilter * SynonymFilter (with ignoreCase=true after lower-casing everything) * StopFilter (we should have stopped using stopwords 20 years ago) *

Re: Solr Cloud Issue

2019-01-21 Thread Erick Erickson
I think the -c option should be unnecessary if -z is supplied. And it works on the other machines. Take a look at the solr.log files on the nodes that doesn't start, that might give more information. Or start with the -f option, that'll log to the foreground and you'll probably see a better

Re: Warnings in Zookeeper Server Logs

2019-01-21 Thread Joe Lerner
After a long slog, I am now able to answer my own question, just in case anybody is listening. We determined that when we deploy our application to Tomcat using the Tomcat deploy service, which happens when we deploy with Jenkins and Ansible, these errors start. Conversely, if we re-start Tomcat

Re: Get MLT Interesting Terms for a set of documents corresponding to the query specified

2019-01-21 Thread Pratik Patel
Aman, Thanks for the reply! I have tried with corrected query but it doesn't solve the problem. also, my tags filter matches multiple documents, however the interestingTerms seems to correspond to just the first document. Here is an example of a query which matches 1900 documents.

Re: Get MLT Interesting Terms for a set of documents corresponding to the query specified

2019-01-21 Thread Aman Tandon
I see two rows params, looks like which will be overwritten by rows=2, and then your tags filter is resulting only one document. Please remove extra rows and try. On Mon, Jan 21, 2019, 08:44 Pratik Patel Hi Everyone! > > I am trying to use MLT request handler. My query matches more than one >

Re: Error using collapse parser with /export

2019-01-21 Thread Joel Bernstein
I haven't had time to look into the details of this issue but it's not clear that these two features will be able to be used together. Although that it would be nice if the could. A couple of questions about your use case: 1) After collapsing is it not possible to use the /select handler? 2)

Re: Single query to get the count for all individual collections

2019-01-21 Thread Jens Brandt
Hi, maybe adding =true might help. In case of SolrCloud this gives you numFound for each shard. Regards, Jens > Am 10.01.2019 um 04:40 schrieb Zheng Lin Edwin Yeo : > > Hi, > > I would like to find out, is there any way that I can send a single query > to retrieve the numFound for all the

Re: Solr Cloud Issue

2019-01-21 Thread Edward Ribeiro
AFAIK, to start as SolrCloud you should add "-c" switch option as below: bin/solr start -c -z 192.168.1.6:2181,192.168.1.7:2181, 192.168.1.102:2181/solr Otherwise, you'll be starting as standalone Solr instance. Edward On Mon, Jan 21, 2019 at 3:15 PM wrote: > Hello, > > I am configuring the

Solr Cloud Issue

2019-01-21 Thread vinod.suthar
Hello, I am configuring the solrCloud setup at my local network. I have setup zookeeper on three machines and created chroot bin/solr zk mkroot /solr -z 192.168.1.6:2181,192.168.1.7:2181,192.168.1.102:2181 Then starting solr with command on all three machine bin/solr start -z

Re: REBALANCELEADERS is not reliable

2019-01-21 Thread Bernd Fehling
Hi Erik, patches and the new comments look good. Unfortunately I'm at 6.6.5 and can't test this with my cloud. Replica (o.a.s.common.cloud.Replica) at 6.6.5 is to far away from 7.6 and up. And a backport for 6.6.5 is to much rework, if possible at all. Thanks for solving this issue. Regards,

Re: How to have the same SOLR cores for both 8983 and 8984 ports

2019-01-21 Thread Jan Høydahl
As I said before: "For us to help you more, you will have to provide more details on how you have installed and started Solr, where your SOLR_HOME is located etc". I am guessing that you start Solr with two different SOLR_HOMEs and thus will not see the existing cores. But then I don't even

Re: regarding debugging solr in eclipse

2019-01-21 Thread SAGAR INGALE
after running *'ant eclipse'* in the root folder of solr, I try to import the project in eclipse by selecting the solr home source directory, but no project is imported. do eclipse support ant out of the box? can we create a maven project from source and import it in eclipse? I tried to use *'ant

Re: Difference in queryString and Parsed query

2019-01-21 Thread Lavanya Thirumalaisami
Thank you Aman Deep  I tried removing the kstem filter factory and still get the same issue, but when i comment the Porterstemfilterfactory the character y does not get replaced.  On Monday, 21 January 2019, 11:16:23 pm AEDT, Aman deep singh wrote: Hi Lavanya, This is probably due

Re: Difference in queryString and Parsed query

2019-01-21 Thread Lavanya Thirumalaisami
thank you Mikhail. On Monday, 21 January 2019, 11:13:51 pm AEDT, Mikhail Khludnev wrote: querystring  is what goes into QPaser,  parsedquery  is LuceneQuery.toString() On Mon, Jan 21, 2019 at 3:04 PM Lavanya Thirumalaisami wrote: > Hi, > Our solr search is not returning expected

Re: Difference in queryString and Parsed query

2019-01-21 Thread Aman deep singh
Hi Lavanya, This is probably due to the kstem Filter factory it is removing the y charactor ,since the stemmer has rule of words ending with y . Regards, Aman Deep Singh > On 21-Jan-2019, at 5:43 PM, Mikhail Khludnev wrote: > > querystring is what goes into QPaser, parsedquery is >

Re: Difference in queryString and Parsed query

2019-01-21 Thread Mikhail Khludnev
querystring is what goes into QPaser, parsedquery is LuceneQuery.toString() On Mon, Jan 21, 2019 at 3:04 PM Lavanya Thirumalaisami wrote: > Hi, > Our solr search is not returning expected results for keywords ending with > the character 'y'. > For example keywords like battery, way,

Difference in queryString and Parsed query

2019-01-21 Thread Lavanya Thirumalaisami
Hi, Our solr search is not returning expected results for keywords ending with the character 'y'. For example keywords like battery, way, accessory etc. I tried debugging the solr query in solr admin console and i find there is a difference between query string and parsed query.

Re: Same field name cannot be added in newer Solr versions

2019-01-21 Thread Arunan Sugunakumar
@Jorn Franke In the link you shared, both replace and delete methods returns an exception if the field is not already there. I am wondering how to handle both cases mentioned below. - When a fresh collection is created, fieldnames and fieldtypes would not already exist. Hence they have to

Intermittent timeout on the Slave

2019-01-21 Thread damian.pawski
Hi All We are working with "Master -> 2 Slaves" configuration (BitNami Stack on Win2012 server). Recently we have started to get a timeout responses on our Slaves. The error is similar to the one below: "/A connection attempt failed because the connected party did not properly respond after a