You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Bridget Bevens (JIRA)" <ji...@apache.org> on 2017/03/27 19:06:41 UTC
[jira] [Commented] (DRILL-5388) Correct Parquet reader option name
in documentation
[ https://issues.apache.org/jira/browse/DRILL-5388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15943855#comment-15943855 ]
Bridget Bevens commented on DRILL-5388:
---------------------------------------
Updated the option on the following pages:
https://drill.apache.org/blog/2017/03/15/drill-1.10-released/
https://drill.apache.org/docs/parquet-format/#about-int96-support
https://drill.apache.org/docs/configuration-options-introduction/
You may need to refresh the pages to see the updates.
Setting status to "Resolved."
> Correct Parquet reader option name in documentation
> ---------------------------------------------------
>
> Key: DRILL-5388
> URL: https://issues.apache.org/jira/browse/DRILL-5388
> Project: Apache Drill
> Issue Type: Bug
> Components: Documentation
> Reporter: Bridget Bevens
> Assignee: Bridget Bevens
> Fix For: 1.10.0
>
>
> You need to update this link also.
> https://drill.apache.org/docs/parquet-format/#about-int96-support
> Parquet Format - Apache Drill
> drill.apache.org
> Configuring the Parquet Storage Format. To read or write Parquet data, you need to include the Parquet format in the storage plugin format definitions.
> Yes, you are right. We need to update the documentation with
> the correct option name. Thanks for bringing it up.
> |
> Today, 1:57 AM
> > According to this page
> > <https://drill.apache.org/blog/2017/03/15/drill-1.10-released/>, Drill can
> > implicitly interprets the INT96 timestamp data type in Parquet files after
> > setting the *store.parquet.int96_as_timestamp* option to *true*.
> >
> > I believe the option name should be
> > *store.parquet.reader.int96_as_timestamp*
> >\
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)