Skip to content
This repository has been archived by the owner on Oct 23, 2023. It is now read-only.

Add Presto query message #45

Merged
merged 4 commits into from
Mar 10, 2020
Merged

Add Presto query message #45

merged 4 commits into from
Mar 10, 2020

Conversation

lu4nm3
Copy link
Contributor

@lu4nm3 lu4nm3 commented Mar 4, 2020

This message is to support functionality for a Presto task

varshaparthay
varshaparthay previously approved these changes Mar 4, 2020
// This message works with the 'presto' task type in the SDK and is the object that will be in the 'custom' field
// of a Presto task's TaskTemplate
message PrestoQuery {
string routing_group = 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a concept of tags like qubole has for hive? are there any other metadata fields that our installation of presto has that would be helpful to include?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if not sure, +1

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

oh but can you bump the setup.py version so that this can be published to pypi?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wild-endeavor So there are a couple of ways that you can pass identifying information to Presto, but it's not through tags. First, there is the user which I was planning on deriving from a user's email if they log into Flyte. Then, you can also specify source which in this case will be flyte to indicate where the query is coming from. Here is a screenshot of what these fields look like from the Presto console for a particular query.
Screen Shot 2020-03-05 at 12 01 19 AM So to answer your original question, I think these should be a good set of starting fields. Should we need to add more in the future, I don't think it would be too much work.

Also, what version should I bump setup.py to? Currently it looks like it's set to 0.17.7. Can I just set it to 0.17.8?

@lu4nm3 lu4nm3 merged commit d62036e into master Mar 10, 2020
eapolinario pushed a commit that referenced this pull request Sep 8, 2023
* Add Presto query message

* add generated protos

* update ver
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants