[teiid-issues] [JBoss JIRA] (TEIID-4456) Enable the abiltiy to support nested and non-nested message descriptors

[Van Halbert (JIRA)]

     [ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Van Halbert updated TEIID-4456:
-------------------------------
    Description: 
Protobuf definition files can have messages defined in a nested and non-nested form. 

Nested:

{code}
package bigdata;
message DataEntity {
..
   optional MetaData context = 6;

  message MetaData {
 ... 
 }
}
{code}

Non-nested:
{code}
package bigdata;

message DataEntity {
..
   optional MetaData context = 6;
}
  message MetaData {
 ... 
 }

{code}

The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case.  

Currently it obtains the child descriptor messages from the parent descriptor. 

  was:
Protobuf definition files can have messages defined in a nested and non-nested from.

Nested:

{code}
package bigdata;
message DataEntity {
..
   optional MetaData context = 6;

  message MetaData {
 ... 
 }
}
{code}

Non-nested:
{code}
package bigdata;

message DataEntity {
..
   optional MetaData context = 6;
}
  message MetaData {
 ... 
 }

{code}

The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case.  

Currently it obtains the child descriptor messages from the parent descriptor. 



> Enable the abiltiy to support nested and non-nested message descriptors
> -----------------------------------------------------------------------
>
>                 Key: TEIID-4456
>                 URL: https://issues.jboss.org/browse/TEIID-4456
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: Misc. Connectors
>    Affects Versions: 9.2
>            Reporter: Van Halbert
>            Assignee: Van Halbert
>
> Protobuf definition files can have messages defined in a nested and non-nested form. 
> Nested:
> {code}
> package bigdata;
> message DataEntity {
> ..
>    optional MetaData context = 6;
>   message MetaData {
>  ... 
>  }
> }
> {code}
> Non-nested:
> {code}
> package bigdata;
> message DataEntity {
> ..
>    optional MetaData context = 6;
> }
>   message MetaData {
>  ... 
>  }
> {code}
> The ProtobufMetadataProcessor needs to be changed to so that it can create the metadata from either use case.  
> Currently it obtains the child descriptor messages from the parent descriptor. 



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)