This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/parquet-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 93023a3 deploy: df3d5f946504aed3ba9a7b37d44069c1fcd070a4
93023a3 is described below
commit 93023a335b55c2e41a516ca56ca77f1f1a947446
Author: alamb <[email protected]>
AuthorDate: Thu Oct 23 20:59:33 2025 +0000
deploy: df3d5f946504aed3ba9a7b37d44069c1fcd070a4
---
output/docs/_print/index.html | 3 ++-
output/docs/file-format/_print/index.html | 3 ++-
output/docs/file-format/data-pages/_print/index.html | 3 ++-
output/docs/file-format/data-pages/encodings/index.html | 9 +++++----
output/docs/file-format/data-pages/index.xml | 3 ++-
output/docs/index.xml | 3 ++-
output/sitemap.xml | 2 +-
7 files changed, 16 insertions(+), 10 deletions(-)
diff --git a/output/docs/_print/index.html b/output/docs/_print/index.html
index 28b5723..5c4d952 100644
--- a/output/docs/_print/index.html
+++ b/output/docs/_print/index.html
@@ -362,7 +362,8 @@ repeated-value := value that is repeated, using a
fixed-width of round-up-to-nex
</code></pre><ol><li><p>The bit-packing here is done in a different order than
the one in the <a
href=/docs/file-format/data-pages/encodings/#BITPACKED>deprecated
bit-packing</a> 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:</p><p>The numbers 1 through 7 using bit width
3:</p><pre tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
+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.</p><p>The numbers 1 through 7 using bit width 3:</p><pre
tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
bit label: ABC DEF GHI JKL MNO PQR STU VWX
</code></pre><p>would be encoded like this where spaces mark byte boundaries
(3 bytes):</p><pre tabindex=0><code>bit value: 10001000 11000110 11111010
diff --git a/output/docs/file-format/_print/index.html
b/output/docs/file-format/_print/index.html
index 4cca596..fe9ba76 100644
--- a/output/docs/file-format/_print/index.html
+++ b/output/docs/file-format/_print/index.html
@@ -355,7 +355,8 @@ repeated-value := value that is repeated, using a
fixed-width of round-up-to-nex
</code></pre><ol><li><p>The bit-packing here is done in a different order than
the one in the <a
href=/docs/file-format/data-pages/encodings/#BITPACKED>deprecated
bit-packing</a> 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:</p><p>The numbers 1 through 7 using bit width
3:</p><pre tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
+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.</p><p>The numbers 1 through 7 using bit width 3:</p><pre
tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
bit label: ABC DEF GHI JKL MNO PQR STU VWX
</code></pre><p>would be encoded like this where spaces mark byte boundaries
(3 bytes):</p><pre tabindex=0><code>bit value: 10001000 11000110 11111010
diff --git a/output/docs/file-format/data-pages/_print/index.html
b/output/docs/file-format/data-pages/_print/index.html
index 4452ade..06a6531 100644
--- a/output/docs/file-format/data-pages/_print/index.html
+++ b/output/docs/file-format/data-pages/_print/index.html
@@ -68,7 +68,8 @@ repeated-value := value that is repeated, using a fixed-width
of round-up-to-nex
</code></pre><ol><li><p>The bit-packing here is done in a different order than
the one in the <a
href=/docs/file-format/data-pages/encodings/#BITPACKED>deprecated
bit-packing</a> 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:</p><p>The numbers 1 through 7 using bit width
3:</p><pre tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
+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.</p><p>The numbers 1 through 7 using bit width 3:</p><pre
tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
bit label: ABC DEF GHI JKL MNO PQR STU VWX
</code></pre><p>would be encoded like this where spaces mark byte boundaries
(3 bytes):</p><pre tabindex=0><code>bit value: 10001000 11000110 11111010
diff --git a/output/docs/file-format/data-pages/encodings/index.html
b/output/docs/file-format/data-pages/encodings/index.html
index 7c098f4..2213f8f 100644
--- a/output/docs/file-format/data-pages/encodings/index.html
+++ b/output/docs/file-format/data-pages/encodings/index.html
@@ -5,10 +5,10 @@ The plain encoding is used whenever a more efficient encoding
can not be used. I
BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><meta property="og:title"
content="Encodings"><meta property="og:description" content="P [...]
This is the plain encoding that must be supported for types. It is intended to
be the simplest encoding. Values are encoded back to back.
The plain encoding is used whenever a more efficient encoding can not be used.
It stores the data in the following format:
-BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><meta property="og:type"
content="article"><meta property="og:url" content="/docs/file-f [...]
+BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><meta property="og:type"
content="article"><meta property="og:url" content="/docs/file-f [...]
This is the plain encoding that must be supported for types. It is intended to
be the simplest encoding. Values are encoded back to back.
The plain encoding is used whenever a more efficient encoding can not be used.
It stores the data in the following format:
-BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><meta itemprop=dateModified
content="2024-03-11T22:11:10+01:00"><meta itemprop=wordCount [...]
+BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><meta itemprop=dateModified
content="2025-10-23T22:58:27+02:00"><meta itemprop=wordCount [...]
This is the plain encoding that must be supported for types. It is intended to
be the simplest encoding. Values are encoded back to back.
The plain encoding is used whenever a more efficient encoding can not be used.
It stores the data in the following format:
BOOLEAN: Bit Packed, LSB first INT32: 4 bytes little endian INT64: 8 bytes
little endian INT96: 12 bytes little endian (deprecated) FLOAT: 4 bytes IEEE
little endian DOUBLE: 8 bytes IEEE little endian BYTE_ARRAY: length in 4 bytes
little endian followed by the bytes contained in the array
FIXED_LEN_BYTE_ARRAY: the bytes contained in the array For native types, this
outputs the data as little endian."><link rel=preload
href=/scss/main.min.a33c1c4fab371eabb24ab6ba78781e08364e3b3186c475b3b9 [...]
@@ -43,7 +43,8 @@ repeated-value := value that is repeated, using a fixed-width
of round-up-to-nex
</code></pre><ol><li><p>The bit-packing here is done in a different order than
the one in the <a
href=/docs/file-format/data-pages/encodings/#BITPACKED>deprecated
bit-packing</a> 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:</p><p>The numbers 1 through 7 using bit width
3:</p><pre tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
+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.</p><p>The numbers 1 through 7 using bit width 3:</p><pre
tabindex=0><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
bit label: ABC DEF GHI JKL MNO PQR STU VWX
</code></pre><p>would be encoded like this where spaces mark byte boundaries
(3 bytes):</p><pre tabindex=0><code>bit value: 10001000 11000110 11111010
@@ -142,6 +143,6 @@ is allowed inside the data page.</p><p>Example:
Original data is three 32-bit floats and for simplicity we look at their raw
representation.</p><pre tabindex=0><code> Element 0 Element 1
Element 2
Bytes AA BB CC DD 00 11 22 33 A3 B4 C5 D6
</code></pre><p>After applying the transformation, the data has the following
representation:</p><pre tabindex=0><code>Bytes AA 00 A3 BB 11 B4 CC 22 C5 DD
33 D6
-</code></pre><div class=td-page-meta__lastmod>Last modified March 11, 2024: <a
href=https://github.com/apache/parquet-site/commit/e79b30489c6bd50f0829a5f2b87f4a26f5e4af05>Fix
typos (#46) (e79b304)</a></div></div></main></div></div><footer
class="td-footer row d-print-none"><div class=container-fluid><div class="row
mx-md-2"><div class="td-footer__left col-6 col-sm-4 order-sm-1"><ul
class=td-footer__links-list><li class=td-footer__links-item
data-bs-toggle=tooltip title="Post to Mailing L [...]
+</code></pre><div class=td-page-meta__lastmod>Last modified October 23, 2025:
<a
href=https://github.com/apache/parquet-site/commit/df3d5f946504aed3ba9a7b37d44069c1fcd070a4>Clarify
Bit-Packing doc example positioning (#29)
(df3d5f9)</a></div></div></main></div></div><footer class="td-footer row
d-print-none"><div class=container-fluid><div class="row mx-md-2"><div
class="td-footer__left col-6 col-sm-4 order-sm-1"><ul
class=td-footer__links-list><li class=td-footer__links-item data-bs-tog [...]
2025
<span class=td-footer__authors>Apache Parquet</span></span><span
class=td-footer__all_rights_reserved>All Rights Reserved</span><span
class=ms-2><a href=https://policies.google.com/privacy target=_blank
rel=noopener>Privacy Policy</a></span></div></div></div></footer></div><script
src=/js/main.min.26b35480299b932e285af8358c943de97509b95a0086d091584e7cb9b00c5c7b.js
integrity="sha256-JrNUgCmbky4oWvg1jJQ96XUJuVoAhtCRWE58ubAMXHs="
crossorigin=anonymous></script><script defer src=/js/click-to [...]
\ No newline at end of file
diff --git a/output/docs/file-format/data-pages/index.xml
b/output/docs/file-format/data-pages/index.xml
index 43e4faa..08c6886 100644
--- a/output/docs/file-format/data-pages/index.xml
+++ b/output/docs/file-format/data-pages/index.xml
@@ -111,7 +111,8 @@ repeated-value := value that is repeated, using a
fixed-width of round-up-to-nex
<p>The bit-packing here is done in a different order than the one in the
<a href="/docs/file-format/data-pages/encodings/#BITPACKED">deprecated
bit-packing</a> 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:</p>
+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.</p>
<p>The numbers 1 through 7 using bit width 3:</p>
<pre tabindex="0"><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
diff --git a/output/docs/index.xml b/output/docs/index.xml
index f92e944..5437c2b 100644
--- a/output/docs/index.xml
+++ b/output/docs/index.xml
@@ -111,7 +111,8 @@ repeated-value := value that is repeated, using a
fixed-width of round-up-to-nex
<p>The bit-packing here is done in a different order than the one in the
<a href="/docs/file-format/data-pages/encodings/#BITPACKED">deprecated
bit-packing</a> 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:</p>
+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.</p>
<p>The numbers 1 through 7 using bit width 3:</p>
<pre tabindex="0"><code>dec value: 0 1 2 3 4 5 6 7
bit value: 000 001 010 011 100 101 110 111
diff --git a/output/sitemap.xml b/output/sitemap.xml
index 7ef7c33..cdbf75d 100644
--- a/output/sitemap.xml
+++ b/output/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/file-format/data-pages/compression/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encodings/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encryption/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/file-format/data-pages/compression/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encodings/</loc><lastmod>2025-10-23T22:58:27+02:00</lastmod></url><url><loc>/docs/file-format/data-pages/encryption/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/
[...]
\ No newline at end of file
