[jira] [Updated] (DRILL-5034) Select timestamp from hive generated parquet always return in UTC

[ https://issues.apache.org/jira/browse/DRILL-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheesh Katkam updated DRILL-5034: --- Fix Version/s: (was: 1.9.0) > Select timestamp from hive generated parquet always return

[jira] [Updated] (DRILL-4373) Drill and Hive have incompatible timestamp representations in parquet

[ https://issues.apache.org/jira/browse/DRILL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheesh Katkam updated DRILL-4373: --- Fix Version/s: (was: 1.9.0) > Drill and Hive have incompatible timestamp representations

[jira] [Reopened] (DRILL-4848) Minor correction in UDF's documentation

[ https://issues.apache.org/jira/browse/DRILL-4848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli reopened DRILL-4848: -- The example in step 3 is still wrong. Also I am not sure if we need the example > Minor

[jira] [Updated] (DRILL-4971) query encounters system error: Statement "break AndOP3" is not enclosed by a breakable statement with label "AndOP3"

[ https://issues.apache.org/jira/browse/DRILL-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Hou updated DRILL-4971: -- Description: This query returns an error. The stack trace suggests it might be a schema change issue,

[jira] [Closed] (DRILL-4342) Drill fails to read a date column from hive generated parquet

[ https://issues.apache.org/jira/browse/DRILL-4342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli closed DRILL-4342. > Drill fails to read a date column from hive generated parquet >

[jira] [Commented] (DRILL-4971) query encounters system error: Statement "break AndOP3" is not enclosed by a breakable statement with label "AndOP3"

[ https://issues.apache.org/jira/browse/DRILL-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15658487#comment-15658487 ] Robert Hou commented on DRILL-4971: --- The same problem occurs on 1.8.0. > query encounters system error:

[jira] [Updated] (DRILL-5038) Drill's new parquet reader complains schema change when there is none

[ https://issues.apache.org/jira/browse/DRILL-5038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-5038: - Attachment: min_max_dir.tgz {code} 2016-11-11 14:41:42,866

[jira] [Created] (DRILL-5038) Drill's new parquet reader complains schema change when there is none

Rahul Challapalli created DRILL-5038: Summary: Drill's new parquet reader complains schema change when there is none Key: DRILL-5038 URL: https://issues.apache.org/jira/browse/DRILL-5038 Project:

[jira] [Updated] (DRILL-5034) Select timestamp from hive generated parquet always return in UTC

[ https://issues.apache.org/jira/browse/DRILL-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheesh Katkam updated DRILL-5034: --- Description: commit id: 5cea9afa6278e21574c6a982ae5c3d82085ef904 Reading timestamp data

[jira] [Closed] (DRILL-4894) Fix unit test failure in 'storage-hive/core' module

[ https://issues.apache.org/jira/browse/DRILL-4894?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Girish closed DRILL-4894. -- > Fix unit test failure in 'storage-hive/core' module >

[jira] [Closed] (DRILL-5009) Query with a simple join fails on Hive generated parquet

[ https://issues.apache.org/jira/browse/DRILL-5009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Girish closed DRILL-5009. -- > Query with a simple join fails on Hive generated parquet >

[jira] [Commented] (DRILL-4971) query encounters system error: Statement "break AndOP3" is not enclosed by a breakable statement with label "AndOP3"

[ https://issues.apache.org/jira/browse/DRILL-4971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657919#comment-15657919 ] Rahul Challapalli commented on DRILL-4971: -- [~rhou] Did you get a chance to check whether this is

[jira] [Commented] (DRILL-5037) NPE in Parquet Decimal Converter with the complex parquet reader

[ https://issues.apache.org/jira/browse/DRILL-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657916#comment-15657916 ] Rahul Challapalli commented on DRILL-5037: -- The above error occurred when the query is run using

[jira] [Updated] (DRILL-5037) NPE in Parquet Decimal Converter with the complex parquet reader

[ https://issues.apache.org/jira/browse/DRILL-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-5037: - Description: git.commit.id.abbrev=4b1902c The below query fails when we enable the new

[jira] [Updated] (DRILL-5037) NPE in Parquet Decimal Converter

[ https://issues.apache.org/jira/browse/DRILL-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-5037: - Summary: NPE in Parquet Decimal Converter (was: Random NPE in Parquet Decimal

[jira] [Assigned] (DRILL-5034) Select timestamp from hive generated parquet always return in UTC

[ https://issues.apache.org/jira/browse/DRILL-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kunal Khatua reassigned DRILL-5034: --- Assignee: Kunal Khatua (was: Vitalii Diravka) > Select timestamp from hive generated

[jira] [Commented] (DRILL-4373) Drill and Hive have incompatible timestamp representations in parquet

[ https://issues.apache.org/jira/browse/DRILL-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657809#comment-15657809 ] Vitalii Diravka commented on DRILL-4373: The known

[jira] [Updated] (DRILL-5037) Random NPE in Parquet Decimal Converter

[ https://issues.apache.org/jira/browse/DRILL-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-5037: - Summary: Random NPE in Parquet Decimal Converter (was: NPE in Parquet Decimal Converter)

[jira] [Updated] (DRILL-5037) NPE in Parquet Decimal Converter

[ https://issues.apache.org/jira/browse/DRILL-5037?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rahul Challapalli updated DRILL-5037: - Attachment: drill5037.parquet Error from the logs : {code} 2016-11-10 23:14:50,269

[jira] [Created] (DRILL-5037) NPE in Parquet Decimal Converter

Rahul Challapalli created DRILL-5037: Summary: NPE in Parquet Decimal Converter Key: DRILL-5037 URL: https://issues.apache.org/jira/browse/DRILL-5037 Project: Apache Drill Issue Type:

[jira] [Commented] (DRILL-5034) Select timestamp from hive generated parquet always return in UTC

[ https://issues.apache.org/jira/browse/DRILL-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15657706#comment-15657706 ] Vitalii Diravka commented on DRILL-5034: As for me it is not a bug. Accordingly to the [spec

[jira] [Issue Comment Deleted] (DRILL-5027) ExternalSortBatch is inefficient: rewrites data unnecessarily

[ https://issues.apache.org/jira/browse/DRILL-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5027: --- Comment: was deleted (was: Inspection reveals that the intermediate spill events do not clean up the

[jira] [Updated] (DRILL-5027) ExternalSortBatch is inefficient: rewrites data unnecessarily

[ https://issues.apache.org/jira/browse/DRILL-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Rogers updated DRILL-5027: --- Summary: ExternalSortBatch is inefficient: rewrites data unnecessarily (was: ExternalSortBatch is

[jira] [Closed] (DRILL-4792) Include session options used for a query as part of the profile

[ https://issues.apache.org/jira/browse/DRILL-4792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Krystal closed DRILL-4792. -- Verified that feature is working as expected. There is a minor issue with the formatting of the jsonOptions in

[jira] [Created] (DRILL-5036) The session options used for a query is not nicely formated in the JSON Profile

Krystal created DRILL-5036: -- Summary: The session options used for a query is not nicely formated in the JSON Profile Key: DRILL-5036 URL: https://issues.apache.org/jira/browse/DRILL-5036 Project: Apache

[jira] [Updated] (DRILL-5034) Select timestamp from hive generated parquet always return in UTC

[ https://issues.apache.org/jira/browse/DRILL-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-5034: Assignee: Vitalii Diravka > Select timestamp from hive generated parquet always return in

[jira] [Reopened] (DRILL-4653) Malformed JSON should not stop the entire query from progressing

[ https://issues.apache.org/jira/browse/DRILL-4653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khurram Faraaz reopened DRILL-4653: --- > Malformed JSON should not stop the entire query from progressing >

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656486#comment-15656486 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sohami commented on a diff in the pull request:

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656485#comment-15656485 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sohami commented on a diff in the pull request:

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656488#comment-15656488 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sohami commented on a diff in the pull request:

[jira] [Commented] (DRILL-5015) As per documentation, when issuing a list of drillbits in the connection string, we always attempt to connect only to the first one

[ https://issues.apache.org/jira/browse/DRILL-5015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15656487#comment-15656487 ] ASF GitHub Bot commented on DRILL-5015: --- Github user sohami commented on a diff in the pull request: