Extensions are a nice tool for breaking up message management between teams.  
Let say you have a product that keeps track of people like the white pages and 
you have a core group that manages your primary functionality as well as 
satellite teams that provide different extended functionality like profession 
management like linked-in or grouping people by interests like a social 
platform.  You can carve out a space in your core Person message for extensions 
management by other teams.  For example:

// Person.protopackage people;

message Person {
        optional string firstName = 1;
        optional string lastName = 2;
        extensions 100 to 1000;
}

// Profession.proto
message Profession {
        required string industry = 1;
        required string title = 2;
}
extend people.Person {
        optional Profession profession = 100;
}
// Interests.proto
message Interests {
        repeated string tags = 1;
}
extend people.Person {
        optional Interests interests = 101;
}

      From: lukas nalezenec <lukas.naleze...@gmail.com>
 To: dev@parquet.incubator.apache.org; Chris Luby <clubyco...@yahoo.com> 
 Sent: Saturday, March 28, 2015 3:23 PM
 Subject: Re: Protobuf extension support in parquet-protobuf
   
Hi,
There is really no extension support in parquet protobuf. I have never worked 
with protobuf extensions - I can't imagine what the extensions support in 
parquet-protobuf would do. Can you please write more about it ? It might be 
good idea.

Lukas




On Sat, Mar 28, 2015 at 9:23 AM, Chris Luby <clubyco...@yahoo.com.invalid> 
wrote:

It appears that unless I'm missing something that there isn't support for 
protobuf messages using extensions in parquet-protobuf.  If I'm missing 
something and they are supported let me know.  If it is the case that they are 
currently not supported I'm thinking about doing the work to add the support.  
Have any thoughts been but into adding support yet?  If interfaces have already 
been thought out for this I should probably start there instead of from scratch.
 



  

Reply via email to