[
https://issues.apache.org/jira/browse/BEAM-12767?focusedWorklogId=645454&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-645454
]
ASF GitHub Bot logged work on BEAM-12767:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 01/Sep/21 18:13
Start Date: 01/Sep/21 18:13
Worklog Time Spent: 10m
Work Description: steveniemitz edited a comment on pull request #15338:
URL: https://github.com/apache/beam/pull/15338#issuecomment-910533042
roll-forward PR up as well: #15439 , I'm not sure if the trigger phrase
worked for that one though, maybe I don't have permissions?
I'd love to figure out how to reproduce this in a unit test as well, it
seems like we're missing coverage over something pretty fundamental.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 645454)
Time Spent: 16h 20m (was: 16h 10m)
> 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
> Fix For: 2.34.0
>
> Time Spent: 16h 20m
> Remaining Estimate: 0h
>
> 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)
