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 an inconsistency in wal search #1548

Merged
merged 6 commits into from
Jul 6, 2022
Merged

Conversation

mdisibio
Copy link
Contributor

@mdisibio mdisibio commented Jul 5, 2022

What this PR does:
This PR is a followup to #1538. It runs the same comprehensive search tests against the two block types in the ingester: wal (StreamingSearchBlock) and completed (BackendSearchBlock). A bug was found and addressed in the StreamingSearchBlock header tag check.

The comprehensive test cases in /tempodb/ were moved to /pkg/model/trace and made reusable, as well as the tag extraction logic from the distributor. These two PRs are in preparation for #1547.

Which issue(s) this PR fixes:
Fixes n/a

Checklist

  • Tests updated
  • Documentation added
  • CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

pkg/model/trace/search_test_suite.go Outdated Show resolved Hide resolved
@mdisibio mdisibio changed the title Search testing 2 Fix an inconsistency in wal search Jul 6, 2022
@mdisibio mdisibio merged commit 6f98ff7 into grafana:main Jul 6, 2022
joe-elliott pushed a commit to joe-elliott/tempo that referenced this pull request Jul 7, 2022
* Move flatbuffer search extract methods from distributor to reuseable location

* Move trace test suite to reusable location

* Run trace search tests against wal and backend search blocks.  Fix wal header tag check to be substring

* lint

* changelog

* review feedback
@mdisibio mdisibio deleted the search-testing-2 branch April 25, 2023 18:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants