Github user marmbrus commented on a diff in the pull request:
https://github.com/apache/spark/pull/3820#discussion_r23246274
--- 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 --
Do they? As far as I can tell the parquet spec does not have a nanosecond
precision timestamp type.
On Jan 20, 2015 12:26 AM, "Cheng Lian" <[email protected]> wrote:
> In docs/sql-programming-guide.md
> <https://github.com/apache/spark/pull/3820#discussion-diff-23207993>:
>
> > @@ -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>
>
> I'm probably OK with this property. Just wanna ask doesn't Impala store
> original type information (TIMESTAMP) together in Parquet metainfo?
>
> â
> Reply to this email directly or view it on GitHub
> <https://github.com/apache/spark/pull/3820/files#r23207993>.
>
---
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]
