Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query DSL: Allow to provide pattern field names when using query_string query #511

Closed
berndlutz opened this issue Nov 12, 2010 · 3 comments

Comments

@berndlutz
Copy link

When using query_string query, allow to use simple pattern matching to allow to expand the fields searched on to the ones matching the pattern. For example, a document in the following form:

{
    "name" : {
        "first" : "shay",
        "last" : "banon"
    }
}

And a query string to query any field under name:

{
    "query_string" : {
        "fields" : [ "name.*" ],
        "query" : "test"
    }
}

The matching is done on the full name of the fields, the index name, and the stand alone name, so allows for interesting matching capabilities. The matching is done using the simple pattern matching support (Match a String against the given pattern, supporting the following simple pattern styles: "xxx*", "xxx", "xxx" and "xxxyyy" matches (with an arbitrary number of pattern parts), as well as direct equality.).

@kimchy
Copy link
Member

kimchy commented Nov 13, 2010

Query DSL: Allow to provide pattern field names when using query_string query, closed by 38d77f8.

@clintongormley
Copy link

Does this also work within the query_string itself? as in "foo bar name.*:kimchy"

@kimchy
Copy link
Member

kimchy commented Nov 13, 2010

No, this can be added as a separate feature, though you should be able to control similar aspects (use dis max or boolean query, tie breaker, and so on).

medcl pushed a commit to medcl/elasticsearch that referenced this issue Jul 1, 2011
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…tic#511)

* Fix MPC-4816: add `X-Forwarded-For` header

(cherry picked from pull request elastic#508)(cherry picked from commit dcd17a548dbd4af46e38d363d36228c7c7836be2)

Approved-by: Gideon Avida
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
The sorted indexing challenge for geonames turned out to be unstable. As
we have other options which are more reliable (such as `http_logs`) we
stop running the sorted indexing challenge for `geonames`.

Relates elastic#511
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants