We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Note: this is bit tricky problem love to hear more feedback
trying to find sweet spot of "try not to introduce breaking change too much" vs "have more intuitive cli with v2 <> v1 generalization".
This is the cases where we use hdp most often:
we will have 4 command
hdp encode --request-query {FILE_PATH} --encoded-query {FILE_PATH}
hdp decode --encoded-query {FILE_PATH} --request-query {FILE_PATH}
and run command will support 2 type, each can be either by calling encoded request or raw request
hdp run-datalake --encoded-datalakes {BYTES} --encoded-tasks {BYTES} ... some etc arguments
hdp run-module --encoded-modules {BYTES} ... some etc arguments
and raw server request
hdp run --request-query {FILE_PATH}
The text was updated successfully, but these errors were encountered:
close with #115
Sorry, something went wrong.
No branches or pull requests
Note: this is bit tricky problem love to hear more feedback
trying to find sweet spot of "try not to introduce breaking change too much" vs "have more intuitive cli with v2 <> v1 generalization".
And also try to remove unnecessary serde/deserde and commands
Background
This is the cases where we use hdp most often:
we will have 4 command
and run command will support 2 type, each can be either by calling encoded request or raw request
and raw server request
The text was updated successfully, but these errors were encountered: