serialized along with it — so if
the message is passed on to new code, the new fields are still available.
This is inaccurate. If you use Thrift "normally", when you deserialize, the
struct (message) will only contain the fields you know (in any
requiredness).
--Randy
On Thu, Jan 18, 20
Hi,
Is this statement true, especially the last part? (from:
https://diwakergupta.github.io/thrift-missing-guide/)
Any new fields that you add should be optional. This means that any messages
serialized by code using your "old" message format can be parsed by your new
generated code, as
Hi,
Is this statement true, especially the last part?
Any new fields that you add should be optional. This means that any messages
serialized by code using your "old" message format can be parsed by your new
generated code, as they won’t be missing any required elements. Similarly,
messages
Hi,
Is this statement true, especially the last part? (from:
https://diwakergupta.github.io/thrift-missing-guide/)
Any new fields that you add should be optional. This means that any messages
serialized by code using your "old" message format can be parsed by your new
generated code, as they
