Hi,
If data are in json format, you should use jq -S
https://stackoverflow.com/a/38210345/5998915
Regards
Dominique
Le lun. 28 sept. 2020 à 18:30, gnandre a écrit :
> Hi,
>
> I have a use-case where I want to compare stored fields values of Solr
> documents from two different Solr instances.
Hi Erick,"You still haven’t given an example of the results you’re seeing
that are unexpected".
I will give an example of the data I received. Before starting data update I
have:
solrCloud: Expected series criteria:386062
Collected series: 386062
Number of requests: 40
Collected unique series: 3
Hello all,
Our Solr web ui (/solr/#/) doesn't show query results if it takes longer than,
say 3-4 seconds. When I look at the browser console, I see the request is
getting cancelled. I went through the javascript code but didn't see a part
that cancels the request after a couple of seconds. D
In our index, we have few fields defined as `ExternalFileField` field type.
We decided to use docValues for such fields. Here is the field type
definition
OLD => (ExternalFileField)
NEW => (docValues)
After this modification we started getting the following `timeout warning`
messages:
```The
Let’s see the query. My bet is that you are _searching_ against the field and
have indexed=false.
Searching against a docValues=true indexed=false field results in the
equivalent of a “table scan” in the RDBMS world. You may use
the docValues efficiently for _function queries_ to mimic some
searc
Solr follows the ASF policy for reporting vulnerabilities, described in this
page on our website: https://lucene.apache.org/solr/security.html. This page
also lists known vulnerabilities that have been addressed, with their
mitigation steps.
Scanning tools are commonly full of false positives s
Hey Erick,
In cases for which we are getting this warning, I'm not able to extract the
`exact solr query`. Instead logger is logging `parsedquery ` for such cases.
Here is one example:
2020-09-29 13:09:41.279 WARN (qtp926837661-82461) [c:mycollection
s:shard1_0 r:core_node5 x:mycollection_s
Hi Solr Experts!
We are moving from Solr 6.5.1 to Solr 8.5.0 and having a problem with long
query, which has a search text plus many OR and AND conditions (all in one
place, the query is about 20KB long).
For the same set of data (about 500K docs) and the same schema the query in
Solr 6 return r
What do the debug versions of the query show between two versions?
One thing that changed is sow (split on whitespace) parameter among
many. It is unlikely to be the cause, but I am mentioning just in
case.
https://lucene.apache.org/solr/guide/8_6/the-standard-query-parser.html#standard-query-pars
Hi
I have read in the mailings list that we should try to avoid using stop
words.
I have a use case where I would like to know if there is other
alternative solutions beside using stop words.
There is business requirement to return zero result when the search is
cigarette related words and
I am not sure why you think stop words are your first choice. Maybe I
misunderstand the question. I read it as that you need to exclude
completely a set of documents that include specific keywords when
called from specific module.
If I wanted to differentiate the searches from specific module, I
w
Thanks for sharing this Anshum. Day 1 had some really interesting sessions.
Missed out on a couple that I would have liked to listen to. Are the
recordings of these sessions available anywhere?
-Rahul
On Mon, Sep 28, 2020 at 7:08 PM Anshum Gupta wrote:
> Hey everyone!
>
> ApacheCon at Home 2020
12 matches
Mail list logo
