-
Notifications
You must be signed in to change notification settings - Fork 313
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
Support datastreams in Rally #1053
Comments
I have hit an issue on the a track that also needs |
Code merged. Pending IT and docs. |
@danielmitterdorfer we will need data streams stats. My initial instinct is to add as a runner like https://esrally.readthedocs.io/en/stable/track.html?highlight=index%20stats#index-stats? Any other approaches you'd like to consider? Happy to own. |
If we want custom metrics I suggest we implement a so-called telemetry device similar to: Line 1243 in 4d4f863
|
👍 appreciate the guidance. |
Propose the following features be core operations in Rally due to the applicability to common workloads:
Ability to rollover a datastream - https://www.elastic.co/guide/en/elasticsearch/reference/master/use-a-data-stream.html#manually-roll-over-a-data-stream We can potentially support this through a new runner. Note the event data supports this via this runner. We want this rollover to occur during indexing, however - so we may want to incorporate it into the bulk action itself. To discuss with @dliappis. This is low priority and likely to be used infrequently if we recommend using ILM for rollover.Dropped in support of ILM. Support ILM Policies #1087Datastreams support a number of other operations e.g. Updating documents by query. I don't believe these will be used regularly in workloads however and can be implemented as custom runners if needed.
The text was updated successfully, but these errors were encountered: