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 Parsing not robust against dateOptionali formatted fields #7310

Closed
richtmat opened this issue Aug 18, 2014 · 3 comments
Closed

Query Parsing not robust against dateOptionali formatted fields #7310

richtmat opened this issue Aug 18, 2014 · 3 comments

Comments

@richtmat
Copy link

My query looks like this:

   "query": {
      "query_string": {
         "query": "myquery",
         "fields": [
            "stringField1",
            "stringField2",
            "dateOptionalTimeField"
         ]
      }
   }

which leads to an HTTP 400: ElasticsearchParseException[failed to parse date field [myquery], tried both date format [dateOptionalTime], and timestamp number]; nested: IllegalArgumentException[Invalid format: \"myquery\"]; }

If I remove the "dateOptionalTimeField" field from the search I get a result.
If I delete the fields info altogether or have fields: ["_all"] I get the same correct result.

In my opinion the parsing should be robust enough to fulfill the search request without the error.

@richtmat
Copy link
Author

Thanks Clinton, is there such an option on the simple_query_string ? I use them both and have the issue on it as well.

@richtmat
Copy link
Author

as I understand, there is: #5208 but it's not mentioned in the docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants