alamb commented on PR #76:
URL: https://github.com/apache/parquet-testing/pull/76#issuecomment-2871924119
> @alamb I noticed that:
>
> 1. decimal is named as {4|8|16} not {32|64|128}
I tried to follow the naming in the table from
[VariantEncoding.md](https://github.com/apache/parquet-format/blob/master/VariantEncoding.md#encoding-types)
which uses those terms
Exact Numeric | decimal4 | 8 | DECIMAL(precision, scale) | 1 byte scale in
range [0, 38], followed by little-endian unscaled value (see decimal table)
-- | -- | -- | -- | --
Exact Numeric | decimal8 | 9 | DECIMAL(precision, scale) | 1 byte scale in
range [0, 38], followed by little-endian unscaled value (see decimal table)
Exact Numeric | decimal16 | 10 | DECIMAL(precision, scale) | 1 byte scale in
range [0, 38], followed by little-endian unscaled value (see decimal table)
> 2. Null object metadata is empty, is this expected?
This is probably not right -- it is likely an artifact of how spark wrote
the parquet file (probably with a parquet null rather than a null in the
object). I filed a ticket to track it:
- https://github.com/apache/parquet-testing/issues/81 to track
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
