This is an automated email from the ASF dual-hosted git repository.
gangwu pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/orc.git
The following commit(s) were added to refs/heads/asf-site by this push:
new a1360d4 update site for timestamp description and pmc member
a1360d4 is described below
commit a1360d4446b82bd46d19e98cb6aa174d217cd108
Author: Gang Wu <[email protected]>
AuthorDate: Mon Feb 25 13:33:10 2019 -0800
update site for timestamp description and pmc member
---
develop/committers/index.html | 2 +-
specification/ORCv0/index.html | 6 +++---
specification/ORCv1/index.html | 6 +++---
specification/ORCv2/index.html | 6 +++---
4 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/develop/committers/index.html b/develop/committers/index.html
index b09bc4a..da498ee 100644
--- a/develop/committers/index.html
+++ b/develop/committers/index.html
@@ -143,7 +143,7 @@
<tr>
<td style="text-align: left">Gang Wu</td>
<td style="text-align: left">gangwu</td>
- <td style="text-align: left">Committer</td>
+ <td style="text-align: left">PMC</td>
</tr>
<tr>
<td style="text-align: left">Alan Gates</td>
diff --git a/specification/ORCv0/index.html b/specification/ORCv0/index.html
index 4845099..09ff103 100644
--- a/specification/ORCv0/index.html
+++ b/specification/ORCv0/index.html
@@ -1005,9 +1005,9 @@ number of nanoseconds.</p>
<p>Because the number of nanoseconds often has a large number of trailing
zeros, the number has trailing decimal zero digits removed and the
-last three bits are used to record how many zeros were removed. Thus
-1000 nanoseconds would be serialized as 0x0b and 100000 would be
-serialized as 0x0d.</p>
+last three bits are used to record how many zeros were removed. if the
+trailing zeros are more than 2. Thus 1000 nanoseconds would be
+serialized as 0x0a and 100000 would be serialized as 0x0c.</p>
<table>
<thead>
diff --git a/specification/ORCv1/index.html b/specification/ORCv1/index.html
index 33136da..6b57eb2 100644
--- a/specification/ORCv1/index.html
+++ b/specification/ORCv1/index.html
@@ -1370,9 +1370,9 @@ number of nanoseconds.</p>
<p>Because the number of nanoseconds often has a large number of trailing
zeros, the number has trailing decimal zero digits removed and the
-last three bits are used to record how many zeros were removed. Thus
-1000 nanoseconds would be serialized as 0x0b and 100000 would be
-serialized as 0x0d.</p>
+last three bits are used to record how many zeros were removed. if the
+trailing zeros are more than 2. Thus 1000 nanoseconds would be
+serialized as 0x0a and 100000 would be serialized as 0x0c.</p>
<table>
<thead>
diff --git a/specification/ORCv2/index.html b/specification/ORCv2/index.html
index 4311d33..c348a25 100644
--- a/specification/ORCv2/index.html
+++ b/specification/ORCv2/index.html
@@ -1385,9 +1385,9 @@ number of nanoseconds.</p>
<p>Because the number of nanoseconds often has a large number of trailing
zeros, the number has trailing decimal zero digits removed and the
-last three bits are used to record how many zeros were removed. Thus
-1000 nanoseconds would be serialized as 0x0b and 100000 would be
-serialized as 0x0d.</p>
+last three bits are used to record how many zeros were removed. if the
+trailing zeros are more than 2. Thus 1000 nanoseconds would be
+serialized as 0x0a and 100000 would be serialized as 0x0c.</p>
<table>
<thead>
