thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <>
Subject Re: static vs dynamic typing
Date Sun, 31 Aug 2014 16:12:33 GMT
Neither are an incredibly great fit when the schema is unknown. In protobuf
after you deser a record there is a map<binary,binary> called unknownFields
(or something to that effect) and all the unknown fields land in there.

If that happens you are probably "doing it wrong" as you should release
your new schema from leaf applications to root applications so that no one
ever needs to see a record with fields they do not understand.

On Sun, Aug 31, 2014 at 8:39 AM, Jens Geyer <> wrote:

> Hi,
>  Just wondering if Avro or Thrift are equally suitable when the  source
>> schema is unknown.
> No. Avro holds the schema within the data.
> Thrift does not do this (performance), the schema must be known to all
> parties up front.
> However, due to soft-versioning, the Thrift-producing/consuming parties
> are not forced to "speak" the same version of the Thrift contract, so there
> is some flexibility built into the system.
> Have fun,
> JensG

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message