[jira] [Assigned] (DRILL-5334) Questionable code in the TimeVector class

[ https://issues.apache.org/jira/browse/DRILL-5334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5334: -- Assignee: (was: Vitalii Diravka) > Questionable code in the TimeVector class >

[jira] [Assigned] (DRILL-5389) select 2 int96 using convert_from(col, 'TIMESTAMP_IMPALA') function fails

[ https://issues.apache.org/jira/browse/DRILL-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5389: -- Assignee: (was: Vitalii Diravka) > select 2 int96 using convert_from(col,

[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=16031350#comment-16031350 ] Vitalii Diravka commented on DRILL-2975: [~rkins] Could you provide the output of above queries

[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=16031397#comment-16031397 ] Vitalii Diravka commented on DRILL-4116: [~rkins] It looks like the output relies on the local

[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] [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] [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] [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 >

[jira] [Updated] (DRILL-3250) Drill fails to compare multi-byte characters from hive table

[ https://issues.apache.org/jira/browse/DRILL-3250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3250: --- Issue Type: Sub-task (was: Bug) Parent: DRILL-4039 > Drill fails to compare

[jira] [Assigned] (DRILL-5035) Selecting timestamp value from Hive table causes IndexOutOfBoundsException

[ https://issues.apache.org/jira/browse/DRILL-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-5035: -- Assignee: (was: Vitalii Diravka) > Selecting timestamp value from Hive table

[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] [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] [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] [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] [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] [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] [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] [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] [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] [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] [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] [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-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] [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] [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] [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: --- 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] [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-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] [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] [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] [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] [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-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] [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] [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] [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] [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] [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] [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-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-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] [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-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-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] [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=16227349#comment-16227349 ] Vitalii Diravka commented on DRILL-5822: [~Paul.Rogers] Here is the issue of unnecessary sorting

[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] [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: --- 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] [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] [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] [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] [Created] (DRILL-6412) Hive default storage plugin template shows "null" when drillbit is started

Vitalii Diravka created DRILL-6412: -- Summary: Hive default storage plugin template shows "null" when drillbit is started Key: DRILL-6412 URL: https://issues.apache.org/jira/browse/DRILL-6412

[jira] [Comment Edited] (DRILL-6417) Project is not pushed into scan if use subquery with UNION operator

[ https://issues.apache.org/jira/browse/DRILL-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475786#comment-16475786 ] Vitalii Diravka edited comment on DRILL-6417 at 5/15/18 2:20 PM: - Looks

[jira] [Comment Edited] (DRILL-6417) Project is not pushed into scan if use subquery with UNION operator

[ https://issues.apache.org/jira/browse/DRILL-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475786#comment-16475786 ] Vitalii Diravka edited comment on DRILL-6417 at 5/15/18 2:14 PM: - Looks

[jira] [Assigned] (DRILL-6412) Hive default storage plugin template shows "null" when drillbit is started

[ https://issues.apache.org/jira/browse/DRILL-6412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-6412: -- Assignee: (was: Vitalii Diravka) > Hive default storage plugin template shows

[jira] [Created] (DRILL-6424) Updating FasterXML Jackson libraries

Vitalii Diravka created DRILL-6424: -- Summary: Updating FasterXML Jackson libraries Key: DRILL-6424 URL: https://issues.apache.org/jira/browse/DRILL-6424 Project: Apache Drill Issue Type:

[jira] [Commented] (DRILL-6417) Project is not pushed into scan if use subquery with UNION operator

[ https://issues.apache.org/jira/browse/DRILL-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16475786#comment-16475786 ] Vitalii Diravka commented on DRILL-6417: Looks like the rule doesn't support UNION DISTINCT yet:

[jira] [Updated] (DRILL-6371) Use FilterSetOpTransposeRule, DrillProjectSetOpTransposeRule in main logical stage

[ https://issues.apache.org/jira/browse/DRILL-6371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6371: --- Description: FilterSetOpTransposeRule, ProjectSetOpTransposeRule are leveraged in DRILL-3855.

[jira] [Commented] (DRILL-4682) Allow full schema identifier in SELECT clause

[ https://issues.apache.org/jira/browse/DRILL-4682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16483749#comment-16483749 ] Vitalii Diravka commented on DRILL-4682: CALCITE-1208 resolves two-level column structure

[jira] [Updated] (DRILL-6374) Transitive Closure leads to TPCH Queries regressions and OOM when run concurrency test

[ https://issues.apache.org/jira/browse/DRILL-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6374: --- Summary: Transitive Closure leads to TPCH Queries regressions and OOM when run concurrency

[jira] [Updated] (DRILL-6374) Transitive Closure leads to TPCH Queries regressions and OOM when run concurrency test

[ https://issues.apache.org/jira/browse/DRILL-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6374: --- Labels: ready-to-commit (was: ) > Transitive Closure leads to TPCH Queries regressions and

[jira] [Commented] (DRILL-6435) MappingSet is stateful, so it can't be shared between threads

[ https://issues.apache.org/jira/browse/DRILL-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16484332#comment-16484332 ] Vitalii Diravka commented on DRILL-6435: I think this is the same issue as DRILL-6416. So I have

[jira] [Updated] (DRILL-6454) Native MapR DB plugin support for Hive MapR-DB json table

[ https://issues.apache.org/jira/browse/DRILL-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6454: --- Description: Hive can create and query MapR-DB tables via maprdb-json-handler:

[jira] [Commented] (DRILL-4931) Attempting to execute a SELECT against an HBase store results in an IllegalAccessError accessing method "com.google.common.base.Stopwatch.()"

[ https://issues.apache.org/jira/browse/DRILL-4931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16505362#comment-16505362 ] Vitalii Diravka commented on DRILL-4931: It should be resolved after shading guava in Drill -

[jira] [Commented] (DRILL-6145) Enable usage of Hive MapR-DB JSON handler

[ https://issues.apache.org/jira/browse/DRILL-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16516077#comment-16516077 ] Vitalii Diravka commented on DRILL-6145: Hi [~bbevens], * "Release note summary" looks good.

[jira] [Commented] (DRILL-6494) Drill Plugins Handler

[ https://issues.apache.org/jira/browse/DRILL-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16511604#comment-16511604 ] Vitalii Diravka commented on DRILL-6494: [~parthc], [~shamirwasia] Could you please do comments

[jira] [Updated] (DRILL-6494) Drill Plugins Handler

[ https://issues.apache.org/jira/browse/DRILL-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6494: --- Fix Version/s: (was: Future) > Drill Plugins Handler > - > >

[jira] [Created] (DRILL-6494) Drill Plugins Handler

Vitalii Diravka created DRILL-6494: -- Summary: Drill Plugins Handler Key: DRILL-6494 URL: https://issues.apache.org/jira/browse/DRILL-6494 Project: Apache Drill Issue Type: New Feature

[jira] [Updated] (DRILL-6494) Drill Plugins Handler

[ https://issues.apache.org/jira/browse/DRILL-6494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6494: --- Description: The new service of updating Drill's plugins configs could be implemented.

[jira] [Updated] (DRILL-3964) CTAS fails with NPE when source JSON file is empty

[ https://issues.apache.org/jira/browse/DRILL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3964: --- Component/s: (was: Storage - Parquet) Storage - Writer > CTAS fails

[jira] [Updated] (DRILL-3539) CTAS over empty json file throws NPE

[ https://issues.apache.org/jira/browse/DRILL-3539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3539: --- Fix Version/s: (was: Future) 1.14.0 > CTAS over empty json file

[jira] [Updated] (DRILL-3964) CTAS fails with NPE when source JSON file is empty

[ https://issues.apache.org/jira/browse/DRILL-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-3964: --- Fix Version/s: 1.14.0 > CTAS fails with NPE when source JSON file is empty >

[jira] [Created] (DRILL-6454) Native MapR DB plugin support for Hive MapR-DB json table

Vitalii Diravka created DRILL-6454: -- Summary: Native MapR DB plugin support for Hive MapR-DB json table Key: DRILL-6454 URL: https://issues.apache.org/jira/browse/DRILL-6454 Project: Apache Drill

[jira] [Updated] (DRILL-6454) Native MapR DB plugin support for Hive MapR-DB json table

[ https://issues.apache.org/jira/browse/DRILL-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6454: --- Description: Hive can create and query MapR-DB tables via maprdb-json-handler:

[jira] [Updated] (DRILL-6145) Implement using of Hive MapR-DB JSON handler.

[ https://issues.apache.org/jira/browse/DRILL-6145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6145: --- Summary: Implement using of Hive MapR-DB JSON handler. (was: Implement Hive MapR-DB JSON

[jira] [Updated] (DRILL-6293) Unable to read hive(2.1.1) tables using Drill 1.13.0

[ https://issues.apache.org/jira/browse/DRILL-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6293: --- Attachment: hive-metastore-2.1.1.jar > Unable to read hive(2.1.1) tables using Drill 1.13.0

[jira] [Commented] (DRILL-6293) Unable to read hive(2.1.1) tables using Drill 1.13.0

[ https://issues.apache.org/jira/browse/DRILL-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16498552#comment-16498552 ] Vitalii Diravka commented on DRILL-6293: [~anuptiwari] It seems that to use Drill with Hive 2.1

[jira] [Created] (DRILL-6460) Different hive-metastore jar files in accordance with the version of Hive

Vitalii Diravka created DRILL-6460: -- Summary: Different hive-metastore jar files in accordance with the version of Hive Key: DRILL-6460 URL: https://issues.apache.org/jira/browse/DRILL-6460 Project:

[jira] [Assigned] (DRILL-6293) Unable to read hive(2.1.1) tables using Drill 1.13.0

[ https://issues.apache.org/jira/browse/DRILL-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-6293: -- Assignee: (was: Vitalii Diravka) > Unable to read hive(2.1.1) tables using Drill

[jira] [Assigned] (DRILL-6460) Different hive-metastore jar files in accordance with the version of Hive

[ https://issues.apache.org/jira/browse/DRILL-6460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-6460: -- Assignee: (was: Vitalii Diravka) > Different hive-metastore jar files in

[jira] [Assigned] (DRILL-6465) Transitive closure is not working in Drill for Join with multiple local conditions

[ https://issues.apache.org/jira/browse/DRILL-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka reassigned DRILL-6465: -- Assignee: Vitalii Diravka > Transitive closure is not working in Drill for Join with

[jira] [Commented] (DRILL-6465) Transitive closure is not working in Drill for Join with multiple local conditions

[ https://issues.apache.org/jira/browse/DRILL-6465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16502046#comment-16502046 ] Vitalii Diravka commented on DRILL-6465: The issue for [NOT IN

[jira] [Created] (DRILL-6559) Travis timing out

Vitalii Diravka created DRILL-6559: -- Summary: Travis timing out Key: DRILL-6559 URL: https://issues.apache.org/jira/browse/DRILL-6559 Project: Apache Drill Issue Type: Improvement

[jira] [Updated] (DRILL-6559) Travis timing out

[ https://issues.apache.org/jira/browse/DRILL-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6559: --- Description: There was a decision to exclude some more TPCH unit tests from Travis CI build

[jira] [Commented] (DRILL-6559) Travis timing out

[ https://issues.apache.org/jira/browse/DRILL-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16527925#comment-16527925 ] Vitalii Diravka commented on DRILL-6559: One more candidate is MongoTestSuit. > Travis timing

[jira] [Updated] (DRILL-6564) Storage plugins versioning and separate storage plugins handler service

[ https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6564: --- Summary: Storage plugins versioning and separate storage plugins handler service (was:

[jira] [Updated] (DRILL-6564) Storage plugins versioning and separate storage plugins handler service

[ https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6564: --- Description: Storage plugin handler can be improved with: * Versioning can be implemented

[jira] [Created] (DRILL-6564) Storage Plugins Versioning

Vitalii Diravka created DRILL-6564: -- Summary: Storage Plugins Versioning Key: DRILL-6564 URL: https://issues.apache.org/jira/browse/DRILL-6564 Project: Apache Drill Issue Type: Improvement

[jira] [Updated] (DRILL-6564) Storage Plugins Versioning

[ https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6564: --- Description: Versioning can be implemented by introducing timestamp:long in the

[jira] [Updated] (DRILL-6564) Storage Plugins Versioning

[ https://issues.apache.org/jira/browse/DRILL-6564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vitalii Diravka updated DRILL-6564: --- Description: Versioning can be implemented by introducing timestamp:long in the

[jira] [Commented] (DRILL-6562) Provide option to Export All storage plugin configurations at once

[ https://issues.apache.org/jira/browse/DRILL-6562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528396#comment-16528396 ] Vitalii Diravka commented on DRILL-6562: [~agirish] It can be useful for Drill Plugins Handler

<    1   2   3   4   5   6   7   8   9   10   >