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

[DOCS]explain how checkpoints works for time buckets #71472

Closed

Conversation

hendrikmuhs
Copy link

Draft

With #54068 change detection optimized uses cases with date histograms. This optimization isn't reflected in the docs yet. I think it also makes sense to give an example.

NOTE This PR is not meant to be merged.

Another Heuristic can be applied for time buckets if you use a `date_histogram` to
group by time buckets. Change detection will detect which time buckets have changed
and only update those.

[discrete]
Copy link
Author

Choose a reason for hiding this comment

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

Another improvement idea:

It would be good to explain a checkpointing best practice: using ingest timestamps (requires 7.11) instead of timestamps that are coming from outside. However I am not sure if this belongs here or in the put transform documentation (or both)

Copy link
Author

Choose a reason for hiding this comment

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

this is already mentioned in create transform


TIP: If the cluster experiences unsuitable performance degradation due to the
{transform}, stop the {transform} and refer to <<transform-performance>>.

[discrete]
[[ml-transform-checkpoint-heuristics]]
== Change Detection Heuristics
Copy link
Author

Choose a reason for hiding this comment

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

I created some visuals about change point detection, e.g. in #63315

This is a very technical one, but maybe we can take the ideas from it to create a better visual for this place.

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.

1 participant