[jira] [Comment Edited] (DRILL-4309) Make this option store.hive.optimize_scan_with_native_readers=true default

[ https://issues.apache.org/jira/browse/DRILL-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311453#comment-16311453 ] Vitalii Diravka edited comment on DRILL-4309 at 1/4/18 3:16 PM: There are

[jira] [Commented] (DRILL-4309) Make this option store.hive.optimize_scan_with_native_readers=true default

[ https://issues.apache.org/jira/browse/DRILL-4309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311453#comment-16311453 ] Vitalii Diravka commented on DRILL-4309: There are at least 3 blockers for resolving current

[jira] [Commented] (DRILL-5970) DrillParquetReader always builds the schema with "OPTIONAL" dataMode columns instead of "REQUIRED" ones

[ https://issues.apache.org/jira/browse/DRILL-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16311417#comment-16311417 ] Vitalii Diravka commented on DRILL-5970: [~paul-rogers] I just was not concentrated on MYCOL

[jira] [Assigned] (DRILL-4185) UNION ALL involving empty directory on any side of union all results in Failed query

[ https://issues.apache.org/jira/browse/DRILL-4185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-4185: -- Assignee: Vitalii Diravka > UNION ALL involving empty directory on any side of union

[jira] [Commented] (DRILL-5970) DrillParquetReader always builds the schema with "OPTIONAL" dataMode columns instead of "REQUIRED" ones

[ https://issues.apache.org/jira/browse/DRILL-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16303863#comment-16303863 ] Vitalii Diravka commented on DRILL-5970: [~Paul.Rogers] The schema of second file is the

[jira] [Comment Edited] (DRILL-5702) Jdbc Driver Class not found

[ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16282729#comment-16282729 ] Vitalii Diravka edited comment on DRILL-5702 at 12/8/17 8:32 AM: -

[jira] [Updated] (DRILL-5702) Jdbc Driver Class not found

[ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5702: --- Attachment: drill-jdbc-all-1.12.0-SNAPSHOT.jar [~korlawulki] Could you please verify this

[jira] [Commented] (DRILL-6016) Error reading INT96 created by Apache Spark

[ https://issues.apache.org/jira/browse/DRILL-6016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16281561#comment-16281561 ] Vitalii Diravka commented on DRILL-6016: Interesting dataset. Drill reads INT96 by default as

[jira] [Commented] (DRILL-5702) Jdbc Driver Class not found

[ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16277410#comment-16277410 ] Vitalii Diravka commented on DRILL-5702: Thank you [~korlawulki] for finding this issue. I have

[jira] [Commented] (DRILL-5845) Columns returned by select with "ORDER BY" and "LIMIT" clauses are not in correct order.

[ https://issues.apache.org/jira/browse/DRILL-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16276611#comment-16276611 ] Vitalii Diravka commented on DRILL-5845: [~rhou] Dir0/dir1/dir2 should appear as the first few

[jira] [Commented] (DRILL-5702) Jdbc Driver Class not found

[ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275575#comment-16275575 ] Vitalii Diravka commented on DRILL-5702: Currently Drill uses 2.7.1 hadoop libraries version:

[jira] [Commented] (DRILL-5702) Jdbc Driver Class not found

[ https://issues.apache.org/jira/browse/DRILL-5702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275572#comment-16275572 ] Vitalii Diravka commented on DRILL-5702: I have not seen this issue on my env: Ran driillbit in

[jira] [Commented] (DRILL-6003) Unit test TestDynamicUDFSupport.testLazyInitWhenDynamicUdfSupportIsDisabled fails with FUNCTION ERROR: Failure reading Function class.

[ https://issues.apache.org/jira/browse/DRILL-6003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275547#comment-16275547 ] Vitalii Diravka commented on DRILL-6003: This test is passed on my machine: {code} mvn

[jira] [Assigned] (DRILL-5681) Incorrect query result when query uses star and correlated subquery

[ https://issues.apache.org/jira/browse/DRILL-5681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5681: -- Assignee: Vitalii Diravka (was: Jinfeng Ni) > Incorrect query result when query uses

[jira] [Assigned] (DRILL-5683) Incorrect query result when query uses NOT(IS NOT NULL) expression

[ https://issues.apache.org/jira/browse/DRILL-5683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5683: -- Assignee: Vitalii Diravka (was: Jinfeng Ni) > Incorrect query result when query uses

[jira] [Commented] (DRILL-5970) DrillParquetReader always builds the schema with "OPTIONAL" dataMode columns instead of "REQUIRED" ones

[ https://issues.apache.org/jira/browse/DRILL-5970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16259778#comment-16259778 ] Vitalii Diravka commented on DRILL-5970: There is an issue with a REQUIRED fields which are part

[jira] [Created] (DRILL-5978) Upgrade drill-hive library version to 2.1 or newer.

Vitalii Diravka created DRILL-5978: -- Summary: Upgrade drill-hive library version to 2.1 or newer. Key: DRILL-5978 URL: https://issues.apache.org/jira/browse/DRILL-5978 Project: Apache Drill

[jira] [Created] (DRILL-5970) DrillParquetReader always builds the schema with "OPTIONAL" dataMode columns instead of "REQUIRED" ones

Vitalii Diravka created DRILL-5970: -- Summary: DrillParquetReader always builds the schema with "OPTIONAL" dataMode columns instead of "REQUIRED" ones Key: DRILL-5970 URL:

[jira] [Commented] (DRILL-3288) False "Hash aggregate does not support schema changes" error message in a query with merge join and hash aggregation

[ https://issues.apache.org/jira/browse/DRILL-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16253661#comment-16253661 ] Vitalii Diravka commented on DRILL-3288: [~vicky] I have compared schema of the files provided by

[jira] [Commented] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16227349#comment-16227349 ] Vitalii Diravka commented on DRILL-5822: [~Paul.Rogers] Here is the issue of unnecessary sorting

[jira] [Comment Edited] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226679#comment-16226679 ] Vitalii Diravka edited comment on DRILL-5822 at 10/31/17 1:37 PM: -- This

[jira] [Commented] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16226679#comment-16226679 ] Vitalii Diravka commented on DRILL-5822: This is an old topic which was discussed in DRILL-1499

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Labels: (was: read) > The query with "SELECT *" with "ORDER BY" clause and

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Component/s: (was: Storage - JSON) > The query with "SELECT *" with "ORDER BY" clause and

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Labels: read (was: ) > The query with "SELECT *" with "ORDER BY" clause and

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Description: Columns ordering doesn't preserve for the star query with sorting when this is

[jira] [Commented] (DRILL-3101) Setting "slice_target" to 1 changes the order of the columns in a "select *" query with order by

[ https://issues.apache.org/jira/browse/DRILL-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16225607#comment-16225607 ] Vitalii Diravka commented on DRILL-3101: The issue is raised in the context of DRILL-5822 and

[jira] [Resolved] (DRILL-1499) Different column order could appear in the result set for a schema-less select * query, even there are no changing schemas.

[ https://issues.apache.org/jira/browse/DRILL-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka resolved DRILL-1499. Resolution: Resolved Assignee: Vitalii Diravka (was: Steven Phillips) Fix

[jira] [Updated] (DRILL-5906) java.lang.NullPointerException while quering Hive ORC tables on MapR cluster.

[ https://issues.apache.org/jira/browse/DRILL-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5906: --- Attachment: bucketed_table.zip > java.lang.NullPointerException while quering Hive ORC tables

[jira] [Updated] (DRILL-5906) java.lang.NullPointerException while quering Hive ORC tables on MapR cluster.

[ https://issues.apache.org/jira/browse/DRILL-5906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5906: --- Description: Record reader throw an exception when trying to read an empty split. To

[jira] [Assigned] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5822: -- Assignee: Vitalii Diravka > The query with "SELECT *" with "ORDER BY" clause and

[jira] [Commented] (DRILL-5898) Query returns columns in the wrong order

[ https://issues.apache.org/jira/browse/DRILL-5898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16219272#comment-16219272 ] Vitalii Diravka commented on DRILL-5898: [~rhou] Wrong column ordering for queries with ORDER BY

[jira] [Created] (DRILL-5906) java.lang.NullPointerException while quering Hive ORC tables on MapR cluster.

Vitalii Diravka created DRILL-5906: -- Summary: java.lang.NullPointerException while quering Hive ORC tables on MapR cluster. Key: DRILL-5906 URL: https://issues.apache.org/jira/browse/DRILL-5906

[jira] [Commented] (DRILL-5706) Select * on hbase table having multiple regions(one or more empty) returns wrong result intermittently

[ https://issues.apache.org/jira/browse/DRILL-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216919#comment-16216919 ] Vitalii Diravka commented on DRILL-5706: [~paul-rogers] Can we close it, since it was fixed in

[jira] [Assigned] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5822: -- Assignee: (was: Vitalii Diravka) > The query with "SELECT *" with "ORDER BY"

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Description: Repro steps: 1) {code}alter session set `planner.slice_target`=1;{code} 2) ORDER

[jira] [Updated] (DRILL-5822) The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1 doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5822: --- Summary: The query with "SELECT *" with "ORDER BY" clause and `planner.slice_target`=1

[jira] [Commented] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16216742#comment-16216742 ] Vitalii Diravka commented on DRILL-5822: [~prasadns14] With "order by" clause I have reproduced

[jira] [Updated] (DRILL-5845) Columns returned by select with "ORDER BY" and "LIMIT" clauses are not in correct order.

[ https://issues.apache.org/jira/browse/DRILL-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5845: --- Fix Version/s: (was: Future) 1.12.0 > Columns returned by select with

[jira] [Commented] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16209525#comment-16209525 ] Vitalii Diravka commented on DRILL-5822: [~prasadns14] Not sure how to reproduce the issue. Please

[jira] [Assigned] (DRILL-5845) Columns returned by select with "ORDER BY" and "LIMIT" clauses are not in correct order.

[ https://issues.apache.org/jira/browse/DRILL-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5845: -- Assignee: Vitalii Diravka > Columns returned by select with "ORDER BY" and "LIMIT"

[jira] [Updated] (DRILL-5845) Columns returned by select with "ORDER BY" and "LIMIT" clauses are not in correct order.

[ https://issues.apache.org/jira/browse/DRILL-5845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5845: --- Summary: Columns returned by select with "ORDER BY" and "LIMIT" clauses are not in correct

[jira] [Created] (DRILL-5845) Columns returned by select with "ORDER BY" and "LIMIT" clauses returned in correct order

Vitalii Diravka created DRILL-5845: -- Summary: Columns returned by select with "ORDER BY" and "LIMIT" clauses returned in correct order Key: DRILL-5845 URL: https://issues.apache.org/jira/browse/DRILL-5845

[jira] [Commented] (DRILL-5822) Select * on directory containing multiple json files (one or more empty) with same schema doesn't preserve column order

[ https://issues.apache.org/jira/browse/DRILL-5822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16184057#comment-16184057 ] Vitalii Diravka commented on DRILL-5822: [~prasadns14] Is it expected that in second case 3 rows

[jira] [Assigned] (DRILL-5792) CONVERT_FROM_JSON on an empty file throws runtime exception

[ https://issues.apache.org/jira/browse/DRILL-5792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5792: -- Assignee: Vitalii Diravka > CONVERT_FROM_JSON on an empty file throws runtime

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Priority: Minor (was: Major) > Five-digit year dates are displayed incorrectly via jdbc >

[jira] [Comment Edited] (DRILL-5706) Select * on hbase table having multiple regions(one or more empty) returns wrong result intermittently

[ https://issues.apache.org/jira/browse/DRILL-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172202#comment-16172202 ] Vitalii Diravka edited comment on DRILL-5706 at 9/20/17 5:40 PM: - I have a

[jira] [Assigned] (DRILL-5706) Select * on hbase table having multiple regions(one or more empty) returns wrong result intermittently

[ https://issues.apache.org/jira/browse/DRILL-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5706: -- Assignee: Vitalii Diravka > Select * on hbase table having multiple regions(one or

[jira] [Commented] (DRILL-5706) Select * on hbase table having multiple regions(one or more empty) returns wrong result intermittently

[ https://issues.apache.org/jira/browse/DRILL-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16172202#comment-16172202 ] Vitalii Diravka commented on DRILL-5706: [~prasadns14] Looks like the result is correct. Please

[jira] [Updated] (DRILL-5002) Using hive's date functions on top of date column gives wrong results for local time-zone

[ https://issues.apache.org/jira/browse/DRILL-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5002: --- Labels: ready-to-commit (was: ) > Using hive's date functions on top of date column gives

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Fix Version/s: (was: Future) 1.12.0 > Five-digit year dates are

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Labels: ready-to-commit (was: ) > Five-digit year dates are displayed incorrectly via jdbc >

[jira] [Commented] (DRILL-5141) Difference in output date format on sqlline vs Drill's Web UI

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

[jira] [Updated] (DRILL-5757) CONVERT_TO_JSON function is failed while using non-existence field as a parameter.

[ https://issues.apache.org/jira/browse/DRILL-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5757: --- Description: Using of non-existence field as parameter (or field with null values across a

[jira] [Updated] (DRILL-5757) CONVERT_TO_JSON function is failed while using non-existence field as a parameter.

[ https://issues.apache.org/jira/browse/DRILL-5757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5757: --- Description: Using of non-existence field as parameter (or field with null values across a

[jira] [Created] (DRILL-5757) CONVERT_TO_JSON function is failed while using non-existence field as a parameter.

Vitalii Diravka created DRILL-5757: -- Summary: CONVERT_TO_JSON function is failed while using non-existence field as a parameter. Key: DRILL-5757 URL: https://issues.apache.org/jira/browse/DRILL-5757

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Description: git.commit.id.abbrev=38ef562 The issue is connected to displaying five-digit

[jira] [Commented] (DRILL-5606) Some tests fail after creating a fresh clone

[ https://issues.apache.org/jira/browse/DRILL-5606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144966#comment-16144966 ] Vitalii Diravka commented on DRILL-5606: 1. The above "TestCastFunctions.testToDateForTimeStamp()"

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Fix Version/s: Future > Five-digit year dates are displayed incorrectly via jdbc >

[jira] [Updated] (DRILL-5377) Five-digit year dates are displayed incorrectly via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Summary: Five-digit year dates are displayed incorrectly via jdbc (was: Five-digit year

[jira] [Commented] (DRILL-5377) Five-digit year dates aren't correct displayed via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133082#comment-16133082 ] Vitalii Diravka commented on DRILL-5377: The root cause of the issue is that java.sql.Date cut

[jira] [Commented] (DRILL-1051) Casting timestamp as date gives wrong result for dates earlier than 1883

[ https://issues.apache.org/jira/browse/DRILL-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16133080#comment-16133080 ] Vitalii Diravka commented on DRILL-1051: The issue is connected to the JDBC and converting of Joda

[jira] [Updated] (DRILL-5377) Five-digit year dates aren't correct displayed via jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Summary: Five-digit year dates aren't correct displayed via jdbc (was: Five-digit year dates

[jira] [Comment Edited] (DRILL-5377) Five-digit year dates aren't correct displayed by jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15945457#comment-15945457 ] Vitalii Diravka edited comment on DRILL-5377 at 8/18/17 1:49 PM: - Dates

[jira] [Updated] (DRILL-5377) Five-digit year dates aren't correct displayed by jdbc

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5377: --- Summary: Five-digit year dates aren't correct displayed by jdbc (was: Drill returns weird

[jira] [Updated] (DRILL-1051) Casting timestamp as date gives wrong result for dates earlier than 1883

[ https://issues.apache.org/jira/browse/DRILL-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-1051: --- Summary: Casting timestamp as date gives wrong result for dates earlier than 1883 (was:

[jira] [Updated] (DRILL-1051) casting timestamp as date gives wrong result for dates earlier than 1883

[ https://issues.apache.org/jira/browse/DRILL-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-1051: --- Summary: casting timestamp as date gives wrong result for dates earlier than 1883 (was:

[jira] [Resolved] (DRILL-3827) Empty metadata file causes queries on the table to fail

[ https://issues.apache.org/jira/browse/DRILL-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka resolved DRILL-3827. Resolution: Fixed Fix Version/s: (was: Future) 1.12.0 Fixed

[jira] [Resolved] (DRILL-3829) Metadata Caching : Drill should ignore a corrupted cache file

[ https://issues.apache.org/jira/browse/DRILL-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka resolved DRILL-3829. Resolution: Fixed Fix Version/s: (was: Future) 1.12.0 Fixed

[jira] [Updated] (DRILL-3867) Store relative paths in metadata file

[ https://issues.apache.org/jira/browse/DRILL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3867: --- Description: git.commit.id.abbrev=cf4f745 git.commit.time=29.09.2015 @ 23\:19\:52 UTC The

[jira] [Assigned] (DRILL-3827) Empty metadata file causes queries on the table to fail

[ https://issues.apache.org/jira/browse/DRILL-3827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-3827: -- Assignee: Vitalii Diravka (was: Parth Chandra) > Empty metadata file causes queries

[jira] [Assigned] (DRILL-3829) Metadata Caching : Drill should ignore a corrupted cache file

[ https://issues.apache.org/jira/browse/DRILL-3829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-3829: -- Assignee: Vitalii Diravka > Metadata Caching : Drill should ignore a corrupted cache

[jira] [Assigned] (DRILL-1051) casting timestamp as date gives wrong result for dates earlier than 1797

[ https://issues.apache.org/jira/browse/DRILL-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-1051: -- Assignee: Vitalii Diravka > casting timestamp as date gives wrong result for dates

[jira] [Assigned] (DRILL-5377) Drill returns weird characters when parquet date auto-correction is turned off

[ https://issues.apache.org/jira/browse/DRILL-5377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5377: -- Assignee: Vitalii Diravka > Drill returns weird characters when parquet date

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: *Added a possibility of changing characters for quoting identifiers by setting

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: *Added a possibility of changing characters for quoting identifiers by setting

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: Currently Drill's SQL parser uses backtick as identifier quotes, the same as

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: Currently Drill's SQL parser uses backtick as identifier quotes, the same as

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: Currently Drill's SQL parser uses backtick as identifier quotes, the same as

[jira] [Updated] (DRILL-3510) Add ANSI_QUOTES option so that Drill's SQL Parser will recognize ANSI_SQL identifiers

[ https://issues.apache.org/jira/browse/DRILL-3510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3510: --- Description: Currently Drill's SQL parser uses backtick as identifier quotes, the same as

[jira] [Updated] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5660: --- Description: Drill recently accepted a PR for the following bug: DRILL-3867: Store relative

[jira] [Commented] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16086292#comment-16086292 ] Vitalii Diravka commented on DRILL-5660: [~paul-rogers], [~jni] The patch is submitted. And the

[jira] [Comment Edited] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082118#comment-16082118 ] Vitalii Diravka edited comment on DRILL-5660 at 7/13/17 7:01 PM: -

[jira] [Comment Edited] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082118#comment-16082118 ] Vitalii Diravka edited comment on DRILL-5660 at 7/11/17 3:49 PM: -

[jira] [Commented] (DRILL-5660) Drill 1.10 queries fail due to Parquet Metadata "corruption" from DRILL-3867

[ https://issues.apache.org/jira/browse/DRILL-5660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16082118#comment-16082118 ] Vitalii Diravka commented on DRILL-5660: [~paul-rogers] I agree with update the metadata file

[jira] [Commented] (DRILL-4060) CTAS to csv or json files gives incorrect time values

[ https://issues.apache.org/jira/browse/DRILL-4060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080402#comment-16080402 ] Vitalii Diravka commented on DRILL-4060: It looks like when DRILL-5332 and DRILL-5334 is solved,

[jira] [Resolved] (DRILL-4116) Inconsistent results with datetime functions on different machines

[ https://issues.apache.org/jira/browse/DRILL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka resolved DRILL-4116. Resolution: Duplicate [DRILL-5002|https://issues.apache.org/jira/browse/DRILL-5002] jira

[jira] [Updated] (DRILL-5402) ServerMeta should be updated during the session, if the last has been changed.

[ https://issues.apache.org/jira/browse/DRILL-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5402: --- Fix Version/s: (was: 1.11.0) Future > ServerMeta should be updated

[jira] [Assigned] (DRILL-5402) ServerMeta should be updated during the session, if the last has been changed.

[ https://issues.apache.org/jira/browse/DRILL-5402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5402: -- Assignee: (was: Vitalii Diravka) > ServerMeta should be updated during the

[jira] [Assigned] (DRILL-5332) DateVector support uses questionable conversions to a time

[ https://issues.apache.org/jira/browse/DRILL-5332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5332: -- Assignee: (was: Vitalii Diravka) > DateVector support uses questionable

[jira] [Created] (DRILL-5603) Replacing the type of paths from String to Hadoop Path

Vitalii Diravka created DRILL-5603: -- Summary: Replacing the type of paths from String to Hadoop Path Key: DRILL-5603 URL: https://issues.apache.org/jira/browse/DRILL-5603 Project: Apache Drill

[jira] [Closed] (DRILL-2975) Extended Json : Time type reporting data which is dependent on the system on which it ran

[ https://issues.apache.org/jira/browse/DRILL-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka closed DRILL-2975. -- Resolution: Not A Bug Fix Version/s: (was: Future) According to the conversation in

[jira] [Commented] (DRILL-4721) Doc "dateDiff" in Drill

[ https://issues.apache.org/jira/browse/DRILL-4721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055286#comment-16055286 ] Vitalii Diravka commented on DRILL-4721: [~bbevens] datediff() is [hive built-in

[jira] [Commented] (DRILL-5002) Using hive's date functions on top of date column gives wrong results for local time-zone

[ https://issues.apache.org/jira/browse/DRILL-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055280#comment-16055280 ] Vitalii Diravka commented on DRILL-5002: One more hive built-in function, which relies on local

[jira] [Commented] (DRILL-4116) Inconsistent results with datetime functions on different machines

[ https://issues.apache.org/jira/browse/DRILL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055264#comment-16055264 ] Vitalii Diravka commented on DRILL-4116: datediff() is a [hive build-in

[jira] [Commented] (DRILL-2975) Extended Json : Time type reporting data which is dependent on the system on which it ran

[ https://issues.apache.org/jira/browse/DRILL-2975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16055238#comment-16055238 ] Vitalii Diravka commented on DRILL-2975: [~rkins] If these two queries are used on machines with

[jira] [Commented] (DRILL-3867) Store relative paths in metadata file

[ https://issues.apache.org/jira/browse/DRILL-3867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16052464#comment-16052464 ] Vitalii Diravka commented on DRILL-3867: The fix is storing relative paths in the process of

[jira] [Commented] (DRILL-4116) Inconsistent results with datetime functions on different machines

[ https://issues.apache.org/jira/browse/DRILL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050840#comment-16050840 ] Vitalii Diravka commented on DRILL-4116: [~rkins] [Configure the default time zone format in

[jira] [Comment Edited] (DRILL-4116) Inconsistent results with datetime functions on different machines

[ https://issues.apache.org/jira/browse/DRILL-4116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16031397#comment-16031397 ] Vitalii Diravka edited comment on DRILL-4116 at 6/13/17 10:50 AM: --

[jira] [Updated] (DRILL-5544) Out of heap running CTAS against text delimited

[ https://issues.apache.org/jira/browse/DRILL-5544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-5544: --- Labels: ready-to-commit (was: ) > Out of heap running CTAS against text delimited >

<    5   6   7   8   9   10   11   12   >