[jira] [Commented] (DRILL-6994) TIMESTAMP type DOB column in Spark parquet is treated as VARBINARY in Drill

[ https://issues.apache.org/jira/browse/DRILL-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749568#comment-16749568 ] Khurram Faraaz commented on DRILL-6994: --- [~kkhatua]  here are the parquet schema details {noformat}

[jira] [Commented] (DRILL-6827) Apache Drill 1.14 on a kerberized Cloudera cluster (CDH 5.14).

[ https://issues.apache.org/jira/browse/DRILL-6827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749564#comment-16749564 ] Sorabh Hamirwasia commented on DRILL-6827: -- Your configurations is incorrect. Please refer to

[jira] [Commented] (DRILL-6994) TIMESTAMP type DOB column in Spark parquet is treated as VARBINARY in Drill

[ https://issues.apache.org/jira/browse/DRILL-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749539#comment-16749539 ] Kunal Khatua commented on DRILL-6994: - [~khfaraaz] what does the schema look like according to the

[jira] [Commented] (DRILL-5807) ambiguous error

[ https://issues.apache.org/jira/browse/DRILL-5807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749538#comment-16749538 ] Kunal Khatua commented on DRILL-5807: - I'm wondering if moving the aliases within the parenthesis

[jira] [Commented] (DRILL-6982) Affected rows count is not returned by Drill if return_result_set_for_ddl is false

[ https://issues.apache.org/jira/browse/DRILL-6982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749392#comment-16749392 ] Bridget Bevens commented on DRILL-6982: --- Hi [~kkhatua], Based on

[jira] [Updated] (DRILL-6994) TIMESTAMP type DOB column in Spark parquet is treated as VARBINARY in Drill

[ https://issues.apache.org/jira/browse/DRILL-6994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Khurram Faraaz updated DRILL-6994: -- Component/s: Execution - Data Types > TIMESTAMP type DOB column in Spark parquet is treated as

[jira] [Created] (DRILL-6994) TIMESTAMP type DOB column in Spark parquet is treated as VARBINARY in Drill

Khurram Faraaz created DRILL-6994: - Summary: TIMESTAMP type DOB column in Spark parquet is treated as VARBINARY in Drill Key: DRILL-6994 URL: https://issues.apache.org/jira/browse/DRILL-6994 Project:

[jira] [Updated] (DRILL-6910) A filtering column remains in scan when filter pruning happens

[ https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6910: --- Fix Version/s: 1.16.0 > A filtering column remains in scan when filter pruning

[jira] [Updated] (DRILL-6910) A filtering column remains in scan when filter pruning happens

[ https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6910: --- Description: *Data:* {code:sql} create table dfs.tmp.`nation` as select * from

[jira] [Assigned] (DRILL-6910) A filtering column remains in scan when filter pruning happens

[ https://issues.apache.org/jira/browse/DRILL-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi reassigned DRILL-6910: -- Assignee: Volodymyr Vysotskyi > A filtering column remains in scan when

[jira] [Commented] (DRILL-6991) Kerberos ticket is being dumped in the log if log level is "debug" for stdout

[ https://issues.apache.org/jira/browse/DRILL-6991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16749039#comment-16749039 ] Sorabh Hamirwasia commented on DRILL-6991: -- Why is this a problem ? TGT is encrypted with TGS

[jira] [Created] (DRILL-6993) VARBINARY length is ignored on cast

Bohdan Kazydub created DRILL-6993: - Summary: VARBINARY length is ignored on cast Key: DRILL-6993 URL: https://issues.apache.org/jira/browse/DRILL-6993 Project: Apache Drill Issue Type: Bug

[jira] [Created] (DRILL-6992) Support column histogram statistics

Aman Sinha created DRILL-6992: - Summary: Support column histogram statistics Key: DRILL-6992 URL: https://issues.apache.org/jira/browse/DRILL-6992 Project: Apache Drill Issue Type: New Feature

[jira] [Updated] (DRILL-6950) Row set-based scan framework

[ https://issues.apache.org/jira/browse/DRILL-6950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-6950: Reviewer: Arina Ielchiieva > Row set-based scan framework > >

[jira] [Updated] (DRILL-6977) Improve Hive tests configuration

[ https://issues.apache.org/jira/browse/DRILL-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-6977: Affects Version/s: 1.15.0 > Improve Hive tests configuration >

[jira] [Updated] (DRILL-6977) Improve Hive tests configuration

[ https://issues.apache.org/jira/browse/DRILL-6977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arina Ielchiieva updated DRILL-6977: Labels: ready-to-commit (was: ) > Improve Hive tests configuration >

[jira] [Updated] (DRILL-6862) Update Calcite to 1.18.0

[ https://issues.apache.org/jira/browse/DRILL-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6862: --- Fix Version/s: 1.16.0 > Update Calcite to 1.18.0 > - > >

[jira] [Created] (DRILL-6991) Kerberos ticket is being dumped in the log if log level is "debug" for stdout

Anton Gozhiy created DRILL-6991: --- Summary: Kerberos ticket is being dumped in the log if log level is "debug" for stdout Key: DRILL-6991 URL: https://issues.apache.org/jira/browse/DRILL-6991 Project:

[jira] [Updated] (DRILL-6862) Update Calcite to 1.18.0

[ https://issues.apache.org/jira/browse/DRILL-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6862: --- Affects Version/s: 1.15.0 > Update Calcite to 1.18.0 > - >

[jira] [Comment Edited] (DRILL-6980) --run regression - error when empty line or command at end of the file

[ https://issues.apache.org/jira/browse/DRILL-6980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748033#comment-16748033 ] Volodymyr Vysotskyi edited comment on DRILL-6980 at 1/22/19 10:22 AM:

[jira] [Commented] (DRILL-6987) sqlline - simple semicolon ";" with no command produce error

[ https://issues.apache.org/jira/browse/DRILL-6987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16748571#comment-16748571 ] benj commented on DRILL-6987: - OK. So, for monitoring, I created a related issue on

[jira] [Updated] (DRILL-6969) Inconsistent results when reading MaprDB JSON tables using hive plugin when native reader is enabled

[ https://issues.apache.org/jira/browse/DRILL-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6969: --- Description: Steps to reproduce: 0. Set PST timezone. 1. Create the table in MaprDB

[jira] [Updated] (DRILL-6969) Inconsistent results when reading MaprDB JSON tables using hive plugin when native reader is enabled

[ https://issues.apache.org/jira/browse/DRILL-6969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Volodymyr Vysotskyi updated DRILL-6969: --- Labels: doc-impacting ready-to-commit (was: ready-to-commit) > Inconsistent results