The read part is empty as well, when the decoder is asked to read a
'null' type. For null carrying unions, I believe an index is written
out so if the index evals to a null, the same logic works yet again.
Does not matter if there are two nulls adjacent to one another,
therefore. How do you imagine this ends up being a problem? What
trouble are you running into?
On Mon, Jan 23, 2012 at 8:08 PM, Andrew Kenworthy
<[EMAIL PROTECTED]> wrote:
> I have looked at the Avro 1.6.0 code and am not sure how Avro distinguishes
> between field boundaries when reading null values.
> The BinaryEncoder class (which is where I land when debugging my code) has
> an empty method for writeNull: how does the parser then distinguuish between
> adjacent nullable fields when reading that data?
> Thanks in advance,
Customer Ops. Engineer, Cloudera