This is an automated email from the ASF dual-hosted git repository.
alamb pushed a commit to branch production
in repository https://gitbox.apache.org/repos/asf/parquet-site.git
The following commit(s) were added to refs/heads/production by this push:
new df3d5f9 Clarify Bit-Packing doc example positioning (#29)
df3d5f9 is described below
commit df3d5f946504aed3ba9a7b37d44069c1fcd070a4
Author: Kuba Grzechociński <[email protected]>
AuthorDate: Thu Oct 23 22:58:27 2025 +0200
Clarify Bit-Packing doc example positioning (#29)
When reading through the documentation I stumbled upon the Hybrid
Bit-Packing section. The section is currently above the deprecated Bit-Packing
encoding section, but refers to the example in the latter in a way that
presumes the reader has already read it, which left me sightly confused.
Here's an attempt to better point the reader to the other example so that
he can easier compare both methods.
---
content/en/docs/File Format/Data Pages/encodings.md | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/content/en/docs/File Format/Data Pages/encodings.md
b/content/en/docs/File Format/Data Pages/encodings.md
index ea27d46..5f6429f 100644
--- a/content/en/docs/File Format/Data Pages/encodings.md
+++ b/content/en/docs/File Format/Data Pages/encodings.md
@@ -71,7 +71,8 @@ repeated-value := value that is repeated, using a fixed-width
of round-up-to-nex
1. The bit-packing here is done in a different order than the one in the
[deprecated bit-packing](#BITPACKED) encoding.
The values are packed from the least significant bit of each byte to the
most significant bit,
though the order of the bits in each value remains in the usual order of
most significant to least
- significant. For example, to pack the same values as the example in the
deprecated encoding above:
+ significant. An example of the encoding is presented below. For comparison,
the same case is shown
+ in the example of the deprecated bit-packing encoding in the next section.
The numbers 1 through 7 using bit width 3:
```
