-
Notifications
You must be signed in to change notification settings - Fork 544
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
Extend /flush to support flushing a single tenant #2260
Conversation
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.
Like the change! I think it should use the more common tenant
, instead of instance
.
Good point! I used |
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.
Thank you for adding doc. Update looks good for docs.
Oops, forgot about this one 🙃 |
@kvrhdn Do we want to backport the docs for this change to the Tempo 2.1 release? Your doc updates don't appear to be in the 2.1 docs. |
If it's not too much work, backporting this would be good. Not super critical imo, this addition to the endpoint has a very narrow use-case, so I doubt a lot of people if any will use this outside of us. |
What this PR does:
/flush
will flush data for all the tenants, this PR extends the endpoint to also support/flush?instance=...
. Flushing the data of single tenant can be useful in case you need to work on data of that single tenant.Which issue(s) this PR fixes:
Fixes #Checklist
Tests updatedCHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]