On Tue, 2018-11-20 at 21:17 -0700, Shawn Heisey wrote:
> Maybe the error condition should be related to a new schema
> property, something like allowQueryOnDocValues. This would default
> to true with current schema versions and false in the next schema
> version, which I think is 1.7. Then a use
On 11/20/2018 8:18 PM, Rahul Goswami wrote:
Erick and Toke,
Thank you for the replies. I am surprised there already isn’t a JIRA for
this. In my opinion, this should be an error condition on search or
alternatively should simply be giving zero results. That would be a defined
behavior as opposed
Erick and Toke,
Thank you for the replies. I am surprised there already isn’t a JIRA for
this. In my opinion, this should be an error condition on search or
alternatively should simply be giving zero results. That would be a defined
behavior as opposed to now, where the searches are not particular
On Mon, 2018-11-19 at 22:19 -0500, Rahul Goswami wrote:
> I am using SolrCloud 7.2.1. My understanding is that setting
> docvalues=true would optimize faceting, grouping and sorting; but for
> a field to be searchable it needs to be indexed=true.
Erick explained the search thing, so I'll just note
I've noticed this too, but I think it's more a side effect than
something usable for the reasons you outlined. Searching a docValues
field is akin to a "table scan", the uninverted structure is totally
unsuited for searching. It works, but as you've found out it's
unusably slow for any decent siz
I am using SolrCloud 7.2.1. My understanding is that setting docvalues=true
would optimize faceting, grouping and sorting; but for a field to be
searchable it needs to be indexed=true. However I was dumbfounded today
when I executed a successful search on a field with below configuration:
However
