-
Notifications
You must be signed in to change notification settings - Fork 141
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
Deprecate span collector #990
Deprecate span collector #990
Conversation
Signed-off-by: Chen Dai <[email protected]>
Codecov Report
@@ Coverage Diff @@
## feature/maximus-m1 #990 +/- ##
=========================================================
- Coverage 98.27% 62.76% -35.52%
=========================================================
Files 339 10 -329
Lines 8545 658 -7887
Branches 561 119 -442
=========================================================
- Hits 8398 413 -7985
- Misses 142 192 +50
- Partials 5 53 +48
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
Signed-off-by: Chen Dai <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Signed-off-by: Chen Dai [email protected]
Description
Background
SpanCollector
is an implementation class ofCollector
interface. InAggregationOperator
, it's used to generate span start point for anExprValue
(incollector.bucketKey()
which is similar responsibility asWindowAssigner
). Eventually,AggregationOperator
will fetch all results (incollector.results()
).Problems
For some reason,
SpanCollector
doesn't convert aggregate result map toExprValue
simply and return it toAggregationOperator
. Instead, it calculates result array size and locate each map key again. This is probably to support filling gaps between windows as example shown below:Solution in the PR
However, after testing both current span and OpenSearch histogram DSL query, this complicated logic is no use any more. This PR is to deprecate it and remove unused code in
Rounding
class correspondingly. This preparesAggregationOperator
andRounding
for the upcoming stream processing changes.Testing
Both PPL and DSL query returns only bucket which has data:
Issues Resolved
#954
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.