ASF GitHub Bot logged work on BEAM-9044:

                Author: ASF GitHub Bot
            Created on: 24/Mar/20 08:33
            Start Date: 24/Mar/20 08:33
    Worklog Time Spent: 10m 
      Work Description: alexvanboxel commented on pull request #10529: 
[BEAM-9044] Protobuf options to Schema options
URL: https://github.com/apache/beam/pull/10529#discussion_r396977813

 File path: 
 @@ -205,10 +205,12 @@ static Schema getSchema(Descriptors.Descriptor 
descriptor) {
         // Store proto field number in metadata.
         FieldType fieldType =
 Review comment:
   Is it, I don't think so... because I told Reuven I would do metadata after 
this. Still I think it's a good idea... and with your comment I want to revise 
the URI:
   - `beam:option:proto:field:vptech.data.v1.description` for a proto field 
   - `beam:option:proto:message:vptech.data.v1.description` for a proto message 
   - `beam:option:proto:meta:number` for a proto field number
   - `beam:option:proto:meta:type_name` for a proto type name
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:

Issue Time Tracking

    Worklog Id:     (was: 408592)
    Time Spent: 1h 20m  (was: 1h 10m)

> 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: 1h 20m
>  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

Reply via email to