You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Kenneth Knowles (Jira)" <ji...@apache.org> on 2021/08/17 12:52:00 UTC

[jira] [Updated] (BEAM-12767) Improve UX of PipelineOptions parsing

     [ https://issues.apache.org/jira/browse/BEAM-12767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kenneth Knowles updated BEAM-12767:
-----------------------------------
    Status: Open  (was: Triage Needed)

> Improve UX of PipelineOptions parsing
> -------------------------------------
>
>                 Key: BEAM-12767
>                 URL: https://issues.apache.org/jira/browse/BEAM-12767
>             Project: Beam
>          Issue Type: Improvement
>          Components: sdk-java-core
>            Reporter: Steve Niemitz
>            Assignee: Steve Niemitz
>            Priority: P2
>
> Attempting to parse complex types in PipelineOptions can have a suboptimal UX.  For example, if the option type being parsed is an Instant, simply passing in:
> {{--myInstant=2021-07-17 }}{{will fail.  Instead the user must pass in --myInstant="2021-07-17"}}{{, however, this is complicated by the fact that the quotes will be stripped from the arguments in many cases, requiring a user to actually pass in --myInstant='"2021-07-17"'.  }}
> This can be improved by attempting to parse the input twice, once as-is, and then trying again by automatically wrapping it in quotes.
> Additionally, it's impossible to use a custom JsonDeserializer on a pipeline option property.  We should allow using @JsonDeserialize on the getters to supply a custom one.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)