Should SubQuery be faster than FunctionQuery?
On Sat, Dec 12, 2020 at 10:24 AM Vincenzo D'Amore
wrote:
> Hi, looking at this sample it seems you have just one document for '12345',
> one for '23456' and so on so forth. If this is true, why don't just try
> with a subquery
>
> https://lucene.apac
Hi, looking at this sample it seems you have just one document for '12345',
one for '23456' and so on so forth. If this is true, why don't just try
with a subquery
https://lucene.apache.org/solr/guide/6_6/transforming-result-documents.html#TransformingResultDocuments-_subquery_
On Fri, Dec 11, 202
I have the requirement to create field - xyz to be returned based on the
matched result.
Here Is the code .
XYZ:concat(
if(exists(query({!v='field1:12345'})), '12345', ''),
if(exists(query({!v='field1:23456'})), '23456', ''),
if(exists(query({!v='field1:34567'})), '34567', ''),
https://lucene.apache.org/solr/guide/6_6/common-query-parameters.html#CommonQueryParameters-ThedebugParameter
On Wed, Jul 3, 2019 at 10:10 AM Midas A wrote:
> Please suggest here
>
> On Wed, Jul 3, 2019 at 10:23 AM Midas A wrote:
>
> > Hi,
> >
> > How can i optimize following query it is takin
Please suggest here
On Wed, Jul 3, 2019 at 10:23 AM Midas A wrote:
> Hi,
>
> How can i optimize following query it is taking time
>
> webapp=/solr path=/search params={
> df=ttl&ps=0&hl=true&f.ind.mincount=1&hl.usePhraseHighlighter=true&lowercaseOperators=true&ps2=0&ps3=0&qf=contents^0.05+currd
Hi,
How can i optimize following query it is taking time
webapp=/solr path=/search params={
df=ttl&ps=0&hl=true&f.ind.mincount=1&hl.usePhraseHighlighter=true&lowercaseOperators=true&ps2=0&ps3=0&qf=contents^0.05+currdesig^1.5+predesig^1.5+lng^2+ttl+kw_skl+kw_it&sow=false&hl.fl=ttl,kw_skl,kw_it,co
Ups I forgot the link:
http://yonik.com/solr/paging-and-deep-paging/
On Friday, July 29, 2016 9:51 AM, Ahmet Arslan wrote:
Hi Midas,
Please search 'deep paging' over the documentation, mailing list, etc.
Solr Deep Paging and Sorting
Ahmet
On Friday, July 29, 2016 9:21 AM, Midas A wrote:
Hi Midas,
Please search 'deep paging' over the documentation, mailing list, etc.
Solr Deep Paging and Sorting
Ahmet
On Friday, July 29, 2016 9:21 AM, Midas A wrote:
please reply .
On Fri, Jul 29, 2016 at 10:26 AM, Midas A wrote:
> a) my index size is 10 gb for higher start is query res
please reply .
On Fri, Jul 29, 2016 at 10:26 AM, Midas A wrote:
> a) my index size is 10 gb for higher start is query response got slow .
> what should i do to optimize this query for higher start value in query
>
a) my index size is 10 gb for higher start is query response got slow .
what should i do to optimize this query for higher start value in query
Hi ,
One more thing i would like to add here is we build facet queries over
dynamic fields so my question is
a) Is there any harm of using docValues true with dynamic fields.
b) Other suggestion that we can implement to optimize this query my index
size is 8GB and query is taking more tha 3 seco
DocValues are now the preferred mechanism
whenever you need to sort, facet or group. It'll
make your on-disk index bigger, but the on-disk
structure would have been built in Java's memory
if you didn't use DocValues whereas if you do
it's MMap'd.
So overall, use DocValues by preference.
Best,
as i know when you use docValue=true
solr when indexing doc,
solr although store doc and docValue=true field in memory.to use that in
facet query and sort query result.
so maybe use a lot docvalue=true use a lot memory of ur system.
but use it in logical way.can make better query response time
On
Is there any draw back of using docValues=true ?
On Wed, Jul 13, 2016 at 2:28 PM, sara hajili wrote:
> Hi.
> Facet query take a long time.you vcan use group query.
> Or in fileds in schema that you run facet query on that filed.
> Set doc value=true.
> To get better answer.in quick time.
> On Ju
Hi.
Facet query take a long time.you vcan use group query.
Or in fileds in schema that you run facet query on that filed.
Set doc value=true.
To get better answer.in quick time.
On Jul 13, 2016 11:54 AM, "Midas A" wrote:
> http://
>
> #:8983/solr/prod/select?q=id_path_ids:166&fq=sort_price:[0
http://
#:8983/solr/prod/select?q=id_path_ids:166&fq=sort_price:[0%20TO%20*]&fq=status:A&fq=company_status:A&facet=true&facet.mincount=1&facet.field=show_meta_id&facet.field=show_brand&facet.field=product_amount_available&facet.field=by_processor&facet.field=by_system_memory&facet.field=by_scre
Ok, thanks, new Lucene 2.9 features.
On Mon, Oct 19, 2009 at 2:33 PM, Yonik Seeley
wrote:
> On Mon, Oct 19, 2009 at 4:45 PM, Jason Rutherglen
> wrote:
>> Yonik,
>>
>>> this is a fast operation anyway
>>
>> Can you elaborate on why this is a fast operation?
>
> The scorers will never really be us
On Mon, Oct 19, 2009 at 4:45 PM, Jason Rutherglen
wrote:
> Yonik,
>
>> this is a fast operation anyway
>
> Can you elaborate on why this is a fast operation?
The scorers will never really be used.
The query will be weighted and scorers will be created, but the filter
will be checked first and ret
Yonik,
> this is a fast operation anyway
Can you elaborate on why this is a fast operation?
Basically there's a distributed query with a filter, where on a
number of the servers, the filter query isn't matching anything,
however I'm seeing load on those servers (where nothing
matches), so I'm as
On Mon, Oct 19, 2009 at 2:55 PM, Jason Rutherglen
wrote:
> If a filter query matches nothing, then no additional query should be
> performed and no results returned? I don't think we have this today?
No, but this is a fast operation anyway (In Solr 1.4 at least).
Another thing to watch out for
If a filter query matches nothing, then no additional query should be
performed and no results returned? I don't think we have this today?
: If I know that condition C will eliminate more results than either A or B,
: does specifying the query as: "C AND A AND B" make it any faster (than the
: original "A AND B AND C")?
Nope. Lucene takes care of that for you.
-Hoss
If I know that condition C will eliminate more results than either A or B,
does specifying the query as: "C AND A AND B" make it any faster (than the
original "A AND B AND C")?
--
View this message in context:
http://www.nabble.com/Search-query-optimization-tp17544667p182
: test. If most of requests return the same set of data, cache will
: improve the query performance. But in our usage, almost all requests
: have different data set to return. The cache hit ratio is very low.
that's hwy i suggested moving clauses that are likely to be common (ie:
your "within the
ng
-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 2:32 PM
To: solr-user@lucene.apache.org
Subject: RE: Search query optimization
:Thanks for your suggestions. I did try the [NOW/DAY-7DAYS TO
: NOW/DAY], but it is not better. And I tried [NOW/DA
:Thanks for your suggestions. I did try the [NOW/DAY-7DAYS TO
: NOW/DAY], but it is not better. And I tried [NOW/DAY-7DAYS TO
: NOW/DAY+1DAY], I got some exception as below:
: org.apache.solr.core.SolrException: Query parsing error: Cannot parse
: 'account:1 AND recordeddate_dt:[NOW/DAYS-7DAYS
om: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 1:55 PM
To: solr-user@lucene.apache.org
Subject: Re: Search query optimization
: Probably because the [NOW/DAYS-7DAYS+TO+NOW] part gets rewritten as
lots
: of OR clauses. I think that you'll see that if you add
&
DAY.
Yongjun Rong
-Original Message-
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 1:32 PM
To: solr-user@lucene.apache.org
Subject: Re: Search query optimization
Hi,
This is what I was talking about:
recordeddate_dt:[2008-06-16T00:00:00.000Z TO 2008
: Probably because the [NOW/DAYS-7DAYS+TO+NOW] part gets rewritten as lots
: of OR clauses. I think that you'll see that if you add &debugQuery=true
: to the URL. Make sure your recorded_date_dt is not too granular (e.g.
: if you don't need minutes, round the values to hours. If you don't nee
s, no minutes, no hours...)
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Yongjun Rong <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Tuesday, June 17, 2008 1:09:19 PM
> Subject: RE: Search query optimizatio
-16T00:00:00.000-2008-06-17T17:07:57.420]),
product of:
1.0 = boost
0.09190578 = queryNorm
-Original Message-
From: Otis Gospodnetic [mailto:[EMAIL PROTECTED]
Sent: Tuesday, June 17, 2008 12:43 PM
To: solr-user@lucene.apache.org
Subject: Re: Search query optimization
Hi
you don't need hours, round the values
to days).
Otis
--
Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch
- Original Message
> From: Yongjun Rong <[EMAIL PROTECTED]>
> To: solr-user@lucene.apache.org
> Sent: Tuesday, June 17, 2008 11:56:06 AM
> Subject:
Can anyone give me some explaination why this happens if we have the
query optimization? Thank you very much.
Yongjun Rong
-Original Message-
From: Walter Underwood [mailto:[EMAIL PROTECTED]
Sent: Thursday, May 29, 2008 4:57 PM
To: solr-user@lucene.apache.org
Subject: Re: Search query
The people working on Lucene are pretty smart, and this sort of
query optimization is a well-known trick, so I would not worry
about it.
A dozen years ago at Infoseek, we checked the count of matches
for each term in an AND, and evaluated the smallest one first.
If any of them had zero matches
PROTECTED] On Behalf Of Yonik
Seeley
Sent: Thursday, May 29, 2008 4:12 PM
To: solr-user@lucene.apache.org
Subject: Re: Search query optimization
On Thu, May 29, 2008 at 4:05 PM, Yongjun Rong <[EMAIL PROTECTED]>
wrote:
> I have a question about how the lucene query parser. For example, I
&g
On Thu, May 29, 2008 at 4:05 PM, Yongjun Rong <[EMAIL PROTECTED]> wrote:
> I have a question about how the lucene query parser. For example, I
> have query "A AND B AND C". Will lucene extract all documents satisfy
> condition A in memory and then filter it with condition B and C?
No, Lucene will
Hi,
I have a question about how the lucene query parser. For example, I
have query "A AND B AND C". Will lucene extract all documents satisfy
condition A in memory and then filter it with condition B and C? or only
the documents satisfying "A AND B AND C" will be put into memory? Is
there any art
37 matches
Mail list logo
