[
https://issues.apache.org/jira/browse/DRILL-1965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274077#comment-14274077
]
Ramana Inukonda Nagaraj commented on DRILL-1965:
------------------------------------------------
I got that wrong.
0: jdbc:drill:> select cast(col1 as interval year) from
`/user/root/interval.json`;
+------------+
| EXPR$0 |
+------------+
| PT0S |
| PT0S |
| PT0S |
| PT0S |
| PT0S |
| P1Y2M |
| P2Y |
+------------+
7 rows selected (0.118 seconds)
And the interval.json looks like this:
{col1 : "P18582D"}
{col1 : "P1DT9045S"}
{col1 : "P1DT9000S"}
{col1 : "P10DT9000S"}
{col1 : "P1DT9045.100S"}
{col1 : "P1Y2M"}
{col1 : "P2Y"}
~
> Expand read and write testing for parquet across all supported types
> --------------------------------------------------------------------
>
> Key: DRILL-1965
> URL: https://issues.apache.org/jira/browse/DRILL-1965
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Jason Altekruse
> Assignee: Ramana Inukonda Nagaraj
> Attachments: DRILL-1965-WIP-parquet-file-all-types.patch
>
>
> The additional types we added to the parquet spec to allow use of parquet as
> a general purpose export format for drill query results have not all been
> thoroughly tested, we should make a better set of tests to ensure that the
> read and write path for the types are all working properly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
