tree d9336745bd72276c9c8df68b412d2ec8caf777b9
parent 641424faebcdd39345b496e8bf83d869c40e458f
author Ritik Raj <raj.ritik9835@gmail.com> 1734015581 +0530
committer Peeyush Gupta <peeyush.gupta@couchbase.com> 1734037330 +0000

[ASTERIXDB-3534][STO] Fixed Reading definitionLevel for column having nulls

- user model changes: no
- storage format changes: no
- interface changes: no

Details:

- In cases where a column consists of both null values
  and nonNull values, there can be cases where in a single batch,
  one leafNode is written with all nulls while the other leafNode
  may contains same column with different type, where the "level" of the
  field can be different for null and non-null field.
  This change of level can cause the
  ParquetRunLengthBitPackingHybridDecoder
  to read more than required for pulling out a single definitionLevel,
  leading to early reading of all bytes and causing out of bytes error
  for furthur tupleNumber.

  This patch accomodates for that, by creating/reusing a
  different decoder when a column is reset with
  different maxLevel.

Ext-ref: MB-64486

Change-Id: Ia857e6520f5d2ae2f48a4fbbc9d647855649d145
Reviewed-on: https://asterix-gerrit.ics.uci.edu/c/asterixdb/+/19193
Reviewed-by: Ali Alsuliman <ali.al.solaiman@gmail.com>
Reviewed-by: Peeyush Gupta <peeyush.gupta@couchbase.com>
Tested-by: Peeyush Gupta <peeyush.gupta@couchbase.com>