Skip to content
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

Add --raw-output-data-prefix to the pyflyte-execute command #167

Merged
merged 9 commits into from
Aug 27, 2020

Conversation

wild-endeavor
Copy link
Contributor

@wild-endeavor wild-endeavor commented Aug 25, 2020

TL;DR

Please see the linked issue for more information. This adds a --raw-output-data-prefix switch to the pyflyte-execute command and container args will be changed so that they're registered with --raw-data-output-prefix {{.rawOutputDataPrefix}}. Propeller will then fill them in.

Release this change last, after testing propeller/plugins

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Complete description

  • The AWS and GCP data proxy classes now take in its constructor a prefix which will be used when get_random_path is called. If it is missing it will fall back to the current behavior of looking up either the S3 shard formatter config or the GCS prefix config.
  • Added switch to click command
  • Added switch and template placeholder to sdk runnable task and notebook task container args.

Tracking Issue

flyteorg/flyte#211

Follow-up issue

NA

@@ -447,6 +447,8 @@ def _get_container_definition(
"{{.input}}",
"--output-prefix",
"{{.outputPrefix}}",
"--raw-data-output-prefix",
"{{.outputPrefix}}"
Copy link
Collaborator

Choose a reason for hiding this comment

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

This should be raw output prefix, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yeah this is when i realized that flyteplugins wasn't done

flytekit/bin/entrypoint.py Show resolved Hide resolved
@wild-endeavor wild-endeavor changed the title wip Add --raw-output-data-prefix to the pyflyte-execute command Aug 26, 2020
Yee Hing Tong added 2 commits August 26, 2020 13:21
@kumare3
Copy link
Contributor

kumare3 commented Aug 27, 2020

Hurrah! One step closer to portable Workflows. Definitely all the examples will be portable

@@ -83,7 +83,8 @@ def _execute_task(task_module, task_name, inputs, output_prefix, test):
_data_proxy.Data.get_data(inputs, local_inputs_file)
input_proto = _utils.load_proto_from_file(_literals_pb2.LiteralMap, local_inputs_file)
_engine_loader.get_engine().get_task(task_def).execute(
_literal_models.LiteralMap.from_flyte_idl(input_proto), context={"output_prefix": output_prefix},
_literal_models.LiteralMap.from_flyte_idl(input_proto),
Copy link
Contributor

Choose a reason for hiding this comment

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

wow this seems some hairy logic

Copy link
Contributor

@kumare3 kumare3 left a comment

Choose a reason for hiding this comment

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

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants