-
Notifications
You must be signed in to change notification settings - Fork 3.2k
refactor(queries): refactor query edges #14095
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
Conversation
❌ Unsupported file formatUpload processing failed due to unsupported file format. Please review the parser error message:
|
🔴 Meticulous spotted visual differences in 18 of 1453 screens tested: view and approve differences detected. Meticulous evaluated ~8 hours of user flows against your PR. Last updated for commit 716593d. This comment will update as new commits are pushed. |
Bundle ReportChanges will decrease total bundle size by 174.46kB (-0.79%) ⬇️. This is within the configured threshold ✅ Detailed changes
Affected Assets, Files, and Routes:view changes for bundle: datahub-react-web-esmAssets Changed:
|
metadata-io/src/test/java/com/linkedin/metadata/search/update/WriteDAOTestBase.java
Outdated
Show resolved
Hide resolved
* remove graph relation for queries * bulk delete implementation * cleanup step for query graph edges
716593d
to
3093c15
Compare
Why?
The graph index growth is significantly increased when generating edges between queries and schemaField and dataset entities. These edges are not currently required in the product and their value in the graph index is not sufficient to warrant them at this time.
Changes