Re: SQL Query with NOT (V 7.2.1)

with curl the result is the same: curl --data-urlencode "stmt=select id, name from collection where NOT (name = 'defaultmail')" 'http://server:port/solr/collection/sql' then the response is . . . { "id":113, "name":"defaultmail"} ,{ "id":109, "name":"defau

Re: SQL Query with NOT (V 7.2.1)

using integers in where clause with NOT is the same, though for that one using <> as workaround does the job - Zeki ama calismiyor... Calissa yapar... -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: SQL Query with NOT (V 7.2.1)

okay, found a work around for string fields for NOT queries This query does not filters for NOT: curl --data-urlencode "stmt=select id, name from collection where NOT (name = 'defaultmail')" 'http://server:port/solr/collection/sql' but after adding sth trivial i.e id > 0 o the where clause as c

join

join

RE: Correct join syntax

Hi You cannot join on two fields in SOLR as you do using SQL. Having the same situations I add new string field in collections(to concatenate Type and Id fields) and fill it at index time) Then join two collections on that field at query time -- Vadim -Original Message- From: dami...@gma

Device I/O trouble with solr 7.5

Hi folks, We are today running under SOLR 6.6 on our production environnement. On the end of august, i planned to upgrade SOLR to 7.4 (7.5 since that moment) but I encounter some trouble. Our master SOLR is replicated to a slave SOLR. I tried to upgrade the replica first, this is this one that mak

qf an pf parameters question

Hello, I use edismax qf and pf parameters, but for some field it would be desired to match ONLY if terms are in the same phrase. However, the qf parameter does not work with phrases, it is just for "filtering", and pf params affects only scoring. For example: qf=fulltext subject pf=fulltext s

Re: qf an pf parameters question

Hi, you may be interested in the mm [1] parameter, which in this case shout be set to 100%. However, if your requirements are more complicated than this, an mm=100% could have some unwanted side-effects because it's very "rigid". Best, Andrea [1] https://lucene.apache.org/solr/guide/6_6/the-

Re: Device I/O trouble with solr 7.5

On 10/16/2018 6:04 AM, zoolette wrote: We are today running under SOLR 6.6 on our production environnement. On the end of august, i planned to upgrade SOLR to 7.4 (7.5 since that moment) but I encounter some trouble. Our master SOLR is replicated to a slave SOLR. I tried to upgrade the replica fi

Re: Device I/O trouble with solr 7.5

Hi Shawn, Thanks for you're quick answer. I know it's not ideal to have mysql and SOLR on the same server. The use is perfect for replication, but actually is too short to handle a high query rate. And of course I didn't see the warning about pointed fields and performance on the documentation unti

Streaming rollUp vs Streaming facet

Hi Guys, I am trying to do an aggregation (sum) using streaming API. I have around 10 billion documents in my collection and every document has around 10 docValues. So streaming facet is taking close to 6 secs to respond with aggregation on 10 fields while streaming rollup is returning the respon

hdfs - documents missing after hard poweroff

Hi, Sometimes after a full poweroff of the solr cloud nodes, we see missing documents from the index. Is there anything about our setup or our recovery procedure that could cause this? Details are below: We see the following (somewhat random) behaviour: - add 10 documents to index. Commit. - q

Trying to retrieve two values from two different collections by sql (V 7.2.1)

I am trying to run a query like below to query against two different collections: select collection1.id as collection1id, collection2.id as collection2id from collection1 join collection2 on collection1.name = collection2.name where collection1.name = 'dummyname'; And as a result, I am only seein

Re: Trying to retrieve two values from two different collections by sql (V 7.2.1)

found out sth strange regarding this case. If i change one of the values into sth else, and the field names are not the same any more, then i can get the different values so the initial query was select *collection1.id* as collection1id, collection2.id as collection2id from collection1 join colle