-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
chore(website): add notice on timestamp field renaming in the Elasticsearch sink, when use data_stream mode #22196
chore(website): add notice on timestamp field renaming in the Elasticsearch sink, when use data_stream mode #22196
Conversation
e0ece1f
to
54ee28b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a small editorial edit.
54ee28b
to
833b631
Compare
833b631
to
0e803c2
Compare
0e803c2
to
22de070
Compare
Head branch was pushed to by a user without write access
22de070
to
2dac288
Compare
Head branch was pushed to by a user without write access
2dac288
to
fa5f140
Compare
@pront |
Updated labels and approved check run 🚀 |
…sticsearch sink Signed-off-by: Up Neck <[email protected]>
Head branch was pushed to by a user without write access
fa5f140
to
4772bc9
Compare
@pront |
Summary
Elasticsearch sink documentation doesn't highlight
data_stream
mode behavior on.timestamp
field.Change Type
Is this a breaking change?
How did you test this PR?
Does this PR include user facing changes?
Checklist
make check-all
is a good command to run locally. This check isdefined here. Some of these
checks might not be relevant to your PR. For Rust changes, at the very least you should run:
cargo fmt --all
cargo clippy --workspace --all-targets -- -D warnings
cargo nextest run --workspace
(alternatively, you can runcargo test --all
)Cargo.lock
), pleaserun
dd-rust-license-tool write
to regenerate the license inventory and commit the changes (if any). More details here.References