Repository navigation
#8888: Fix Logstash::Util.deep_clone for Timestamp - #9405
Closed
original-brownbear wants to merge 1 commit into
Closed
original-brownbear wants to merge 1 commit into
original-brownbear wants to merge 1 commit into
Conversation
Contributor
Author
|
@jsvd thanks! |
Contributor
Author
|
@andrewvc this one is pretty nasty (see the related issue, it e.g. prevents copying the timestamp field with |
Contributor
|
Hmmm, I think it's fine to backport this to 6.2. Realistically, however, I think this will be in 6.3.0 since we missed the 6.2.4 train. |
Contributor
|
This looks like its used in three places, mutate, jdbc_static, and jdbc_streaming) https://github.com/search?q=org%3Alogstash-plugins+deep_clone&type=Code |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #8888 by using cloning instead of marshaling for the timestamp since the Java field in the timestamp doesn't get correctly marshaled.