beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Cwik (JIRA)" <>
Subject [jira] [Commented] (BEAM-3493) Prevent users from "implementing" PipelineOptions
Date Fri, 19 Jan 2018 19:04:00 GMT


Luke Cwik commented on BEAM-3493:

We could just make sure that Pipeline.create(PipelineOptions) ensures that PipelineOptions
is always a proxy class of ProxyInvocationHandler. This would prevent people from creating
concrete implementations and any that are created would be ok to break since they wouldn't
be able to function with the Apache Beam APIs.

> Prevent users from "implementing" PipelineOptions
> -------------------------------------------------
>                 Key: BEAM-3493
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: sdk-java-core
>            Reporter: Kenneth Knowles
>            Assignee: Luke Cwik
>            Priority: Major
>              Labels: newbie, starter
> 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

View raw message