-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Sum aggregations for long values precision #50538
Conversation
Change-Id: I6e4b1dfd590aea68dd092318edb11a2baa2f9d65
Change-Id: Ied28bb7b561fd58fdb438199a9be85ea91dc5536
Change-Id: Iebd02310792eac05edb661816e1a455d148db23f
Change-Id: I4b93e948f0130727531cbbf9020168209e486941
Hi @hackerwin7, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in your Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile? |
retest |
ping @colings86 @jpountz |
Pinging @elastic/es-analytics-geo (:Analytics/Aggregations) |
Hi @hackerwin7, thanks for the PR :) Please don't ping individual members though, when tickets are labeled it will ping the correct team to take a look. I'm going to mark this ticket for team discussion, but I suspect we won't be able to merge it. There is some discussion about supporting more precise aggregations in this issue, for background: #46934 There are a few issues which make this problematic:
Marking as team-discuss to see what the rest of the analytics team has to say! |
@polyfractal |
@hackerwin7 at the moment, no plans at all... just something we've been discussing. That's the main reason I didn't close this PR but marked it as team-discuss to see what the rest of the team thought. Sometimes small incremental improvements are better than nothing at all :) |
Any news here? |
Actually yes! ESQL supports |
Create long type for
InternalSum
andSumAggregator
to process the long field type of values without loosing precision.relates #50503