-
Notifications
You must be signed in to change notification settings - Fork 1.2k
extended_bounds type on DateHistogram #2828
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
Comments
Hey @FabienLavocat, thanks for reporting this. I agree that supporting It gets a little trickier with 2.x and 5.x branches however; technically changing from For binary backwards compatibility, a PR against 5.x and 2.x would need to deprecate the |
I've made the change in the master branch. I don't think it would be an issue in 5.x since there is the implicit conversion from |
Thanks for the PR, @FabienLavocat 🎉 The breaking issue is not so much with implicit conversion from |
Oh yes, it makes complete sense. I'll see what's possible for 5.x |
Closing this as PRs merged for the next releases. Thanks for opening @FabienLavocat 👍 |
NEST/Elasticsearch.Net version: NEST 5.5.0
Elasticsearch version: 5.5.1
Description of the problem including expected versus actual behavior: The class DateHistogramAggregation has a property ExtendedBounds with the type
ExtendedBounds<DateTime>
I think this type should be more generic. Having the type
ExtendedBounds<DateMath>
would make it easier to use values like "now-1d".In a JSON message, I can send the following:
PS: I can send a PR if needed.
The text was updated successfully, but these errors were encountered: