[ https://issues.jboss.org/browse/TEIID-4456?page=com.atlassian.jira.plugin... ] 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. -- This message was sent by Atlassian JIRA (v6.4.11#64026)