Is it possible the the move to `StructuredDataset`...
# flyte-support
b
Is it possible the the move to
StructuredDataset
broke support for schema urls in the flyteconsole launch form? Not sure if it ever worked, but https://github.com/flyteorg/flyte/issues/405 seems to indicate it did. Given this example
Copy code
@task
def t1(df: pd.DataFrame) -> pd.DataFrame:
    return df

@workflow
def wf(df: pd.DataFrame) -> pd.DataFrame:
    return t1(df=df)
I get the following message in the launch form:
t
@late-eye-50215 was this added? i thought it was
t
Yeah. There's a problem with launching workflows that accept structured dataset as an input. We'll need to fix this. Despite giving a default value, it still isn't accepting the structured dataset and resulting in an error.
👍 1
l
Noted: we'll pick it up next spring 👍 https://github.com/flyteorg/flyte/issues/3395
👍 1
b
It looks like this is also a restriction in flytectl when generating execFiles:
Copy code
flytectl get launchplan my_launchplan --execFile exec.yaml

error creating default value for literal type  structured_dataset_type:<format:"parquet" > 
Error: failed to convert to a known Literal. Input Type [structured_dataset_type:<format:"parquet" > ] not supported
Should I create an issue?
t
@icy-agent-73298, you did some structured datasets work in flytectl recently, correct? Should this still be handled in flytectl?
i
yes this should have been working with latest flytectl . Could some one help with getting me example workflow or reference from cookbook which i can register and try creating an exec spec from it using flytectl .
i
yeah seems we need more changes for these. I can track improvements in flytectl as part of the same FE issue.
👍 1
152 Views