We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
PR #14300 talks about the reasoning for triggering no-op minion tasks when there are table config updates.
Cons of this approach is that there will be minion tasks created for all segments for each table config update.
To overcome this problem, we can use a server side API that will return the list of segments to be refreshed. It is being developed in #14450.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
PR #14300 talks about the reasoning for triggering no-op minion tasks when there are table config updates.
Cons of this approach is that there will be minion tasks created for all segments for each table config update.
To overcome this problem, we can use a server side API that will return the list of segments to be refreshed. It is being developed in #14450.
The text was updated successfully, but these errors were encountered: