fix(obfuscator): stop obfuscating postgres EXTRACT temporal field#97
Closed
Eldolfin wants to merge 1 commit into
Closed
fix(obfuscator): stop obfuscating postgres EXTRACT temporal field#97Eldolfin wants to merge 1 commit into
Eldolfin wants to merge 1 commit into
Conversation
…nc temporal field
3 tasks
Author
|
Does not fix the issue actually... It should be obfuscated but in a different manner. Sorry for the noise ! |
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
1 participant
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.
Partially fixes DataDog/datadog-agent#49420 DataDog/integrations-core#23565 (the same fix needs to be done in datadog-agent's sql obfuscator)
What does this PR do?
In a query like
SELECT EXTRACT(epoch FROM t.ts) FROM t;keepepoch(the temporal field) as is instead of obfuscating it.Additional Notes
see DataDog/datadog-agent#50307 for the same fix on the agent's side