[ 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 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. was: Change configuration to enable the specification of all the protobuf descriptors to use. Currently, only the root protobuf descriptor is configured in the resource-adapter. Example: {code} <config-property name="MessageDescriptor"> bigdata.DataEntity </config-property> {code} and expect the .proto file to configure the relationship for the child descriptor within the parent: Example: {code} package bigdata; message DataEntity { .. optional MetaData context = 6; message MetaData { ... } } {code} and the metadata process can derive the children descriptors from the root descriptor. However, if all message descriptors are specified, that would allow for defining children message at the root level (outside the parent). And would allow the message descriptor to be shared among other messages. -- This message was sent by Atlassian JIRA (v6.4.11#64026)