to have that feature?
Original message
From: Randy Abernethy <r...@apache.org>
Date: 2018-01-18 9:18 PM (GMT-05:00)
To: dev@thrift.apache.org
Cc: u...@thrift.apache.org
Subject: Re: Is the Thrift serialization compatible both directions?
Taking this apart:
- Any new fields th
Taking this apart:
- Any new fields that you add should be optional.
I disagree, default requiredness with a default value works fine as well
(and is my preference if you are not interested in optimizing the field
away in procs that know about it). On the server side,if the default field
is there
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