-
Notifications
You must be signed in to change notification settings - Fork 88
Textual and Visual Algebra Exploration #503
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
…ary substitution for documents to improve performance
…rom ddlManager and catalog methods
…to algebra-exploration
…ing null error for polyAlg tests
…ded handling for concurrent delays for testing
datomo
left a comment
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.
This look good to me (except the sometimes single failing tests...)!
|
This and UI are both good for me @vogti . Thx @tobias-weber |
vogti
left a comment
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.
Thx, @tobias-weber and @datomo, for this amazing contribution!
Summary
This PR enhances Polypheny with the ability to serialize arbitrary query plans into a textual representation called PolyAlgebra. This is the foundation for the new framework-based plan editor system in the UI. The required functionality is provided via new HTTP endpoints and websocket messages.
Changes
Removed the old query plan builder
Replaced the old InformationQueryPlan with InformationPolyAlg for the new plan editor
Changed the order of information pages for executed queries to be grouped by statements
Added
Optionalfor multiple cost and count metadata @datomoChanged
CyclicMetadataExceptionto followGenericRuntimeException@datomoFeatures
Tests
ToDo
CYPHER_EXTRACT_FROM_PATH, then enable corresponding tests inPolyAlgParsingTestbindArguments()and staticcreate()method). This can also be done at a later point, as it is only required for the rare use case of editing physical plans.