date format parsed from query to builder defaults to current date with fixed format

[oguennec]

@dncrews
When parsed into the builder, date fields from a query default to the current date with fixed format (calendar default format). Only some ISO formats are recognized

[dncrews]

What do you mean by this? I hesitate to add something like moment in here if that can be avoided.

[oguennec]

With this fix, a format field is added next to a date, for instance:

      "range": {
        "datePublished": {
          "lte": "2013-03-08",
          "format": "yyyy-MM-dd"
        }
      }

Hence the builder knows the format to parse a string to a date.

MomentJS/Angular-MomentJS appears to be the solution for the job.

Without this fix, the format is hard coded and any date field in "stored" queries must follow this format so that the query can be parsed by the builder.

Also without the fix, a date in a query defaults to the current date when parsed through the builder.

I have created a search application that uses the builder in this way with a demo. I hope this helps to illustrate my understanding on how to use your builder.

[tienvx]

Just a note: if we add 'format' key to the rule, like this:

{"query":{"filtered":{"filter":{"and":[{"term":{"startRegistered":"2016-06-30T13:37:06+0700", "format": "yyyy-MM-dd'T'HH:mm:ssZ"}}]}}},"sort":[],"from":0,"size":100}

elasticsearch will return an error:

[term] query does not support different field names, use [bool] query instead

I suggest to use one format only 'yyyy-MM-dd'T'HH:mm:ssZ' and then use another datepicker library that include timepicker e.g. angular-bootstrap-datetimepicker

[oguennec]

Elastic search understands multiple date formats so it seems interesting to have this feature in the builder. Also setting the time is not always relevant in a range search so date only format are useful. But I agree that when time is required, it would be nice to have a timepicker. I suggest ui.boostrap.timepicker. This should be a request for a new feature in a separate issue though.

[dncrews]

If it breaks elasticsearch as is, I'm not interested in having it. This is first and foremost an Elasticsearch query builder.

[dncrews]

format doesn't sound like part of the query. It sounds like part of the configuration.

Thoughts about doing something like:

'test.date': { type: 'date', format: 'YYYY-mm-dd' },

This sounds right to me. Elasticsearch supports multiple date formats, but each field in ES should only be standardized into a single format. I think we should rewrite it to be like this.

[dncrews]

Or perhaps passing your own formatter method?