Hello, Kumar.
I don't know. 3 / 84 ratio seems reasonable. The only unknown part of the
equation was that {!simpleFilter}. Anyway, profiler/sampler might get exact
answer.
On Fri, Jan 24, 2020 at 8:55 AM kumar gaurav wrote:
> HI Mikhail
>
> Can you please see above debug log and help ?
>
>
HI Mikhail
Can you please see above debug log and help ?
Thanks
On Thu, Jan 23, 2020 at 12:05 AM kumar gaurav wrote:
> Also
>
> its not looks like box is slow . because for following query prepare time
> is 3 ms but facet time is 84ms on the same box .Don't know why prepare time
> was huge
Never heard of that.
On Thu, Jan 23, 2020 at 11:14 PM Wei wrote:
> Thanks Mikhail. Do you know of any example on query parser with WAND?
>
> On Thu, Jan 23, 2020 at 1:02 AM Mikhail Khludnev wrote:
>
> > If one creates query parser wrapping queries with WAND it just produce
> > incomplete
Thanks Mikhail. Do you know of any example on query parser with WAND?
On Thu, Jan 23, 2020 at 1:02 AM Mikhail Khludnev wrote:
> If one creates query parser wrapping queries with WAND it just produce
> incomplete docset (I guess), which will be passed to facet component and
> produce fewer
Hey All,
is there a way to get a list of all fields in a collection that can be used
in an SQL query? Currently I retrieve a list of fields through the schema
api: GET col/schema/fields.
This returns all fields in a collection. But when I do a select on all
fields I get an exception because
It's a great idea. And then index that file into a separate lean collection
of just the suggestions, along with the weight as another field on those
documents, to use for ranking them at query time with standard /select queries.
(this separate suggest collection would also have appropriate
On Wed, Jan 22, 2020 at 4:27 PM Doss wrote:
> HI,
>
> SOLR version 8.3.1 (10 nodes), zookeeper ensemble (3 nodes)
>
> Read somewhere that the score join parser will be faster, but for me it
> produces no results. I am using string type fields for from and to.
>
That's odd. Can you try to enable
I have been working extensively on query autocompletion, these blogs should
be helpful to you:
https://sease.io/2015/07/solr-you-complete-me.html
https://sease.io/2018/06/apache-lucene-blendedinfixsuggester-how-it-works-bugs-and-improvements.html
You idea of using search quality evaluation to
>From the Join Query Parser code:
"// most of these statistics are only used for the enum method
int fromSetSize; // number of docs in the fromSet (that match
the from query)
long resultListDocs; // total number of docs collected
int fromTermCount;
long fromTermTotalDf;
int
Edward is correct, furthermore using a stemmer in an analysis chain that
don't tokenise is going to work just for single term queries and single
term field values...
Not sure it was intended ...
Cheers
--
Alessandro Benedetti
Search Consultant, R Software Engineer,
Hi Seetesh,
As you can see from the wiki [1] there are mainly two input sources for a
spellcheck dictionary:
1) a file
2) the index (in a couple of different forms)
If you prefer the file approach, it's your call to produce the file and you
can certainly use whatever you like to fill the data.
It
http://localhost:8983/solr/admin/info/health
Jan
> 22. jan. 2020 kl. 18:15 skrev Daniel Trüssel :
>
> Hey
>
> With DuckDuckGo I found no HTTP health endpoint for Solr.
>
> I use https://github.com/prometheus/blackbox_exporter to probe our apps.
> JMX_exporter is not an option, I need to use
If one creates query parser wrapping queries with WAND it just produce
incomplete docset (I guess), which will be passed to facet component and
produce fewer counts.
On Thu, Jan 23, 2020 at 2:11 AM Wei wrote:
> Hi,
>
> I am excited to see Lucene 8 introduced BlockMax WAND as a major speed
>
13 matches
Mail list logo
