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

DataHub service-level agreement #2663

Open
wants to merge 17 commits into
base: develop
Choose a base branch
from
Open

DataHub service-level agreement #2663

wants to merge 17 commits into from

Conversation

eickler
Copy link
Contributor

@eickler eickler commented Nov 21, 2024

No description provided.

Copy link
Contributor

Preview available here

@eickler eickler marked this pull request as draft November 21, 2024 12:49
@MWindel MWindel added the Draft label Nov 21, 2024
@eickler eickler marked this pull request as ready for review December 3, 2024 12:58
@eickler eickler requested a review from cheinz-sag December 3, 2024 12:58
@BeateRixen BeateRixen removed the Draft label Dec 4, 2024
| [Offloaded leaf properties](https://docs.dremio.com/current/get-started/cluster-deployments/architecture/limits/#catalog) | Hard | 6400 |
| Query time out | Hard | ??? |
| Query job retention | Hard | 1 day |
| [Rows in a query job](https://docs.dremio.com/current/get-started/cluster-deployments/architecture/limits/#execution) | Hard | 1000000 |
Copy link
Collaborator

Choose a reason for hiding this comment

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

What does the limit on Offloaded leaf properties, Rows in a query job and ows in a high performance query mean to a customer?
Currently, they link to the Dremio documentation but do not explain what to consider when setting up offloading jobs within Cumulocity IoT.

We should describe somewhere in the Cumulocity documentation what these limits mean to Cumulocity users and use-cases and how a user can ensure to stay below the limits when e.g. creating a new offloading job.

Copy link
Contributor Author

@eickler eickler Dec 5, 2024

Choose a reason for hiding this comment

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

Yeah, I agree. I would do that as a different PR to get this out first.

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.

5 participants