You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Luke Cwik (Jira)" <ji...@apache.org> on 2019/11/19 19:42:00 UTC

[jira] [Resolved] (BEAM-3493) Prevent users from "implementing" PipelineOptions

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

Luke Cwik resolved BEAM-3493.
-----------------------------
    Fix Version/s: 2.18.0
       Resolution: Fixed

> Prevent users from "implementing" PipelineOptions
> -------------------------------------------------
>
>                 Key: BEAM-3493
>                 URL: https://issues.apache.org/jira/browse/BEAM-3493
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Jing Chen
>            Priority: Minor
>              Labels: newbie, starter
>             Fix For: 2.18.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> I've seen a user implement \{{PipelineOptions}}. This implies that it is backwards-incompatible to add new options, which is of course not our intent. We should at least document very loudly that it is not to be implemented, and preferably have some automation that will fail on load if they have implemented it. Ideas?



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