Thank you for your reply Erick.
I've thought about termsquery but it doesn't support phrase search AFAIK,
and I want to query for near words like "Mycobacterium tuberculosis" and
also i would like to use
the tilde syntax "Mycobacterium tuberculosis"~2 .
Does it exists a
Best,
Erick
On Thu, Nov 15, 2018 at 7:52 AM Danilo Tomasoni wrote:
>
> Hello all,
>
> I'm performing some queries with a big list of terms in OR on our solr
> instance,
>
> and this odd situation happened
>
>
> - A. query with N alternatives returns ~130.000 docu
Hello all,
I'm performing some queries with a big list of terms in OR on our solr
instance,
and this odd situation happened
- A. query with N alternatives returns ~130.000 documents
- B. query with N-3 alternatives returns ~ 6.000.000 documents
N is relatively small in this case
ete-by-query.html>
You should do query and delete by ids in order to avoid issues caused by DBQ.
HTH,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticsearch Consulting Support Training - http://sematext.com/
> On 15 Nov 2018, at 06:09, RAKESH KOTE wrote:
and the autoCommit and softCommits are set
to 5 minutes. The SOLR cluster is supported by 3 ZK.
We are able to reach 5000/s updates and we are using solrj to index the data to
solr. We also delete the documents in each of the collection periodically using
solrj delete by query method(we use a non-id filed
Hi,
SolrJ is a client library that helps your application talk to Solr.
It's not a full application that can be run on its own. So the error
message you got is correct. It's not a standalone application. For
more information on using SolrJ, see the documentation here:
Hi,
i am currently using Apache Solr 6. i tried to launch SolrJ6 jar file in
eclipse oxygen by building a path and running it on jetty server but it
said selection does not contain main type. i also tried running java -jar
solr-solr-6.0.0.jar but it also said selection does not contaon main type.
.
A little further thought on this:
When using code to construct query strings, I think a situation can
easily arise where a query clause is optional, and the "()" string, with
or without whitespace between the parentheses, ends up in the generated
query.
I understand why the query parser
Shawn Heisey-2 wrote
> I don't know whether that actually is written anywhere. I suspect it's
> not.
>
> I do think that it is proper for empty parentheses to throw a syntax
> error. The text of the exception message is saying that the parser
> encountered the ) character at a point when it
Shawn Heisey-2 wrote
> I don't know whether that actually is written anywhere. I suspect it's
> not.
>
> I do think that it is proper for empty parentheses to throw a syntax
> error. The text of the exception message is saying that the parser
> encountered the ) character at a point when it
On 11/7/2018 5:10 AM, nettadalet wrote:
I get the following error:
org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError:
Cannot parse '((TITLE_Name_t:( la verita))) AND ((TITLE_Artist_t:( ))) AND
(TITLE_Type_e : "Audio")': Encountered " ")" ") "" at line 1, column 53.
I
We are using Solr 4.6
(yes, I know. We plan an update in the near future)
I get the following error:
org.apache.solr.common.SolrException: org.apache.solr.search.SyntaxError:
Cannot parse '((TITLE_Name_t:( la verita))) AND ((TITLE_Artist_t:( ))) AND
(TITLE_Type_e : "Audio")': Encountered " ")" ")
Phrase query is not working when applied in LTR.
Feature supplied is
{
"name" : "isPook",
"class" : "org.apache.solr.ltr.feature.SolrFeature",
"params" : {
"fq": ["{!type=edismax qf=text v=$qq}=\"${query}\&qu
Hi all,
Had a question about how parameters are combined/overlaid in the JSON
Query DSL. Ran into some behavior that struck me as odd/maybe-buggy.
The query DSL allows params to be provided a few different ways:
1. As query-params in the URI (e.g. "/select?fq=inStock:true")
2. I
fixed, mm will apply to any SHOULD clauses in the query. A
query of "a OR b" has two SHOULD clauses, and the mm value present in this
query requires all clauses to match, so it is effectively the same as "a AND b".
A potential workaround that appears to work: Detect whe
Hi,
What is your full query path or URL that you pass for the query?
And how is your setting like for the edismax in your solrconfig.xml?
Regards,
Edwin
On Fri, 26 Oct 2018 at 06:24, Nicky Mastin wrote:
>
> Oddity with edismax and queries involving boolean operators.
Oddity with edismax and queries involving boolean operators. Here's the
"parsedquery_toString" from two different queries:
input: "dog AND kiwi":
https://apaste.info/gaQl
input: "dog OR kiwi":
https://apaste.info/sBwa
Both queries return the same numbe
,
> Rohan Kasat
>
>
> On Mon, Oct 22, 2018 at 4:49 PM Shawn Heisey wrote:
>
> > On 10/22/2018 1:26 PM, Chris Ulicny wrote:
> > > There weren't any particular problems we ran into since the client that
> > > makes the queries to multiple collections previously would
Hi,
If I have 2 fields e.g. location and products then I might have 2
dictionaries
spell_location
spell_products
I cannot do for example spellcheck..q e.g.
spellcheck.spell_location.q=... only spellcheck.q=...
Does anyone have a workaround for this limitation?
Cheers
Dan
First one treats space as end of operation, so the second keyword is
searched against default field (id). Try putting the whole thing into the
quotes. Or use Field Query Parser:
https://lucene.apache.org/solr/guide/7_5/other-parsers.html#field-query-parser
Regards,
Alex.
On Wed, Oct 24, 2018
Hi,
I'm having troubles with the filter query on a multiple string field,
specifically with a space between words. Looking at the histogram and
values using Solr UI it correctly shows that the indexing stores the
string "Key case" as it should. However the following filter qu
he client that
> > makes the queries to multiple collections previously would query multiple
> > cores using the 'shards' parameter before we moved to solrcloud. We
> didn't
> > have any complicated sorting or scoring requirements fortunately.
> >
> > The one thing I re
On 10/22/2018 1:26 PM, Chris Ulicny wrote:
There weren't any particular problems we ran into since the client that
makes the queries to multiple collections previously would query multiple
cores using the 'shards' parameter before we moved to solrcloud. We didn't
have any complicated sorting
Thanks Chris.
This help.
Regards,
Rohan
On Mon, Oct 22, 2018 at 12:26 PM Chris Ulicny wrote:
> There weren't any particular problems we ran into since the client that
> makes the queries to multiple collections previously would query multiple
> cores using the 'shards' parameter
There weren't any particular problems we ran into since the client that
makes the queries to multiple collections previously would query multiple
cores using the 'shards' parameter before we moved to solrcloud. We didn't
have any complicated sorting or scoring requirements fortunately.
The one
Thanks Alex.
I check aliases but dint focused much , will try to relate more to my use
case and have a look again at the same.
I guess the specification of collection in the query should be useful.
Regards,
Rohan Kasat
On Mon, Oct 22, 2018 at 11:21 AM Alexandre Rafalovitch
wrote:
> Have
t; > I have a SolrCloud setup with multiple collections.
> > I have created say - two collections here as the data source for the
> both
> > collections are different and hence wanted to store them differently.
> > There is a use case , where i need to query both the co
Have you tried using aliases:
http://lucene.apache.org/solr/guide/7_5/collections-api.html#collections-api
You can also - I think - specify a collection of shards/collections
directly in the query, but there may be side edge-cases with that (not
sure).
Regards,
Alex.
On Mon, 22 Oct 2018
t; I have a SolrCloud setup with multiple collections.
> I have created say - two collections here as the data source for the both
> collections are different and hence wanted to store them differently.
> There is a use case , where i need to query both the collections and show
> u
Hi All ,
I have a SolrCloud setup with multiple collections.
I have created say - two collections here as the data source for the both
collections are different and hence wanted to store them differently.
There is a use case , where i need to query both the collections and show
unified search
ocs with matching words I've tried an
> extremely simplified case where a basic query (q=Field1:"foo") returns
> millions of results... however a MLT similar to the one I mention below,
> using a doc Id I know has "foo" in Field1 returns only the same Doc ID as
>
Thanks. There are many docs with matching words I've tried an
extremely simplified case where a basic query (q=Field1:"foo") returns
millions of results... however a MLT similar to the one I mention below,
using a doc Id I know has "foo" in Field1 returns only the same
Make sure your query has an “AND NOT id:your doc id”
Also be certain there are other documents that will meet your criteria for a
test case. Remember it’s unique words in your core/collection
On Oct 18, 2018, at 2:43 PM, John Bickerstaff
mailto:j...@johnbickerstaff.com>> wrote:
All,
All,
I am having trouble with a “more like this” query in Solr.
Here’s what I think should be happening:
1. Query contains Document ID (q=id:"942316176:9009:66
<http://10.157.117.55:10001/solr/BPS/select?==true=on=surnames,genders,givennames,birthlocations,deathlocations=true=id:%229
I believe the NOT should be working. But the joins won't work correctly.
Apache Calcite, which is parsing the query, is attempting to do the joins
but there are no test cases with joins at all. The official docs should say
that joins are not supported.
Joel Bernstein
http://joelsolr.blogspot.com
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
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
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,
I have been trying to get sql queries running, but having trouble while
dealing with the NOT queries.
Basically, the code looks like below
SolrQuery sqlQuery = new SolrQuery();
sqlQuery.setRequestHandler("/sql");
sqlQuery.set("stmt","select collection1.id as collection_1_id,
collection1.email
having troubles forming query. You have examples in
https://lucene.apache.org/solr/guide/6_6/function-queries.html#FunctionQueries-UsingFunctionQuery
<https://lucene.apache.org/solr/guide/6_6/function-queries.html#FunctionQueries-UsingFunctionQuery>
HTH,
Emir
--
Monitoring - Log Managemen
Hi,
I need help on using a custom function in filter query. Can anyone help on
how to get it wokring. Below is the problem statement.
Have a date field in long and a buffer time in milliseconds in the documents
which can vary.
startTime: 153886680
bufferTime: 86400
Need to query for docs
On 10/4/2018 7:10 AM, Greenhorn Techie wrote:
We have a requirement where we need to perform a group query in Solr where
results are grouped by user-name (which is a field in our indexes) . We
then need to filter the results based on numFound response parameter
present under each group
Hi,
We have a requirement where we need to perform a group query in Solr where
results are grouped by user-name (which is a field in our indexes) . We
then need to filter the results based on numFound response parameter
present under each group. In essence, we want to return results only where
earch solution architect
> Cominvent AS - www.cominvent.com
>
> > 21. sep. 2018 kl. 18:14 skrev Steve Rowe :
> >
> > Link correction - wrong fragment identifier in ref #5 - should be:
> >
> > [5]
> https://lucene.apache.org/solr/guide/7_4/other-parsers.html#function
ment identifier in ref #5 - should be:
>
> [5]
> https://lucene.apache.org/solr/guide/7_4/other-parsers.html#function-range-query-parser
>
> --
> Steve
> www.lucidworks.com
>
>> On Sep 21, 2018, at 12:04 PM, Steve Rowe wrote:
>>
>> Hi Sergio,
Link correction - wrong fragment identifier in ref #5 - should be:
[5]
https://lucene.apache.org/solr/guide/7_4/other-parsers.html#function-range-query-parser
--
Steve
www.lucidworks.com
> On Sep 21, 2018, at 12:04 PM, Steve Rowe wrote:
>
> Hi Sergio,
>
> Chris “Hoss
nction processCommit(cmd) { }
function processRollback(cmd) { }
function finish() { }
=
And your query could then look something like (replace "” with your
field name)[5][6]:
=
fq={!frange l=0
h=0}sub(unique_token_count_i,sum(termfreq(,’CENTURY’),termfreq(,’BANCORP’),termfreq(,‘INC’)))
How about sorting the tokens in alphabetical order both for indexing and query,
then using the sentinel trick.
Source text: CENTURY BANCORP, INC
Solr text: SENTINEL bancorp century inc SENTINEL
wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Sep
Hmm, I was suggesting to put TokenCountingFilter at the end of both
indexing and query chains for the same (e.g. name_count) field. Then,
the search would be something like (warning, major syntax errors):
.../select?
queryname=CENTURY BANCORP, INC&
q=*:*
fq={!eDisMax v=queryname mm=100%}name
A variant on Alexandre's approach is:
at index time, count the tokens that will be produced yourself (this
may be a little tricky, you shouldn't have WordDelimiterFilterFactory
in your analysis for instance).
Put the number of tokens in a separate field
At query time, you'd search q=+company_name
I think you can match everything in the query to the field using either
1) disMax/eDisMax with mm=100%
https://lucene.apache.org/solr/guide/7_4/the-dismax-query-parser.html#mm-minimum-should-match-parameter
2) Complex Phrase Query Parser with inOrder=false:
https://lucene.apache.org/solr/guide/7_4
ype string or text without any tokenization and then permute company
names in all reasonable combinations. Since company names should seldom
have more than half a dozen words, that might be practicable.
You then search with an exact match on that field. Make sure to quote
your query parameter
),
in "Relevant Search" the authors describe a cool approach using the so
called "Sentinel Tokens", which are symbolic tokens representing the
beginning and the end of a value (field value or query).
SENTINEL_BEGINSENTINEL_END
Those tokens could be injected at ind
tokens representing the
beginning and the end of a value (field value or query).
SENTINEL_BEGINSENTINEL_END
Those tokens could be injected at index and query time so the returned
matches will be effectively "exact" matches. Matching docs will have
exact values matching (that actually depends o
uot;.
I can't use exact match because the sequence of tokens may differ. Basically
I need to find results where the tokens are the same in any order and the
number of tokens match.
I have no idea if it's possible as include in the query the number of tokens
and solr field has that info within to m
Thanks, Shawn.
We made a change to add q.op=AND as a separate param and found a few issues.
For example, we have a query that filters out guest users in our product.
It boils down to:
select?q=myname*=AND=(-(site_role:"Guest"))
debugQuery shows this is parsed as the following,
I think this is the issue with top-level negative clause. Lucene does
not know what "-x" means without "*:* -x" to establish the baseline
set to subtract from. Solr has a workaround for top-level negative
query, so "-WithinPrefixTreeQuery..." t
Hi Alex and Erick,
We could possibly put them in fq, but how we set everything up would make
it hard to do so, but going that route might be the only option.
I did take a look at the parsed query and this is the difference:
This is the one that works:
"-WithinPrefixTreeQuery(fiel
Also, Solr does _not_ implement strict Boolean logic, although with
appropriate parentheses you can get it to look like Boolean logic.
See: https://lucidworks.com/2011/12/28/why-not-and-or-and-not/.
Additionally, for _some_ clauses a pure-not query is translated into
*:* -pure_not_query which
Have a look at what debug shows in the parsed query. I think every
bracket is quite significant actually and you are generating a
different type of clause.
Also, have you thought about putting those individual clauses into
'fq' instead of jointly into 'q'? This may give you faster search too
Hi,
I am doing some date queries and I was wondering if there is some way of
getting this query to work.
( ( !{!field f=collection_date_range op=Within v='[2000-01-01 TO
2018-09-18]'} AND !{!field f=collection_date_range op=Within v='[1960-01-01
TO 1998-09-18]'} ) AND collection_season:([1999-05
=false
--
BR, Vadim
-Original Message-
From: Steve Pruitt [mailto:bpru...@opentext.com]
Sent: Friday, September 14, 2018 9:22 PM
To: solr-user@lucene.apache.org
Subject: join query in same collection
I see nothing in the documentation suggesting a query with a join filter
doesn't work
I see nothing in the documentation suggesting a query with a join filter
doesn't work when a single collection is involved. There is the special
deployment instructions when joining across two distinct collections, but this
is not my case.
I have a single collection:
I have two VM's, both
Did you manage to solve the problem? I have the same problem and would like
to know a solution.
Chien Nguyen wrote
> Many thank. I will try it.
--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
Afternoon all,
Just to add some closure to this topic in case anybody else stumbles across a
similar problem I've managed to resolve my issue by removing the switch query
parser from the _appends_ component of the parameter set.
so the parameter set changes from this
"set":{
&q
Thanks for the suggestions and responses Erick and Shawn. Erick I only return
30 records irrespective of the query (not the entire payload) I removed some of
my configuration settings for readability. The parameter "allResults" was a
little misleading I apologise for that but I appre
well, it's our general text field that things get dumped into. this special
use case that is sku specific just ends up being done on the general input.
ended up raising the Xss value and i'm able to get results :)
i imagine this is a n00b or stupid question but imma go for it: what would
be the
Looks like your SKU field is points-based? Strings would probably be
better, if you switched to points-based it's new code.
And maxBooleanClauses is so old-school ;) You're better off with
TermsQueryParser, especially if you pre-sort the tokens. see:
hey all!
i'm having an issue w large queries. one of our use cases is for users to
drop in an untold amount of product skus. we previously had our
maxBooleanClause limit set to 20k (eek!). but it worked phenomenally well
and i think our record amount from a user was ~19k items.
we're now on 7.4
awn Heisey wrote:
>
> On 9/12/2018 5:47 AM, Dwane Hall wrote:
> > Good afternoon Solr brains trust I'm seeking some community advice if
> > somebody can spare a minute from their busy schedules.
> >
> > I'm attempting to use the switch query parser to influence client
On 9/12/2018 5:47 AM, Dwane Hall wrote:
Good afternoon Solr brains trust I'm seeking some community advice if somebody
can spare a minute from their busy schedules.
I'm attempting to use the switch query parser to influence client search
behaviour based on a client specified request parameter
Good afternoon Solr brains trust I'm seeking some community advice if somebody
can spare a minute from their busy schedules.
I'm attempting to use the switch query parser to influence client search
behaviour based on a client specified request parameter.
Essentially I want the following
On 9/10/2018 5:45 PM, dshih wrote:
Based on what you said, is my query supposed to work as is if I set
luceneMatchVersion=7.1.0? It does not appear to.
It does look like a luceneMatchVersion check was added to the change in
SOLR-11501, so I would expect that to work. Setting
Thanks Shawn!
Based on what you said, is my query supposed to work as is if I set
luceneMatchVersion=7.1.0? It does not appear to.
Also, my understanding is using the local param makes the AND apply only to
the following search terms provided to the "q" query string. If I
t;>
> >>> I have a question. I am trying to use the "within" op parameter in a
> Date
> >>> Search. This works like I would expect: {!field
> f=collection_date_range
> >>> op=Within}[2013-07-08 TO 2013-07-09]
> >>>
> >>> I would like to
e I would expect: {!field f=collection_date_range
>>> op=Within}[2013-07-08 TO 2013-07-09]
>>>
>>> I would like to use an OR with the query though, something like this:
>>> {!field
>>> f=collection_date_range op=Within}[2013-07-08 TO 2013-07-09] OR {!field
>>> f=c
ould expect: {!field f=collection_date_range
>> op=Within}[2013-07-08 TO 2013-07-09]
>>
>> I would like to use an OR with the query though, something like this:
>> {!field
>> f=collection_date_range op=Within}[2013-07-08 TO 2013-07-09] OR {!field
>> f=colle
On 9/10/2018 1:21 PM, Antelmo Aguilar wrote:
Hi,
I have a question. I am trying to use the "within" op parameter in a Date
Search. This works like I would expect: {!field f=collection_date_range
op=Within}[2013-07-08 TO 2013-07-09]
I would like to use an OR with the query though,
Hi,
I have a question. I am trying to use the "within" op parameter in a Date
Search. This works like I would expect: {!field f=collection_date_range
op=Within}[2013-07-08 TO 2013-07-09]
I would like to use an OR with the query though, something like this: {!field
f=collection_dat
> > Hi
> > I have some docs in my solr index. and now i want to run a query. please
> > help me how create this query?
> > i have documents like this:
> > {
> > topic_code:"A"
> > },
> > {
> > topic_code:"B"
&g
You can't do this with boosting. Boosting affects scoring, i.e. the
ranking. I'd expect this to show
On Mon, Sep 10, 2018 at 12:37 AM sara hajili wrote:
>
> Hi
> I have some docs in my solr index. and now i want to run a query. please
> help me how create this query?
> i have
Hi
I have some docs in my solr index. and now i want to run a query. please
help me how create this query?
i have documents like this:
{
topic_code:"A"
},
{
topic_code:"B"
},
{
topic_code:"A"
},
{
topic_code:"A"
},
{
topic_code:"C"
},
{
topic_co
On 9/7/2018 6:59 PM, dshih wrote:
Query:
/select?q={!q.op=AND}mysearchtext*=edismax=true
Result:
"querystring": "{!q.op=AND}mysearchtext*",
"parsedquery": "+DisjunctionMaxQuery(((Synonym(text:q
text:qopandmysearchtext text:{!q.op=and}mysearchtext*)
SOLR 7.4.0
Apologies if this has been answered, but I can't find the answer for the
life of me if it has been.
Query:
/select?q={!q.op=AND}mysearchtext*=edismax=true
Result:
"querystring": "{!q.op=AND}mysearchtext*",
"parsedquery": "+DisjunctionMaxQuery(((Syn
Alexandre's response is probably a better solution, assuming that the
field in question isn't complex, for instance:
http://localhost:8983/solr/techproducts/query?q={!term f=id}AND
Be aware that this requires that the value for the field (AND in this
case) be exactly as it appears in the index
As Erick said, you need to be looking into Query Parsers. There are
many, depending on what search you are actually allowing your users to
do. You probably know lucene/default, dismax and edismax, but there
are many more: http://lucene.apache.org/solr/guide/7_4/other-parsers.html
For example, you
This is a query _parsing_ issue, way before a tokenizer ever gets to
it. The problem of course is that AND is an operator in the query
language, so your problem is how to distinguish it from the value of a
field.
You can always quote the input for id, as in id:"AND" which yo
One of the ID attribute which we are using to query is AND so our looks like
http://localhost:8983/solr//select?fq=id:AND=json
This throws below mentioned exception
error: { metadata: [ "error-class", "org.apache.solr.common.SolrException"
My guess is that you're searching un-warmed instances of Solr and are
seeing the time it takes to read the index structures into memory the
first time. What happens if you turn off indexing and query a number
of values (not the same one or you'll hit the queryResultCache).
So your first query
t;3",
"v07_s":"155",
"v08_s":"5",
"v09_s":"15",
"v10_s":"15",
"v11_s":"555",
"v12_s":"43819292",
"v13_s":"
t;3",
"v07_s":"155",
"v08_s":"5",
"v09_s":"15",
"v10_s":"15",
"v11_s":"555",
"v12_s":"43819292",
"v13_s":"
Add debug=true and see where the time goes, in which components?
Highlighting is my culprit guess. Or faceting?
> On Sep 3, 2018, at 07:45, zhenyuan wei wrote:
>
> Hi ，
> I am curious “How long does a query q=field1:2312 cost , which
> exactly match only one document? ”
Hi ，
I am curious “How long does a query q=field1:2312 cost , which
exactly match only one document? ”， Of course we just discuss no
queryResultCache with match in this situation.
In fact my QTime is 150ms+， it is too long.
There might be something like fq=filter(foo:[2 TO 3]) OR filter(foo:[3 TO
100])
On Fri, Aug 24, 2018 at 2:23 PM zhenyuan wei wrote:
> Hi All，
> I am confuse about How to hit filterCache？
>
> If filterQuery is range [3 to 100] , but not cache in FilterCache，
> and filterCache already exists
ocSet
from FilterCache range[2 to 100]" ?
Each entry in the filterCache uses the query as its key. So for the
first one, the key will be something like "field:[3 TO 100]" or whatever
your fq parameter value was. When the second one is executed, it will
have a different key, so
problem going above 100 million.
You cannot tell Solr "cache this field, but do not cache this other
field." The caches cannot be configured on a per-field basis like this.
The queryResultCache caches query results, if the result size is inside
the window size. The filterCache cac
Hi,
No it will not and it does not make sense to - it would still have to apply
filter on top of cached results since they can include values with 2. You can
consider a query as entry into cache.
Thanks,
Emir
--
Monitoring - Log Management - Alerting - Anomaly Detection
Solr & Elasticse
Hi All，
I am confuse about How to hit filterCache？
If filterQuery is range [3 to 100] , but not cache in FilterCache，
and filterCache already exists filterQuery range [2 to 100],
My question is " Dose this filterQuery range [3 to 100] will fetch DocSet
from FilterCache range[2 to 100]" ?
Thanks again~ @Shawn @Jan Høydahl
What is the recommend size of one shard？or how many docs per shard is
recommend?
My collection has 20 shard，each shard is 30~50GB。
@Shawn according to your wiki and e-mail reply，
to achieve a better query performance ，I estimate the RAM requirement like
follow
from
> DocBs. The multi-value field is named "members"
>
> I am trying to conceptualize a query join where for a given DocA the
> response contains those DocBs whose identifier is contained in DocA's
> members field.
>
> Not sure how to piece this together.
>
901 - 1000 of 10798 matches
Mail list logo
