[Postgresql] Add alias field for database.oid - #9695
Merged
Conversation
🚀 Benchmarks reportTo see the full report comment with |
ishleenk17
reviewed
Apr 26, 2024
ishleenk17
left a comment
Member
There was a problem hiding this comment.
Please check if we can use field aliasing here.
Alias all these 3 fields in datastream to database.oid.
💚 Build Succeeded
History
|
|
|
Package postgresql - 1.20.0 containing this change is available at https://epr.elastic.co/search?package=postgresql |
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
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.





What does this PR do?
There are 3 datasets in Postgresql and all three have OID fields under different field names.
User should be able to associate data across these 3 datasets using these OID's.
To solve this issue we have added
database.oidfield as alias fild to all the above fieldsRelated issue
Checklist
changelog.ymlfile.