-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
refactor: sql_json view endpoint: use execution context instead of query #16677
refactor: sql_json view endpoint: use execution context instead of query #16677
Conversation
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.
rename SqlJsonExecutionStatus options
Codecov Report
@@ Coverage Diff @@
## master #16677 +/- ##
==========================================
+ Coverage 76.91% 76.93% +0.01%
==========================================
Files 1005 1005
Lines 54017 54044 +27
Branches 7337 7337
==========================================
+ Hits 41549 41577 +28
+ Misses 12228 12227 -1
Partials 240 240
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM
…ery (apache#16677) * refactor sql_json view endpoint: use execution context instead of query * fix failed tests * fix failed tests * refactor renaming enum options
…ery (apache#16677) * refactor sql_json view endpoint: use execution context instead of query * fix failed tests * fix failed tests * refactor renaming enum options
SUMMARY
The sql_json view code in superset core view without any "clean code" standard and it does not adopt any software development principle.
This is the twelveth PR in the sequence of future PRs (previous PR) try to solve it by refactoring the code.
The PR focus on start using execution context to create the final response and get an execution status from the private method who will be refactored soon to a Command class
This is the second PR who build the basis so the code will be able to be separated into layers
there are no logic changes so it implies on the current tests.