[
https://issues.apache.org/jira/browse/BEAM-9044?focusedWorklogId=409095&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-409095
]
ASF GitHub Bot logged work on BEAM-9044:
----------------------------------------
Author: ASF GitHub Bot
Created on: 24/Mar/20 21:12
Start Date: 24/Mar/20 21:12
Worklog Time Spent: 10m
Work Description: reuvenlax commented on pull request #10529: [BEAM-9044]
Protobuf options to Schema options
URL: https://github.com/apache/beam/pull/10529#discussion_r397464252
##########
File path:
sdks/java/extensions/protobuf/src/main/java/org/apache/beam/sdk/extensions/protobuf/ProtoSchemaTranslator.java
##########
@@ -205,10 +205,12 @@ static Schema getSchema(Descriptors.Descriptor
descriptor) {
// Store proto field number in metadata.
FieldType fieldType =
withMetaData(beamFieldTypeFromProtoField(fieldDescriptor),
fieldDescriptor);
Review comment:
I don't want to force all Beam option names to have a prefix - I think
that's the wrong approach. I'm suggesting that we create well-known prefixes
for these proto options (when translated to Beam options), so we can
distinguish them from other options. The prefixes you suggested sound fine to
me.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 409095)
Time Spent: 1.5h (was: 1h 20m)
> BIP-1: Convert protobuf options to Schema options
> -------------------------------------------------
>
> Key: BEAM-9044
> URL: https://issues.apache.org/jira/browse/BEAM-9044
> Project: Beam
> Issue Type: Sub-task
> Components: extensions-java-protobuf
> Reporter: Alex Van Boxel
> Assignee: Alex Van Boxel
> Priority: Minor
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> Protobuf has a rich metadata system called options. This system is fully
> typed and matches Beams Schema Option system. For now we can only convert the
> following protobuf options:
> * File Options -> _Beam doesn't have this concept_
> * Message Options -> *Beam Schema Options*
> * Field Options -> *Beam Schema Options*
> * Enum Options -> _This can only be done when logical type options are
> available_
> * EnumValue Options -> _This can only be done when logical type options are
> available_
> * Service Options -> _Beam doesn't have this concept_
> * Method Options -> _Beam doesn't have this concept_
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
