...
(situation 2.20)
Without this proposal, if a user want the act on extra contextual information that is available in the schema she needs to act on this information out of the pipeline. This means that these implementations will be very format specific (a separate implementation for Protobuf, Avro, Json, etc...).
Table of Contents |
---|
History
Revision
DATE | AUTHOR | DESCRIPTION |
---|---|---|
2019-02-28 | Alex Van Boxel | Changed to Accepted Proposal |
2019-01-01 | Alex Van Boxel | Initial Proposal |
Vote
This proposal has been accepted on February 28, 2020 after a 7 day voting period: [VOTE]
+1 | 7 votes (3 binding) |
-1 | 0 votes |
Implementation choice
Typed options
...
It would be possible to implement options in the Java SDK only and not be included in the model. But doing this would be confusing in cross platform pipelines. If you have options read by the Java implementation, go with a row to a Python transform and then back to Java while loosing the options along the way would be confusing for the user.
Open Issues
BIP-1a : ...
...
...
Implementation Detail
Beam API
...