Benjamin Vetter

i'd like to underline the need for an offical feature complete and performant alternative to the flattened datatype and it also was requested a lot on several sites already: https://github.com/opendistro-for-elasticsearch/opendistro-build/issues/523,...

@macrakis thanks for the notification. Not sure what _not indexing individual subfields_ means performance wise for queries. Our use cases cover mostly i) querying leaf key/value pairs like with keyword...

yes, let's forget about the storage layer complexity. I was as well only talking about the complexity that is ardb specific, because even from looking into the ardb code it's...

well, i can offer to add escaping to the query syntax, such that you can search for ``` word1 word2\:word3 ... ``` then you are free to escape ":", "=",...

... disabling it is not really an option, especially not for string fields only - as it's not possible to change the parser/grammar (treetop) on the fly. So, only option...

you can search for empty values via the = operator, like ``` ruby Book.search("author=''") ``` searching for explicit null's is currently not supported and would require a special syntax/operator, since...

Hi, thanks for reporting. Just trying to reproduce, but my test case is running fine: ``` ruby def test_wildcard expected = create(:product, :title => "Expected") rejected = create(:product, :title =>...

Ah, ok. However, this behaviour is desired. Fulltext search usually works this way and if you don't want it, simply do not use the fulltext feature.

That's true. However, the use cases seem to be limited to me. Maybe you can give examples. I'd be ok, though, with an option `option :title, :fulltext => true, :fulltext_wildcard...

Do you feel like creating a PR?