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

@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:

@late-eye-50215 was this added? i thought it was

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.

Noted: we'll pick it up next spring 👍 https://github.com/flyteorg/flyte/issues/3395

It looks like this is also a restriction in flytectl when generating execFiles:

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?

@icy-agent-73298, you did some structured datasets work in flytectl recently, correct? Should this still be handled in flytectl?

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 .

You can try registering

get_subset_df

task. https://docs.flyte.org/projects/cookbook/en/latest/auto/core/type_system/structured_dataset.html#sphx-glr-auto-core-type-[…]em-structured-dataset-py

yeah seems we need more changes for these. I can track improvements in flytectl as part of the same FE issue.