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

Fix date hardcoding in date aggregator #17239

Merged
merged 1 commit into from
Feb 4, 2025

Conversation

sandeshkr419
Copy link
Contributor

@sandeshkr419 sandeshkr419 commented Feb 3, 2025

Description

Fix in date aggregator where date field was hard-coded. Fixed that to fetch from value-source if available.
This fix was included in #17165 but the PR is missed for 2.19 so creating a separate PR to only include the bug fix to be pushed to 2.19 branch as feature inclusion is blocked for now in 2.19

Will rebase #17165 after this PR gets merged.

Related Issues

Resolves #[Issue number to be closed when this PR is merged]
Fix date field hard-coding introduced in #16674 - this is required to correctly fetch date field in Date Aggregation using star-tree

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

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.

@sandeshkr419 sandeshkr419 added skip-changelog bug Something isn't working Search:Aggregations backport 2.x Backport to 2.x branch v2.19.0 Issues and PRs related to version 2.19.0 backport 2.19 labels Feb 3, 2025
@sandeshkr419 sandeshkr419 changed the title fix date hardcoding in date aggregator Fix date hardcoding in date aggregator Feb 3, 2025
Copy link
Member

@owaiskazi19 owaiskazi19 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. You can remove the changes from #17165

Copy link
Contributor

github-actions bot commented Feb 3, 2025

❌ Gradle check result for 5277900: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Signed-off-by: Sandesh Kumar <sandeshkr419@gmail.com>
Copy link
Contributor

github-actions bot commented Feb 4, 2025

❕ Gradle check result for 786bb22: UNSTABLE

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Copy link

codecov bot commented Feb 4, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.32%. Comparing base (faabd10) to head (786bb22).
Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #17239      +/-   ##
============================================
- Coverage     72.36%   71.32%   -1.05%     
+ Complexity    65733    64557    -1176     
============================================
  Files          5318     5318              
  Lines        305674   305676       +2     
  Branches      44349    44350       +1     
============================================
- Hits         221197   218018    -3179     
- Misses        66341    69496    +3155     
- Partials      18136    18162      +26     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@msfroh msfroh merged commit b82ed5a into opensearch-project:main Feb 4, 2025
31 checks passed
opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 4, 2025
(cherry picked from commit b82ed5a)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
opensearch-trigger-bot bot pushed a commit that referenced this pull request Feb 4, 2025
(cherry picked from commit b82ed5a)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@sandeshkr419 sandeshkr419 deleted the datef branch February 4, 2025 03:03
mch2 pushed a commit that referenced this pull request Feb 4, 2025
(cherry picked from commit b82ed5a)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
mch2 pushed a commit that referenced this pull request Feb 4, 2025
(cherry picked from commit b82ed5a)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch backport 2.19 bug Something isn't working Search:Aggregations skip-changelog v2.19.0 Issues and PRs related to version 2.19.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants