[BEAM-3493] Prevent users from "implementing" PipelineOptions

• Type: Bug
• Status: Resolved
• Priority: P3
• Resolution: Fixed
• Fix Version/s: 2.18.0
• Component/s: sdk-java-core
• Labels: Done newbie starter
• Assignee: Jing Chen
• Reporter: Kenneth Knowles
• Created: 18/Jan/18 04:34
• Updated: 06/Oct/20 21:50
• Resolved: 19/Nov/19 19:41

Description

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?

Issue Links

• links to: GitHub Pull Request #10005