Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/3820#discussion_r23247815
--- Diff: docs/sql-programming-guide.md ---
@@ -581,6 +581,15 @@ Configuration of Parquet can be done using the
`setConf` method on SQLContext or
</td>
</tr>
<tr>
+ <td><code>spark.sql.parquet.int96AsTimestamp</code></td>
+ <td>true</td>
+ <td>
+ Some Parquet-producing systems, in particular Impala, store Timestamp
into INT96. Spark would also
+ store Timestamp as INT96 because we need to avoid precision lost of
the nanoseconds field. This
+ flag tells Spark SQL to interpret INT96 data as a timestamp to provide
compatibility with these systems.
+ </td>
+</tr>
--- End diff --
Yeah, I agree that it's weird though. Perhaps we should ask the parquet
list why they don't support the int 96 version.
On Jan 20, 2015 11:21 AM, "Cheng Lian" <[email protected]> wrote:
> In docs/sql-programming-guide.md
> <https://github.com/apache/spark/pull/3820#discussion-diff-23247492>:
>
> > @@ -581,6 +581,15 @@ Configuration of Parquet can be done using the
`setConf` method on SQLContext or
> > </td>
> > </tr>
> > <tr>
> > + <td><code>spark.sql.parquet.int96AsTimestamp</code></td>
> > + <td>true</td>
> > + <td>
> > + Some Parquet-producing systems, in particular Impala, store
Timestamp into INT96. Spark would also
> > + store Timestamp as INT96 because we need to avoid precision lost
of the nanoseconds field. This
> > + flag tells Spark SQL to interpret INT96 data as a timestamp to
provide compatibility with these systems.
> > + </td>
> > +</tr>
>
> Oh, I see the difference here. Double checked, Parquet only provides
> TIMESTAMP and TIMESTAMP_MILLIS
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/3820/files#r23247492>.
>
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
