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

Make numTasks read-only metadata property in get datastream #824

Merged
merged 7 commits into from
May 12, 2021

Conversation

vmaheshw
Copy link
Collaborator

numTasks is an additional datastream property which is calculated as part of elastic task count and saves in a separate node in /dms/<datastream>/numTasks. Rest client should be able to expose this information and any user which cache this information and call update to modify some other field should be able to do it.

Note: It will be a read-only property and the server will encapsulate how numTasks is stored. For external user, who has no access to zookeeper cannot differentiate between this metadata v/s any other metadata using the get output.

@shrinandthakkar
Copy link
Collaborator

could you check the ci, there's some test failure

Copy link
Collaborator

@shrinandthakkar shrinandthakkar left a comment

Choose a reason for hiding this comment

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

otherwise lgtm ✅

@vmaheshw vmaheshw merged commit d411dbc into linkedin:master May 12, 2021
vmaheshw added a commit to vmaheshw/brooklin that referenced this pull request Mar 1, 2022
…#824)

numTasks is an additional datastream property which is calculated as part of elastic task count and saves in a separate node in /dms/<datastream>/numTasks. Rest client should be able to expose this information and any user which cache this information and call update to modify some other field should be able to do it.

Note: It will be a read-only property and the server will encapsulate how numTasks is stored. For external user, who has no access to zookeeper cannot differentiate between this metadata v/s any other metadata using the get output.
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.

4 participants