Options are not supported in filters that get translated into the must_not part of Elastic queries

[robvandenbogaard]

Building Elastic queries via the build_filter function in elasticsearch_search.erl:169 is done in two parts: one part handles filters that include things, resulting in a must subquery of the top-level boolean query, and the other part handles exclusion (e.g. ne or <> operations).
It turns out that the latter does not support filter options, as the must part does (because it is implemented separately, and it does not use map_filter, where options are processed).
This is troublesome for nested fields that require a path option to be set.
Also, only the atom <> and ne are supported in must_nots, while the must path supports also binary and list (string) operators. This is suspected to introduce unexpected behaviour (or absence of) when using normal quotes.