-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
fix: support for non-string types in object fields #11066
fix: support for non-string types in object fields #11066
Conversation
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThe recent changes enhance the handling of various data types within the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (4)
- metadata-io/src/main/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformer.java (2 hunks)
- metadata-io/src/test/java/com/linkedin/metadata/TestEntityUtil.java (2 hunks)
- metadata-io/src/test/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformerTest.java (1 hunks)
- test-models/src/main/pegasus/com/datahub/test/TestEntityInfo.pdl (1 hunks)
Additional comments not posted (16)
test-models/src/main/pegasus/com/datahub/test/TestEntityInfo.pdl (5)
107-114
: LGTM!The field
esObjectFieldLong
is correctly defined and annotated.
116-123
: LGTM!The field
esObjectFieldBoolean
is correctly defined and annotated.
125-132
: LGTM!The field
esObjectFieldFloat
is correctly defined and annotated.
134-141
: LGTM!The field
esObjectFieldDouble
is correctly defined and annotated.
143-150
: LGTM!The field
esObjectFieldInteger
is correctly defined and annotated.metadata-io/src/test/java/com/linkedin/metadata/TestEntityUtil.java (5)
78-79
: LGTM!The mapping for
esObjectFieldBoolean
is correctly implemented.
80-81
: LGTM!The mapping for
esObjectFieldLong
is correctly implemented.
82-83
: LGTM!The mapping for
esObjectFieldFloat
is correctly implemented.
84-85
: LGTM!The mapping for
esObjectFieldDouble
is correctly implemented.
86-87
: LGTM!The mapping for
esObjectFieldInteger
is correctly implemented.metadata-io/src/test/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformerTest.java (5)
88-88
: LGTM!The assertion for
esObjectFieldBoolean
is correctly implemented.
89-89
: LGTM!The assertion for
esObjectFieldLong
is correctly implemented.
90-90
: LGTM!The assertion for
esObjectFieldFloat
is correctly implemented.
91-91
: LGTM!The assertion for
esObjectFieldDouble
is correctly implemented.
92-92
: LGTM!The assertion for
esObjectFieldInteger
is correctly implemented.metadata-io/src/main/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformer.java (1)
285-311
: LGTM! Ensure the parsing logic is correct.The changes to handle various data types in map values are well-implemented. Each data type is handled separately, ensuring correct parsing.
However, ensure that the parsing logic is correct and handles any potential exceptions.
...io/src/test/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformerTest.java
Outdated
Show resolved
Hide resolved
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- metadata-io/src/test/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformerTest.java (1 hunks)
Files skipped from review as they are similar to previous changes (1)
- metadata-io/src/test/java/com/linkedin/metadata/search/transformer/SearchDocumentTransformerTest.java
@david-leifker can you please review the above PR? |
@Nbagga14 - Please run |
@david-leifker - I have formatted the code. Could you please review? Please let me know if anything further needs to be done. Many thanks. |
@vignesh-hbk - Please take a look at the CI test failures. The tests can be run with |
Hi @david-leifker - We ran both these tests and they passed. Please see below screenshots. Please let me know if further actions or info is needed from me. Thanks. |
Updating the base branch which will rerun the tests. If it passes we're good to move forward. If not, it likely means that your local branch is behind and doesn't account for upstream changes in the project. |
40bd73a
to
fd1c861
Compare
@david-leifker - addressed the failing test cases and tried triggering the tests. Could you please check ? Many thanks. |
Updated with latest master and still seeing failures in Per the failure log, these are the kinds of failures I am seeing:
|
@david-leifker - Hi David - Took the latest changes post merge and addressed the failing changes. Please review. All of the tests seem to have passed here as well. Please review and let us know if anything further needs to be done on our end. Many thanks for you help and patience. |
@david-leifker - Could you please help review the change? Many thanks |
Checklist
Summary by CodeRabbit
New Features
TestEntityInfo
, expanding its functionality.Bug Fixes
Tests
Documentation
TestEntityInfo
now support more complex data structures and are queryable.