[jira] [Updated] (DRILL-3501) No vector has initialized when the value of qualifier is null while using Hbase storage
[ https://issues.apache.org/jira/browse/DRILL-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] 徐波 updated DRILL-3501: -- Attachment: 0001-init-vector-in-setup.patch init vector in setup method > No vector has initialized when the value of qualifier is null while using > Hbase storage > --- > > Key: DRILL-3501 > URL: https://issues.apache.org/jira/browse/DRILL-3501 > Project: Apache Drill > Issue Type: Bug >Affects Versions: 0.9.0, 1.0.0, 1.1.0 >Reporter: 徐波 > Attachments: 0001-init-vector-in-setup.patch > > > drill throws exception while querying from hbase： > Failure while reading vector. Expected vector class of > org.apache.drill.exec.vector.NullableVarBinaryVector but was holding vector > class org.apache.drill.exec.vector.NullableIntVector. > My sql: > select t2.A.A1, t2.A.B2 from hdfs.root.`table1` as t1 inner join > hbase.`table2` as t2 on table1.c1=t2.c1 > Now the table2 has 3 regions and A.B2 on the last region is null while > containing values on the other regions. The node creates a NullableIntVector > while quering from the last region,but the nodes create a > NullableVarBinaryVector while quering from the other regions.So drill throws > Exception on the join node which get two type of vector for one column. > I recommend that we should initialize vector for selected columns in the > method named 'org.apache.drill.exec.store.hbase.HBaseRecordReader.setup' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3503) Make PruneScanRule have a pluggable partitioning mechanism
Mehant Baid created DRILL-3503: -- Summary: Make PruneScanRule have a pluggable partitioning mechanism Key: DRILL-3503 URL: https://issues.apache.org/jira/browse/DRILL-3503 Project: Apache Drill Issue Type: Bug Reporter: Mehant Baid Assignee: Mehant Baid Fix For: 1.2.0 Currently PruneScanRule performs partition pruning for file system. Some of the code relies on certain aspects of how partitioning is done in DFS. This JIRA aims to abstract out the behavior of the underlying partition scheme and delegate to the specific storage plugin to get that information. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DRILL-3500) Provide additional information while registering storage plugin optimizer rules
[ https://issues.apache.org/jira/browse/DRILL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mehant Baid updated DRILL-3500: --- Assignee: Jason Altekruse (was: Mehant Baid) > Provide additional information while registering storage plugin optimizer > rules > --- > > Key: DRILL-3500 > URL: https://issues.apache.org/jira/browse/DRILL-3500 > Project: Apache Drill > Issue Type: Bug >Reporter: Mehant Baid >Assignee: Jason Altekruse > Fix For: 1.2.0 > > > Currently all the optimizer rules internal to Drill have access to > QueryContext. This is used by a few rules like PruneScanRule which invoke the > interpreter to perform partition pruning. However the rules that belong to > specific storage plugins don't have access to this information. This JIRA > aims to do the following > 1. Add a new interface OptimizerRulesContext that will be implemented by > QueryContext. It will contain all the information needed by the rules. This > context will be passed to the storage plugin method while getting the > optimizer rules specific to that storage plugin. > 2. Restrict existing internal rules to only accept OptimizerRulesContext > instead of QueryContext so information in QueryContext has better > encapsulation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3500) Provide additional information while registering storage plugin optimizer rules
[ https://issues.apache.org/jira/browse/DRILL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629246#comment-14629246 ] Mehant Baid commented on DRILL-3500: [~jaltekruse] can you please review > Provide additional information while registering storage plugin optimizer > rules > --- > > Key: DRILL-3500 > URL: https://issues.apache.org/jira/browse/DRILL-3500 > Project: Apache Drill > Issue Type: Bug >Reporter: Mehant Baid >Assignee: Jason Altekruse > Fix For: 1.2.0 > > > Currently all the optimizer rules internal to Drill have access to > QueryContext. This is used by a few rules like PruneScanRule which invoke the > interpreter to perform partition pruning. However the rules that belong to > specific storage plugins don't have access to this information. This JIRA > aims to do the following > 1. Add a new interface OptimizerRulesContext that will be implemented by > QueryContext. It will contain all the information needed by the rules. This > context will be passed to the storage plugin method while getting the > optimizer rules specific to that storage plugin. > 2. Restrict existing internal rules to only accept OptimizerRulesContext > instead of QueryContext so information in QueryContext has better > encapsulation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3502) JDBC driver can cause conflicts
Stefán Baxter created DRILL-3502: Summary: JDBC driver can cause conflicts Key: DRILL-3502 URL: https://issues.apache.org/jira/browse/DRILL-3502 Project: Apache Drill Issue Type: Bug Components: Client - JDBC Affects Versions: 1.1.0 Reporter: Stefán Baxter Assignee: Daniel Barclay (Drill) Using the JDBC driver in Java projects is problematic as it contains older versions of some popular libraries and since they are not isolated/shaded they may conflict with newer versions being used in these projects. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3501) No vector has initialized when the value of qualifier is null while using Hbase storage
徐波 created DRILL-3501: - Summary: No vector has initialized when the value of qualifier is null while using Hbase storage Key: DRILL-3501 URL: https://issues.apache.org/jira/browse/DRILL-3501 Project: Apache Drill Issue Type: Bug Affects Versions: 1.1.0, 1.0.0, 0.9.0 Reporter: 徐波 drill throws exception while querying from hbase： Failure while reading vector. Expected vector class of org.apache.drill.exec.vector.NullableVarBinaryVector but was holding vector class org.apache.drill.exec.vector.NullableIntVector. My sql: select t2.A.A1, t2.A.B2 from hdfs.root.`table1` as t1 inner join hbase.`table2` as t2 on table1.c1=t2.c1 Now the table2 has 3 regions and A.B2 on the last region is null while containing values on the other regions. The node creates a NullableIntVector while quering from the last region,but the nodes create a NullableVarBinaryVector while quering from the other regions.So drill throws Exception on the join node which get two type of vector for one column. I recommend that we should initialize vector for selected columns in the method named 'org.apache.drill.exec.store.hbase.HBaseRecordReader.setup' -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DRILL-3364) Prune scan range if the filter is on the leading field with byte comparable encoding
[ https://issues.apache.org/jira/browse/DRILL-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Smidth Panchamia updated DRILL-3364: Attachment: composite.jun26.diff Patch attached. > Prune scan range if the filter is on the leading field with byte comparable > encoding > > > Key: DRILL-3364 > URL: https://issues.apache.org/jira/browse/DRILL-3364 > Project: Apache Drill > Issue Type: Sub-task > Components: Storage - HBase >Reporter: Aditya Kishore >Assignee: Smidth Panchamia > Fix For: 1.2.0 > > Attachments: composite.jun26.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3364) Prune scan range if the filter is on the leading field with byte comparable encoding
[ https://issues.apache.org/jira/browse/DRILL-3364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628889#comment-14628889 ] Smidth Panchamia commented on DRILL-3364: - ReviewBoard link: https://reviews.apache.org/r/35893/ > Prune scan range if the filter is on the leading field with byte comparable > encoding > > > Key: DRILL-3364 > URL: https://issues.apache.org/jira/browse/DRILL-3364 > Project: Apache Drill > Issue Type: Sub-task > Components: Storage - HBase >Reporter: Aditya Kishore >Assignee: Smidth Panchamia > Fix For: 1.2.0 > > Attachments: composite.jun26.diff > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3499) Using (Column[]) results in parsing error
[
https://issues.apache.org/jira/browse/DRILL-3499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628854#comment-14628854
]
Sean Hsuan-Yi Chu commented on DRILL-3499:
--
This cannot be reproduced on calcite master. After rebasing is done, this issue
should be resolved as well.
> Using (Column[]) results in parsing error
> -
>
> Key: DRILL-3499
> URL: https://issues.apache.org/jira/browse/DRILL-3499
> Project: Apache Drill
> Issue Type: Bug
> Components: SQL Parser
>Reporter: Sean Hsuan-Yi Chu
>Assignee: Sean Hsuan-Yi Chu
> Fix For: 1.4.0
>
>
> For example,
> {code}
> select *
> from dfs.`... .csv` inner join dfs.`... .csv`
> using (columns[0])
> {code}
> gives
> Error: PARSE ERROR: Encountered "[" at line 1, column 89.
> Was expecting one of:
> ")" ...
> "," ...
> Instead, it is supposed to just perform as "[]", being used elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (DRILL-3500) Provide additional information while registering storage plugin optimizer rules
[ https://issues.apache.org/jira/browse/DRILL-3500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628780#comment-14628780 ] ASF GitHub Bot commented on DRILL-3500: --- GitHub user mehant opened a pull request: https://github.com/apache/drill/pull/94 DRILL-3500: Add OptimizerRulesContext which exposes information neede… …d by storage plugin specific optimizer rules 1. Add a new interface OptimizerRulesContext that will be implemented by QueryContext. It will contain all the information needed by the rules. This context will be passed to the storage plugin method while getting the optimizer rules specific to that storage plugin. 2. Restrict existing internal rules to only accept OptimizerRulesContext instead of QueryContext so information in QueryContext has better encapsulation. You can merge this pull request into a Git repository by running: $ git pull https://github.com/mehant/drill hive_pp_1 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/drill/pull/94.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #94 commit 5969dc7f45fe750e0c87f4a157e1bf798866f210 Author: Mehant Baid Date: 2015-07-15T21:30:16Z DRILL-3500: Add OptimizerRulesContext which exposes information needed by storage plugin specific optimizer rules > Provide additional information while registering storage plugin optimizer > rules > --- > > Key: DRILL-3500 > URL: https://issues.apache.org/jira/browse/DRILL-3500 > Project: Apache Drill > Issue Type: Bug >Reporter: Mehant Baid >Assignee: Mehant Baid > Fix For: 1.2.0 > > > Currently all the optimizer rules internal to Drill have access to > QueryContext. This is used by a few rules like PruneScanRule which invoke the > interpreter to perform partition pruning. However the rules that belong to > specific storage plugins don't have access to this information. This JIRA > aims to do the following > 1. Add a new interface OptimizerRulesContext that will be implemented by > QueryContext. It will contain all the information needed by the rules. This > context will be passed to the storage plugin method while getting the > optimizer rules specific to that storage plugin. > 2. Restrict existing internal rules to only accept OptimizerRulesContext > instead of QueryContext so information in QueryContext has better > encapsulation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3500) Provide additional information while registering storage plugin optimizer rules
Mehant Baid created DRILL-3500: -- Summary: Provide additional information while registering storage plugin optimizer rules Key: DRILL-3500 URL: https://issues.apache.org/jira/browse/DRILL-3500 Project: Apache Drill Issue Type: Bug Reporter: Mehant Baid Assignee: Mehant Baid Fix For: 1.2.0 Currently all the optimizer rules internal to Drill have access to QueryContext. This is used by a few rules like PruneScanRule which invoke the interpreter to perform partition pruning. However the rules that belong to specific storage plugins don't have access to this information. This JIRA aims to do the following 1. Add a new interface OptimizerRulesContext that will be implemented by QueryContext. It will contain all the information needed by the rules. This context will be passed to the storage plugin method while getting the optimizer rules specific to that storage plugin. 2. Restrict existing internal rules to only accept OptimizerRulesContext instead of QueryContext so information in QueryContext has better encapsulation. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-3499) Using (Column[]) results in parsing error
Sean Hsuan-Yi Chu created DRILL-3499:
Summary: Using (Column[]) results in parsing error
Key: DRILL-3499
URL: https://issues.apache.org/jira/browse/DRILL-3499
Project: Apache Drill
Issue Type: Bug
Components: SQL Parser
Reporter: Sean Hsuan-Yi Chu
Assignee: Sean Hsuan-Yi Chu
Fix For: 1.4.0
For example,
{code}
select *
from dfs.`... .csv` inner join dfs.`... .csv`
using (columns[0])
{code}
gives
Error: PARSE ERROR: Encountered "[" at line 1, column 89.
Was expecting one of:
")" ...
"," ...
Instead, it is supposed to just perform as "[]", being used elsewhere.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (DRILL-3076) USING clause should not be supported in drill
[ https://issues.apache.org/jira/browse/DRILL-3076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Hsuan-Yi Chu resolved DRILL-3076. -- Resolution: Won't Fix > USING clause should not be supported in drill > -- > > Key: DRILL-3076 > URL: https://issues.apache.org/jira/browse/DRILL-3076 > Project: Apache Drill > Issue Type: Bug > Components: Query Planning & Optimization >Affects Versions: 1.0.0 >Reporter: Victoria Markman >Assignee: Sean Hsuan-Yi Chu > Fix For: 1.2.0 > > > For the same reason natural join is not supported. > See https://issues.apache.org/jira/browse/DRILL-1986 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3424) Hive Views are not accessible through Drill Query
[ https://issues.apache.org/jira/browse/DRILL-3424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14628421#comment-14628421 ] Bruce Penn commented on DRILL-3424: --- I'm not clear on if this is truly resolved, so can Drill now use Hive Queries in 1.1? > Hive Views are not accessible through Drill Query > - > > Key: DRILL-3424 > URL: https://issues.apache.org/jira/browse/DRILL-3424 > Project: Apache Drill > Issue Type: Bug > Components: Storage - Hive >Affects Versions: 1.0.0 > Environment: CentOS 6.5, MapR, Drill 1.0 >Reporter: Soumendra Kumar Mishra >Assignee: Venki Korukanti > Fix For: 1.1.0 > > > Hive Views are not accessible through Drill Query. > Error Message: Hive Views are Not Supported in Current Version -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (DRILL-3455) If a drillbit, that contains fragments for the current query, dies the QueryManager will fail the query even if those fragments already finished successfully
[ https://issues.apache.org/jira/browse/DRILL-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sudheesh Katkam reassigned DRILL-3455: -- Assignee: Sudheesh Katkam (was: Jacques Nadeau) > If a drillbit, that contains fragments for the current query, dies the > QueryManager will fail the query even if those fragments already finished > successfully > - > > Key: DRILL-3455 > URL: https://issues.apache.org/jira/browse/DRILL-3455 > Project: Apache Drill > Issue Type: Bug > Components: Execution - Flow >Reporter: Deneche A. Hakim >Assignee: Sudheesh Katkam > Fix For: 1.2.0 > > Attachments: DRILL-3455.1.patch.txt, DRILL-3455.2.patch.txt > > > Once DRILL-3448 is fixed we need to update > QueryManager.DrillbitStatusListener to no fragment is still running on the > dead node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DRILL-2879) Drill extended json's support $oid
[ https://issues.apache.org/jira/browse/DRILL-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bhallamudi Venkata Siva Kamesh updated DRILL-2879: -- Attachment: 0001-DRILL-2879-Enhancing-extended-json-support-for-date-.patch Rebased patch and updating it with test cases. Consider this patch. Update the same patch in review board > Drill extended json's support $oid > -- > > Key: DRILL-2879 > URL: https://issues.apache.org/jira/browse/DRILL-2879 > Project: Apache Drill > Issue Type: Improvement > Components: Storage - JSON >Reporter: Bhallamudi Venkata Siva Kamesh >Assignee: Jacques Nadeau > Fix For: 1.2.0 > > Attachments: > 0001-DRILL-2879-Enhancing-extended-json-support-for-date-.patch, > DRILL-2879_1.patch, extended.json, extendedjson.patch > > > Enhancing JSON reader to parse $oid (from mongo). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (DRILL-3491) SELECT COUNT(*) FROM HBASE Returns Incorrect Row Count
[ https://issues.apache.org/jira/browse/DRILL-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627808#comment-14627808 ] Carrot Hu edited comment on DRILL-3491 at 7/15/15 9:48 AM: --- I have changed from cdh5.4.2 to hbase-1.0.1.1 and hadoop-2.7.1 with same configurations. The issue does not occur anymore. I suspect this is due to incompatibility with cdh version of hadoop and hbase. was (Author: carrotyiyi): I have changed from cdh5.4.2 to hbase-1.0.1.1 and hadoop-2.7.1 with same configurations. The issue does not occur anymore. My suspect this is due to some incompatibility with cdh version of hadoop and hbase. > SELECT COUNT(*) FROM HBASE Returns Incorrect Row Count > -- > > Key: DRILL-3491 > URL: https://issues.apache.org/jira/browse/DRILL-3491 > Project: Apache Drill > Issue Type: Bug > Components: Storage - HBase >Affects Versions: 1.0.0, 1.1.0 > Environment: CentOS6.5 > jdk1.8.0_45 > hadoop-2.6.0-cdh5.4.2 > hbase-1.0.0-cdh5.4.2 > IntelliJ14.1.4 > Maven3.0.5 >Reporter: Carrot Hu >Assignee: Aditya Kishore > Labels: hbase, sql > > Create a table 'test' in Hbase with 1 column family, 7 columns. > Inserting 100,000 rows into 'test' using Java API, each column with same > value = "value". > SELECT COUNT() FROM hbase.test > returns an incorrect row count. > Verified using count 'test' in hbase shell, the row count is correct. > SELECT COUNT(row_key) is correct, > SELECT COUNT() is also correct. > Clear the table, and changed to inserting 1000 rows, keep the number of > columns, Drill returns the right count. But when increasing the number of > columns to 30. SELLECT COUNT() returns an incorrect row count (only 673). > Use count 'test' and scan 'test' in hbase to check the result, nothing usual > were noticed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-3491) SELECT COUNT(*) FROM HBASE Returns Incorrect Row Count
[ https://issues.apache.org/jira/browse/DRILL-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14627808#comment-14627808 ] Carrot Hu commented on DRILL-3491: -- I have changed from cdh5.4.2 to hbase-1.0.1.1 and hadoop-2.7.1 with same configurations. The issue does not occur anymore. My suspect this is due to some incompatibility with cdh version of hadoop and hbase. > SELECT COUNT(*) FROM HBASE Returns Incorrect Row Count > -- > > Key: DRILL-3491 > URL: https://issues.apache.org/jira/browse/DRILL-3491 > Project: Apache Drill > Issue Type: Bug > Components: Storage - HBase >Affects Versions: 1.0.0, 1.1.0 > Environment: CentOS6.5 > jdk1.8.0_45 > hadoop-2.6.0-cdh5.4.2 > hbase-1.0.0-cdh5.4.2 > IntelliJ14.1.4 > Maven3.0.5 >Reporter: Carrot Hu >Assignee: Aditya Kishore > Labels: hbase, sql > > Create a table 'test' in Hbase with 1 column family, 7 columns. > Inserting 100,000 rows into 'test' using Java API, each column with same > value = "value". > SELECT COUNT() FROM hbase.test > returns an incorrect row count. > Verified using count 'test' in hbase shell, the row count is correct. > SELECT COUNT(row_key) is correct, > SELECT COUNT() is also correct. > Clear the table, and changed to inserting 1000 rows, keep the number of > columns, Drill returns the right count. But when increasing the number of > columns to 30. SELLECT COUNT() returns an incorrect row count (only 673). > Use count 'test' and scan 'test' in hbase to check the result, nothing usual > were noticed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
