On 11/20/2017 12:50 PM, Sundeep T wrote:
> I initially asked this question regarding leading wildcards. This was a
> typo, and what I meant was trailing wild card queries were slow. So queries
> like text:'hello*" are slow. We were expecting since the string field is
> already indexed, the
At first glance you have a mis-configured setup. The most glaring
issue is that you're trying to search a 150G index in 1G of memory.
bq: String field (not tokenized) is docValues=true, indexed=true and stored=true
OK, this is kind of unusual to query but if the field just contains
single tokens
Hi Erick,
Thanks for the reply. Here are more details on our setup -
*Setup/schema details -*
100 million doc solr core
String field (not tokenized) is docValues=true, indexed=true and stored=true
Field is almost unique in the index, around 80 million are unique
no commits on index
all
Well, define "slow". Conceptually a large OR clause is created that
contains all the terms that start with the indicated text. (actually a
PrefixQuery should be formed).
That said, I'd expect hello* to be reasonably fast as not many terms
_probably_ start with 'hello'. Not the same at all for,
Hi Erick.
I initially asked this question regarding leading wildcards. This was a
typo, and what I meant was trailing wild card queries were slow. So queries
like text:'hello*" are slow. We were expecting since the string field is
already indexed, the searches should be fast, but that seems to be
You already asked that question and got several answers, did you not
see them? If you did see them, what is unclear?
Best,
Erick
On Mon, Nov 20, 2017 at 9:33 AM, Sundeep T wrote:
> Hi,
>
> We have several indexed string fields which is not tokenized and does not
> have
Hi,
We have several indexed string fields which is not tokenized and does not
have docValues enabled.
When we do trailing wildcard searches on these fields they are running very
slow. We were thinking that since this field is indexed, such queries
should be running pretty quickly. We are using