[jira] [Updated] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6610: - Status: Open (was: Patch Available) Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13930636#comment-13930636 ] Laljo John Pullokkaran commented on HIVE-6610: -- Renamed patch to follow naming convention Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6610: - Attachment: HIVE-6610.patch Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6610: - Status: Patch Available (was: Open) Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6550) SemanticAnalyzer.reset() doesn't clear all the state
[ https://issues.apache.org/jira/browse/HIVE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6550: - Attachment: HIVE-6550.patch SemanticAnalyzer.reset() doesn't clear all the state Key: HIVE-6550 URL: https://issues.apache.org/jira/browse/HIVE-6550 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6550.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6550) SemanticAnalyzer.reset() doesn't clear all the state
[ https://issues.apache.org/jira/browse/HIVE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6550: - Status: Patch Available (was: Open) SemanticAnalyzer.reset() doesn't clear all the state Key: HIVE-6550 URL: https://issues.apache.org/jira/browse/HIVE-6550 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6550.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6550) SemanticAnalyzer.reset() doesn't clear all the state
[ https://issues.apache.org/jira/browse/HIVE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6550: - Attachment: (was: HIVE-6550.Patch) SemanticAnalyzer.reset() doesn't clear all the state Key: HIVE-6550 URL: https://issues.apache.org/jira/browse/HIVE-6550 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6550.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6619) Stats inaccurate for auto_join32.q
Laljo John Pullokkaran created HIVE-6619: Summary: Stats inaccurate for auto_join32.q Key: HIVE-6619 URL: https://issues.apache.org/jira/browse/HIVE-6619 Project: Hive Issue Type: Bug Components: Statistics Reporter: Laljo John Pullokkaran Assignee: Prasanth J auto_join32.q unit test fails for hadoop2. Seems like stats have changed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
Laljo John Pullokkaran created HIVE-6658: Summary: Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6659) Update log for list_bucket_* to add pre/post DB
Laljo John Pullokkaran created HIVE-6659: Summary: Update log for list_bucket_* to add pre/post DB Key: HIVE-6659 URL: https://issues.apache.org/jira/browse/HIVE-6659 Project: Hive Issue Type: Bug Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran On Hadoop2 we now print out Database Name using pre/post hooks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6550) SemanticAnalyzer.reset() doesn't clear all the state
[ https://issues.apache.org/jira/browse/HIVE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6550: - Status: Patch Available (was: Open) SemanticAnalyzer.reset() doesn't clear all the state Key: HIVE-6550 URL: https://issues.apache.org/jira/browse/HIVE-6550 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6550.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6550) SemanticAnalyzer.reset() doesn't clear all the state
[ https://issues.apache.org/jira/browse/HIVE-6550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6550: - Status: Open (was: Patch Available) SemanticAnalyzer.reset() doesn't clear all the state Key: HIVE-6550 URL: https://issues.apache.org/jira/browse/HIVE-6550 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6550.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6610: - Status: Open (was: Patch Available) Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6610) Unit test log needs to reflect DB Name
[ https://issues.apache.org/jira/browse/HIVE-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6610: - Status: Patch Available (was: Open) Unit test log needs to reflect DB Name -- Key: HIVE-6610 URL: https://issues.apache.org/jira/browse/HIVE-6610 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6610.patch Following Hadoop2 Unit tests are failing because ddl pre/post hooks are printing out database name. auto_join14.q, join14.q, input12.q, input39.q Current analysis suggest authentication changes caused it. These tests are marked as hadoop-2 only. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6658: - Attachment: HIVE-6658.patch Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6659) Update log for list_bucket_* to add pre/post DB
[ https://issues.apache.org/jira/browse/HIVE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6659: - Status: Patch Available (was: Open) Update log for list_bucket_* to add pre/post DB --- Key: HIVE-6659 URL: https://issues.apache.org/jira/browse/HIVE-6659 Project: Hive Issue Type: Bug Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6659.patch On Hadoop2 we now print out Database Name using pre/post hooks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6659) Update log for list_bucket_* to add pre/post DB
[ https://issues.apache.org/jira/browse/HIVE-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6659: - Attachment: HIVE-6659.patch Update log for list_bucket_* to add pre/post DB --- Key: HIVE-6659 URL: https://issues.apache.org/jira/browse/HIVE-6659 Project: Hive Issue Type: Bug Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6659.patch On Hadoop2 we now print out Database Name using pre/post hooks. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6658: - Status: Patch Available (was: Open) Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13935843#comment-13935843 ] Laljo John Pullokkaran commented on HIVE-6658: -- Szehon, Shouldn't it depend on de-supporting time line for HADOOP 0.20 ? In my opinion till HADOOP 0.20 is de-supported we would want to test the behavior (alter bucket) for HADOOP 0.20 and hence require two different set of tests. Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
Laljo John Pullokkaran created HIVE-6687: Summary: JDBC ResultSet fails to get value by qualified projection name Key: HIVE-6687 URL: https://issues.apache.org/jira/browse/HIVE-6687 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Fix For: 0.12.1 Getting value from result set using fully qualified name would throw exception. Only solution today is to use position of the column as opposed to column label. String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y; ResultSet res = stmt.executeQuery(sql); res.getInt(r1.x); Fix is to fix resultsetschema in semantic analyzer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[ https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6687: - Description: Getting value from result set using fully qualified name would throw exception. Only solution today is to use position of the column as opposed to column label. String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y; ResultSet res = stmt.executeQuery(sql); res.getInt(r1.x); res.getInt(r1.x); would throw exception unknown column even though sql specifies it. Fix is to fix resultsetschema in semantic analyzer. was: Getting value from result set using fully qualified name would throw exception. Only solution today is to use position of the column as opposed to column label. String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y; ResultSet res = stmt.executeQuery(sql); res.getInt(r1.x); Fix is to fix resultsetschema in semantic analyzer. JDBC ResultSet fails to get value by qualified projection name -- Key: HIVE-6687 URL: https://issues.apache.org/jira/browse/HIVE-6687 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Fix For: 0.12.1 Getting value from result set using fully qualified name would throw exception. Only solution today is to use position of the column as opposed to column label. String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y; ResultSet res = stmt.executeQuery(sql); res.getInt(r1.x); res.getInt(r1.x); would throw exception unknown column even though sql specifies it. Fix is to fix resultsetschema in semantic analyzer. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6658: - Attachment: HIVE-6658.2.patch Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.2.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6658: - Attachment: (was: HIVE-6658.patch) Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.2.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13938587#comment-13938587 ] Laljo John Pullokkaran commented on HIVE-6658: -- I assumed there were older versions of hadoop that Hive supported ( 0.20). I have reworked the patch. Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.2.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6658) Modify Alter_numbuckets* test to reflect hadoop2 changes
[ https://issues.apache.org/jira/browse/HIVE-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6658: - Status: Patch Available (was: Open) Modify Alter_numbuckets* test to reflect hadoop2 changes Key: HIVE-6658 URL: https://issues.apache.org/jira/browse/HIVE-6658 Project: Hive Issue Type: Bug Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-6658.2.patch Hadoop2 now honors number of reducers config while running in local mode. This affects bucketing tests as the data gets properly bucketed in Hadoop2 (In hadoop1 all data ended up in same bucket while in local mode). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: HIVE-6687.patch
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Status: Patch Available (was: Open)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Status: Open (was: Patch Available)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: (was: HIVE-6687.patch)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: HIVE-6687.2.patch
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.2.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943398#comment-13943398
]
Laljo John Pullokkaran commented on HIVE-6687:
--
Apparently view schema also uses same result set schema.
Modified patch to:
1. Separate out View Schema vs Result Set Schema.
2. View Schema won't use qualified table names. View schema would also ensure
that column names are unique.
3. ResultSet schema by default would use table aliases if provided (select *,
or user provided qualified projections select r1.x..)
4. To get old behavior for result set schema, introduced a config param
hive.resultset.use.unique.column.names; this is set to true by default. User
will have to set this to false for old behavior.
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.2.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943399#comment-13943399
]
Laljo John Pullokkaran commented on HIVE-6687:
--
Vaibhav, I modified the test cases that seems like could get affected. If we
are not using JDBC1 then its a no-op.
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.2.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: (was: HIVE-6687.2.patch)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: HIVE-6687.3.patch
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.3.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Status: Patch Available (was: Open)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Fix For: 0.12.1
Attachments: HIVE-6687.3.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943587#comment-13943587
]
Laljo John Pullokkaran commented on HIVE-6687:
--
Review Board: https://reviews.apache.org/r/19551/
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.3.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: (was: HIVE-6687.3.patch)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.4.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Attachment: HIVE-6687.4.patch
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.4.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Status: Open (was: Patch Available)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.4.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Commented] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13944744#comment-13944744
]
Laljo John Pullokkaran commented on HIVE-6687:
--
Modified unit test print_header.q log file.
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.4.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (HIVE-6687) JDBC ResultSet fails to get value by qualified projection name
[
https://issues.apache.org/jira/browse/HIVE-6687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-6687:
-
Status: Patch Available (was: Open)
JDBC ResultSet fails to get value by qualified projection name
--
Key: HIVE-6687
URL: https://issues.apache.org/jira/browse/HIVE-6687
Project: Hive
Issue Type: Bug
Components: HiveServer2
Affects Versions: 0.12.0
Reporter: Laljo John Pullokkaran
Assignee: Laljo John Pullokkaran
Labels: documentation
Fix For: 0.12.1
Attachments: HIVE-6687.4.patch
Getting value from result set using fully qualified name would throw
exception. Only solution today is to use position of the column as opposed to
column label.
{code}
String sql = select r1.x, r2.x from r1 join r2 on r1.y=r2.y;
ResultSet res = stmt.executeQuery(sql);
res.getInt(r1.x);
{code}
res.getInt(r1.x); would throw exception unknown column even though sql
specifies it.
Fix is to fix resultsetschema in semantic analyzer.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Created] (HIVE-6819) Correctness issue with Hive limit operator predicate push down
Laljo John Pullokkaran created HIVE-6819: Summary: Correctness issue with Hive limit operator predicate push down Key: HIVE-6819 URL: https://issues.apache.org/jira/browse/HIVE-6819 Project: Hive Issue Type: Bug Components: Query Processor Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Fix For: 0.13.0 Following query produces 0 rows with Predicate Push Down optimization turned on; the same query produces 130 rows with predicate push down turned off. select t2.c_int from (select key, value, c_float, c_int from t1 order by key,value,c_float,c_int limit 10)t1 join t2 on t1.c_int=t2.c_int and t1.c_float=t2.c_float where t2.c_int=1; I could reproduce this on Apache Trunk. Haven't checked if previous releases have the same issue. hive desc t1; Query ID = jpullokkaran_20140401191515_36e441c6-074b-45ae-aff6-489e13a6f401 OK key string value string c_int int c_float float c_boolean boolean Time taken: 0.077 seconds, Fetched: 5 row(s) hive select distinct key, value, c_float, c_int from t1; OK 11 1.0 1 1 1 1.0 1 1 1 1.0 1 1 1 1.0 1 nullnullNULLNULL Time taken: 0.062 seconds, Fetched: 5 row(s) hive desc t2; Query ID = jpullokkaran_20140401191616_dfbd14bb-b5b8-4165-8d01-e9a61a7f1c33 OK key string value string c_int int c_float float c_boolean boolean Time taken: 0.062 seconds, Fetched: 5 row(s) hive select distinct key, value, c_float, c_int from t2; OK 11 1.0 1 1 1 1.0 1 1 1 1.0 1 1 1 1.0 1 2 2 2.0 2 nullnullNULLNULL Time taken: 4.698 seconds, Fetched: 6 row(s) hive select t2.c_int from (select key, value, c_float, c_int from t1 order by key,value,c_float,c_int limit 10)t1 join t2 on t1.c_int=t2.c_int and t1.c_float=t2.c_float where t2.c_int=1; MapredLocal task succeeded OK Time taken: 13.029 seconds hive hive select t2.c_int from (select key, value, c_float, c_int from t1 order by key,value,c_float,c_int limit 10)t1 join t2 on t1.c_int=t2.c_int and t1.c_float=t2.c_float where t2.c_int=1; MapredLocal task succeeded OK ... 1 1 1 1 1 1 1 1 1 1 1 Time taken: 9.317 seconds, Fetched: 130 row(s) hive -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-6867) Bucketized Table feature fails in some cases
Laljo John Pullokkaran created HIVE-6867: Summary: Bucketized Table feature fails in some cases Key: HIVE-6867 URL: https://issues.apache.org/jira/browse/HIVE-6867 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Bucketized Table feature fails in some cases. if src destination is bucketed on same key, and if actual data in the src is not bucketed (because data got loaded using LOAD DATA LOCAL INPATH ) then the data won't be bucketed while writing to destination. Example -- CREATE TABLE P1(key STRING, val STRING) CLUSTERED BY (key) SORTED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE; LOAD DATA LOCAL INPATH '/Users/jpullokkaran/apache-hive1/data/files/P1.txt' INTO TABLE P1; – perform an insert to make sure there are 2 files INSERT OVERWRITE TABLE P1 select key, val from P1; -- This is not a regression. This has never worked. This got only discovered due to Hadoop2 changes. In Hadoop1, in local mode, number of reducers will always be 1, regardless of what is requested by app. Hadoop2 now honors the number of reducer setting in local mode (by spawning threads). Long term solution seems to be to prevent load data for bucketed table. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6867) Bucketized Table feature fails in some cases
[ https://issues.apache.org/jira/browse/HIVE-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13963472#comment-13963472 ] Laljo John Pullokkaran commented on HIVE-6867: -- BucketingSortingReduceSinkOptimizer removes RS op if src destination is bucketed on same key. Bucketized Table feature fails in some cases Key: HIVE-6867 URL: https://issues.apache.org/jira/browse/HIVE-6867 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Bucketized Table feature fails in some cases. if src destination is bucketed on same key, and if actual data in the src is not bucketed (because data got loaded using LOAD DATA LOCAL INPATH ) then the data won't be bucketed while writing to destination. Example -- CREATE TABLE P1(key STRING, val STRING) CLUSTERED BY (key) SORTED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE; LOAD DATA LOCAL INPATH '/Users/jpullokkaran/apache-hive1/data/files/P1.txt' INTO TABLE P1; – perform an insert to make sure there are 2 files INSERT OVERWRITE TABLE P1 select key, val from P1; -- This is not a regression. This has never worked. This got only discovered due to Hadoop2 changes. In Hadoop1, in local mode, number of reducers will always be 1, regardless of what is requested by app. Hadoop2 now honors the number of reducer setting in local mode (by spawning threads). Long term solution seems to be to prevent load data for bucketed table. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-6867) Bucketized Table feature fails in some cases
[ https://issues.apache.org/jira/browse/HIVE-6867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-6867: - Description: Bucketized Table feature fails in some cases. if src destination is bucketed on same key, and if actual data in the src is not bucketed (because data got loaded using LOAD DATA LOCAL INPATH ) then the data won't be bucketed while writing to destination. Example -- CREATE TABLE P1(key STRING, val STRING) CLUSTERED BY (key) SORTED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE; LOAD DATA LOCAL INPATH '/Users/jp/apache-hive1/data/files/P1.txt' INTO TABLE P1; – perform an insert to make sure there are 2 files INSERT OVERWRITE TABLE P1 select key, val from P1; -- This is not a regression. This has never worked. This got only discovered due to Hadoop2 changes. In Hadoop1, in local mode, number of reducers will always be 1, regardless of what is requested by app. Hadoop2 now honors the number of reducer setting in local mode (by spawning threads). Long term solution seems to be to prevent load data for bucketed table. was: Bucketized Table feature fails in some cases. if src destination is bucketed on same key, and if actual data in the src is not bucketed (because data got loaded using LOAD DATA LOCAL INPATH ) then the data won't be bucketed while writing to destination. Example -- CREATE TABLE P1(key STRING, val STRING) CLUSTERED BY (key) SORTED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE; LOAD DATA LOCAL INPATH '/Users/jpullokkaran/apache-hive1/data/files/P1.txt' INTO TABLE P1; – perform an insert to make sure there are 2 files INSERT OVERWRITE TABLE P1 select key, val from P1; -- This is not a regression. This has never worked. This got only discovered due to Hadoop2 changes. In Hadoop1, in local mode, number of reducers will always be 1, regardless of what is requested by app. Hadoop2 now honors the number of reducer setting in local mode (by spawning threads). Long term solution seems to be to prevent load data for bucketed table. Bucketized Table feature fails in some cases Key: HIVE-6867 URL: https://issues.apache.org/jira/browse/HIVE-6867 Project: Hive Issue Type: Bug Components: HiveServer2 Affects Versions: 0.12.0 Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Bucketized Table feature fails in some cases. if src destination is bucketed on same key, and if actual data in the src is not bucketed (because data got loaded using LOAD DATA LOCAL INPATH ) then the data won't be bucketed while writing to destination. Example -- CREATE TABLE P1(key STRING, val STRING) CLUSTERED BY (key) SORTED BY (key) INTO 2 BUCKETS STORED AS TEXTFILE; LOAD DATA LOCAL INPATH '/Users/jp/apache-hive1/data/files/P1.txt' INTO TABLE P1; – perform an insert to make sure there are 2 files INSERT OVERWRITE TABLE P1 select key, val from P1; -- This is not a regression. This has never worked. This got only discovered due to Hadoop2 changes. In Hadoop1, in local mode, number of reducers will always be 1, regardless of what is requested by app. Hadoop2 now honors the number of reducer setting in local mode (by spawning threads). Long term solution seems to be to prevent load data for bucketed table. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970241#comment-13970241 ] Laljo John Pullokkaran commented on HIVE-5775: -- First rev of CBO. This is a limited version that does not support: 1. Outer Joins 2. Union 3. All of the UDFs 4. Doesn't play all permutations of joins Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-5775: - Attachment: HIVE-5775.1.patch Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13970417#comment-13970417 ] Laljo John Pullokkaran commented on HIVE-5775: -- Thanks Julian Hyde, Harish Bhutani for help with CBO V1. Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13971970#comment-13971970 ] Laljo John Pullokkaran commented on HIVE-5775: -- I don't think this should go in to trunk yet. I need to remove some of the limitations (outer join, union) before it can go on to trunk. Also a better algorithm for join permutations is also being worked on. Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-6439) Introduce CBO step in Semantic Analyzer
[ https://issues.apache.org/jira/browse/HIVE-6439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13902603#comment-13902603 ] Laljo John Pullokkaran commented on HIVE-6439: -- @Brock #2 Is the concern that we are swallowing the exception or is it that the log level should be info or warning instead of debug? Introduce CBO step in Semantic Analyzer --- Key: HIVE-6439 URL: https://issues.apache.org/jira/browse/HIVE-6439 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-6439.1.patch This patch introduces CBO step in SemanticAnalyzer. For now the CostBasedOptimizer is an empty shell. The contract between SemAly and CBO is: - CBO step is controlled by the 'hive.enable.cbo.flag'. - When true Hive SemAly will hand CBO a Hive Operator tree (with operators annotated with stats). If it can CBO will return a better plan in Hive AST form. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (HIVE-6540) Support Multi Column Stats
Laljo John Pullokkaran created HIVE-6540: Summary: Support Multi Column Stats Key: HIVE-6540 URL: https://issues.apache.org/jira/browse/HIVE-6540 Project: Hive Issue Type: Improvement Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran For Joins involving compound predicates, multi column stats can be used to accurately compute the NDV. Objective is to compute NDV of more than one columns. Compute NDV of (x,y,z). R1 IJ R2 on R1.x=R2.x and R1.y=R2.y and R1.z=R2.z can use max(NDV(R1.x, R1.y, R1.z), NDV(R2.x, R2.y, R2.z)) for Join NDV ( hence selectivity). http://www.oracle-base.com/articles/11g/statistics-collection-enhancements-11gr1.php#multi_column_statistics http://blogs.msdn.com/b/ianjo/archive/2005/11/10/491548.aspx http://developer.teradata.com/database/articles/removing-multi-column-statistics-a-process-for-identification-of-redundant-statist -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14040970#comment-14040970 ] Laljo John Pullokkaran commented on HIVE-5775: -- The cost model as described in the doc assumes TEZ as the execution layer. Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041053#comment-14041053 ] Laljo John Pullokkaran commented on HIVE-5775: -- Following may help in reducing the confusion: 1. In design doc the cost formula is for choosing Join Algorithm. The cost formula as described in the doc assumes Tez execution. 2. However current work on CBO doesn’t include Join algorithm selection. Instead it rearranges Join based on Join cardinality NDV. In other words Join reordering is not depended on Physical Execution Layer (Tez or MR). 3. When we decide to do Join Algorithm Selection we can fit in cost formula for both a) MR b) Tez. This way, based on the physical execution layer we can select best Join Algorithm/Order. 4. The cost formula for Join Algorithm selection is not that different between MR Tez (except for intermediate HDFS writes). So assume that CBO can support both execution layers rather easily. 5. CBO framework allows you to plug and play any cost model. There is no hard coupling. Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14041085#comment-14041085 ] Laljo John Pullokkaran commented on HIVE-5775: -- Cost Model described doesn't apply to current CBO work and for the proposed branch. It will apply only for Join Algorithm selection which is not part of the current work. IMO moving join reordering to physical optimizer is the not the correct solution. I would rather leave it in logical, since after doing join reordering you may able to do other optimizations like, new predicate push down, transitive inferences…. When we get around to do Join Algorithm selection there will be two cost formulas one for MR and one for Tez. I think best solution is to support both cost models and decide which one to apply based on physical execution layer. I will update the doc. Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7280) Commit CBO code from github repo to CBO branch
Laljo John Pullokkaran created HIVE-7280: Summary: Commit CBO code from github repo to CBO branch Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042677#comment-14042677 ] Laljo John Pullokkaran commented on HIVE-7280: -- Patch includes: 1. Optiq 0.8-snapshot integration 2. Join Reorder based on Cardinality, NDV (using Optiq) 3. Gen Optiq plan from Hive QL AST 4. Optiq Rel Node gets converted to Hive AST Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch.gz -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Attachment: (was: HIVE-7280.patch.gz) Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Attachment: HIVE-7280.patch Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Attachment: (was: HIVE-7280.patch) Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Status: Patch Available (was: Open) Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) Commit CBO code from github repo to CBO branch
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Attachment: HIVE-7280.patch Commit CBO code from github repo to CBO branch -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7283) CBO: plumb in HepPlanner and FieldTrimmer(ColumnPruner) into Optiq based planning
[ https://issues.apache.org/jira/browse/HIVE-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14042876#comment-14042876 ] Laljo John Pullokkaran commented on HIVE-7283: -- +1 CBO: plumb in HepPlanner and FieldTrimmer(ColumnPruner) into Optiq based planning - Key: HIVE-7283 URL: https://issues.apache.org/jira/browse/HIVE-7283 Project: Hive Issue Type: Sub-task Components: Query Processor Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7283.1.patch 1. HepPlanner initially used for: - Predicate Pushdown - Transitive Predicate inference - Partition Pruning 2. Use Optiq's FieldTrimmer for ColumnPruner To begin with the rules are copies of Optiq base rules. Once Optiq is refactored to work on Base RelNode classes, the copied rules will be removed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7310) Turning CBO on results in NPE on some queries
[
https://issues.apache.org/jira/browse/HIVE-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-7310:
-
Attachment: HIVE-7310.patch
Turning CBO on results in NPE on some queries
-
Key: HIVE-7310
URL: https://issues.apache.org/jira/browse/HIVE-7310
Project: Hive
Issue Type: Sub-task
Reporter: Gunther Hagleitner
Assignee: Laljo John Pullokkaran
Labels: cbo
Attachments: HIVE-7310.patch
On the CBO branch if I do the following:
hive set hive.cbo.enable=true;
hive select i_item_id,
s_state,
GROUPING__ID,
avg(ss_quantity) agg1,
avg(ss_list_price) agg2,
avg(ss_coupon_amt) agg3,
avg(ss_sales_price) agg4
from store_sales ss
join customer_demographics cd on (ss.ss_cdemo_sk = cd.cd_demo_sk)
join date_dim d on (ss.ss_sold_date_sk = d.d_date_sk)
join store s on (ss.ss_store_sk = s.s_store_sk)
join item i on (ss.ss_item_sk = i.i_item_sk)
where cd_gender = 'M' and
cd_marital_status = 'S' and
cd_education_status = 'Secondary' and
d_year = 2002 and
s_state in ('OH','SD', 'LA', 'MO', 'WA', 'MN')
group by i_item_id, s_state with rollup
order by i_item_id
,s_state
limit 100
;
I get an NPE. The stack trace is:
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException: java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9555)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:328)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:412)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:308)
at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:962)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1027)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:898)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:888)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:277)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:229)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:439)
at
org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:812)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:706)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:645)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.getOptimizedAST(SemanticAnalyzer.java:11732)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.access$200(SemanticAnalyzer.java:11711)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9532)
... 18 more
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at
net.hydromatic.optiq.tools.Frameworks.withPrepare(Frameworks.java:170)
at
net.hydromatic.optiq.tools.Frameworks.withPlanner(Frameworks.java:142)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.getOptimizedAST(SemanticAnalyzer.java:11727)
... 20 more
Caused by: java.lang.NullPointerException
at
org.eigenbase.reltype.RelDataTypeImpl.getField(RelDataTypeImpl.java:79)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.convertAgg(SemanticAnalyzer.java:12129)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genGBRelNode(SemanticAnalyzer.java:12184)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genGBLogicalPlan(SemanticAnalyzer.java:12324)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genLogicalPlan(SemanticAnalyzer.java:12749)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.apply(SemanticAnalyzer.java:11758)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.apply(SemanticAnalyzer.java:11711)
at net.hydromatic.optiq.tools.Frameworks$1.apply(Frameworks.java:146)
[jira] [Updated] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-5775: - Attachment: HIVE-7310.patch Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-5775) Introduce Cost Based Optimizer to Hive
[ https://issues.apache.org/jira/browse/HIVE-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-5775: - Attachment: (was: HIVE-7310.patch) Introduce Cost Based Optimizer to Hive -- Key: HIVE-5775 URL: https://issues.apache.org/jira/browse/HIVE-5775 Project: Hive Issue Type: New Feature Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: CBO-2.pdf, HIVE-5775.1.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7310) Turning CBO on results in NPE on some queries
[
https://issues.apache.org/jira/browse/HIVE-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laljo John Pullokkaran updated HIVE-7310:
-
Status: Patch Available (was: Open)
Turning CBO on results in NPE on some queries
-
Key: HIVE-7310
URL: https://issues.apache.org/jira/browse/HIVE-7310
Project: Hive
Issue Type: Sub-task
Reporter: Gunther Hagleitner
Assignee: Laljo John Pullokkaran
Labels: cbo
Attachments: HIVE-7310.patch
On the CBO branch if I do the following:
hive set hive.cbo.enable=true;
hive select i_item_id,
s_state,
GROUPING__ID,
avg(ss_quantity) agg1,
avg(ss_list_price) agg2,
avg(ss_coupon_amt) agg3,
avg(ss_sales_price) agg4
from store_sales ss
join customer_demographics cd on (ss.ss_cdemo_sk = cd.cd_demo_sk)
join date_dim d on (ss.ss_sold_date_sk = d.d_date_sk)
join store s on (ss.ss_store_sk = s.s_store_sk)
join item i on (ss.ss_item_sk = i.i_item_sk)
where cd_gender = 'M' and
cd_marital_status = 'S' and
cd_education_status = 'Secondary' and
d_year = 2002 and
s_state in ('OH','SD', 'LA', 'MO', 'WA', 'MN')
group by i_item_id, s_state with rollup
order by i_item_id
,s_state
limit 100
;
I get an NPE. The stack trace is:
java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.RuntimeException: java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9555)
at
org.apache.hadoop.hive.ql.parse.BaseSemanticAnalyzer.analyze(BaseSemanticAnalyzer.java:328)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:412)
at org.apache.hadoop.hive.ql.Driver.compile(Driver.java:308)
at org.apache.hadoop.hive.ql.Driver.compileInternal(Driver.java:962)
at org.apache.hadoop.hive.ql.Driver.runInternal(Driver.java:1027)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:898)
at org.apache.hadoop.hive.ql.Driver.run(Driver.java:888)
at
org.apache.hadoop.hive.cli.CliDriver.processLocalCmd(CliDriver.java:277)
at org.apache.hadoop.hive.cli.CliDriver.processCmd(CliDriver.java:229)
at org.apache.hadoop.hive.cli.CliDriver.processLine(CliDriver.java:439)
at
org.apache.hadoop.hive.cli.CliDriver.executeDriver(CliDriver.java:812)
at org.apache.hadoop.hive.cli.CliDriver.run(CliDriver.java:706)
at org.apache.hadoop.hive.cli.CliDriver.main(CliDriver.java:645)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.apache.hadoop.util.RunJar.main(RunJar.java:212)
Caused by: java.lang.RuntimeException: java.lang.RuntimeException:
java.lang.NullPointerException
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.getOptimizedAST(SemanticAnalyzer.java:11732)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.access$200(SemanticAnalyzer.java:11711)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer.analyzeInternal(SemanticAnalyzer.java:9532)
... 18 more
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at
net.hydromatic.optiq.tools.Frameworks.withPrepare(Frameworks.java:170)
at
net.hydromatic.optiq.tools.Frameworks.withPlanner(Frameworks.java:142)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.getOptimizedAST(SemanticAnalyzer.java:11727)
... 20 more
Caused by: java.lang.NullPointerException
at
org.eigenbase.reltype.RelDataTypeImpl.getField(RelDataTypeImpl.java:79)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.convertAgg(SemanticAnalyzer.java:12129)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genGBRelNode(SemanticAnalyzer.java:12184)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genGBLogicalPlan(SemanticAnalyzer.java:12324)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.genLogicalPlan(SemanticAnalyzer.java:12749)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.apply(SemanticAnalyzer.java:11758)
at
org.apache.hadoop.hive.ql.parse.SemanticAnalyzer$OptiqBasedPlanner.apply(SemanticAnalyzer.java:11711)
at
[jira] [Assigned] (HIVE-7312) CBO throws ArrayIndexOutOfBounds
[ https://issues.apache.org/jira/browse/HIVE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran reassigned HIVE-7312: Assignee: Laljo John Pullokkaran CBO throws ArrayIndexOutOfBounds Key: HIVE-7312 URL: https://issues.apache.org/jira/browse/HIVE-7312 Project: Hive Issue Type: Sub-task Reporter: Gunther Hagleitner Assignee: Laljo John Pullokkaran Running tpcds query 17. Still confirming if col stats are available. When I turn CBO on (this is just the relevant snipped, the actual exception is pages long): Caused by: java.lang.IndexOutOfBoundsException: Index: 24, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at org.apache.hadoop.hive.ql.optimizer.optiq.RelOptHiveTable.getColStat(RelOptHiveTable.java:97) at org.apache.hadoop.hive.ql.optimizer.optiq.reloperators.HiveTableScanRel.getColStat(HiveTableScanRel.java:73) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:47) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:36) ... 272 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7312) CBO throws ArrayIndexOutOfBounds
[ https://issues.apache.org/jira/browse/HIVE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7312: - Status: Patch Available (was: Open) CBO throws ArrayIndexOutOfBounds Key: HIVE-7312 URL: https://issues.apache.org/jira/browse/HIVE-7312 Project: Hive Issue Type: Sub-task Reporter: Gunther Hagleitner Assignee: Laljo John Pullokkaran Attachments: HIVE-7312.patch Running tpcds query 17. Still confirming if col stats are available. When I turn CBO on (this is just the relevant snipped, the actual exception is pages long): Caused by: java.lang.IndexOutOfBoundsException: Index: 24, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at org.apache.hadoop.hive.ql.optimizer.optiq.RelOptHiveTable.getColStat(RelOptHiveTable.java:97) at org.apache.hadoop.hive.ql.optimizer.optiq.reloperators.HiveTableScanRel.getColStat(HiveTableScanRel.java:73) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:47) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:36) ... 272 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7312) CBO throws ArrayIndexOutOfBounds
[ https://issues.apache.org/jira/browse/HIVE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7312: - Attachment: HIVE-7312.patch CBO throws ArrayIndexOutOfBounds Key: HIVE-7312 URL: https://issues.apache.org/jira/browse/HIVE-7312 Project: Hive Issue Type: Sub-task Reporter: Gunther Hagleitner Assignee: Laljo John Pullokkaran Attachments: HIVE-7312.patch Running tpcds query 17. Still confirming if col stats are available. When I turn CBO on (this is just the relevant snipped, the actual exception is pages long): Caused by: java.lang.IndexOutOfBoundsException: Index: 24, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at org.apache.hadoop.hive.ql.optimizer.optiq.RelOptHiveTable.getColStat(RelOptHiveTable.java:97) at org.apache.hadoop.hive.ql.optimizer.optiq.reloperators.HiveTableScanRel.getColStat(HiveTableScanRel.java:73) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:47) at org.apache.hadoop.hive.ql.optimizer.optiq.stats.HiveRelMdDistinctRowCount.getDistinctRowCount(HiveRelMdDistinctRowCount.java:36) ... 272 more -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7280) CBO V1
[ https://issues.apache.org/jira/browse/HIVE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7280: - Summary: CBO V1 (was: Commit CBO code from github repo to CBO branch) CBO V1 -- Key: HIVE-7280 URL: https://issues.apache.org/jira/browse/HIVE-7280 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7280.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (HIVE-7367) Support count(distinct)
[ https://issues.apache.org/jira/browse/HIVE-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran reassigned HIVE-7367: Assignee: Laljo John Pullokkaran Support count(distinct) --- Key: HIVE-7367 URL: https://issues.apache.org/jira/browse/HIVE-7367 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7367) Support count(distinct)
Laljo John Pullokkaran created HIVE-7367: Summary: Support count(distinct) Key: HIVE-7367 URL: https://issues.apache.org/jira/browse/HIVE-7367 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7369) Support agg distinct function with GB
Laljo John Pullokkaran created HIVE-7369: Summary: Support agg distinct function with GB Key: HIVE-7369 URL: https://issues.apache.org/jira/browse/HIVE-7369 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7369) Support agg distinct function with GB
[ https://issues.apache.org/jira/browse/HIVE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7369: - Status: Patch Available (was: Open) Support agg distinct function with GB - Key: HIVE-7369 URL: https://issues.apache.org/jira/browse/HIVE-7369 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7369.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7369) Support agg distinct function with GB
[ https://issues.apache.org/jira/browse/HIVE-7369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7369: - Attachment: HIVE-7369.patch Support agg distinct function with GB - Key: HIVE-7369 URL: https://issues.apache.org/jira/browse/HIVE-7369 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7369.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7392) Support Columns Stats for Partition Columns
Laljo John Pullokkaran created HIVE-7392: Summary: Support Columns Stats for Partition Columns Key: HIVE-7392 URL: https://issues.apache.org/jira/browse/HIVE-7392 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Ashutosh Chauhan -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7395) Work around non availability of stats for partition columns
Laljo John Pullokkaran created HIVE-7395: Summary: Work around non availability of stats for partition columns Key: HIVE-7395 URL: https://issues.apache.org/jira/browse/HIVE-7395 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7395) Work around non availability of stats for partition columns
[ https://issues.apache.org/jira/browse/HIVE-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7395: - Attachment: HIVE-7395.patch Work around non availability of stats for partition columns --- Key: HIVE-7395 URL: https://issues.apache.org/jira/browse/HIVE-7395 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7395.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7395) Work around non availability of stats for partition columns
[ https://issues.apache.org/jira/browse/HIVE-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7395: - Status: Patch Available (was: Open) Work around non availability of stats for partition columns --- Key: HIVE-7395 URL: https://issues.apache.org/jira/browse/HIVE-7395 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7395.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7401) Fetch Column stats on Demand
Laljo John Pullokkaran created HIVE-7401: Summary: Fetch Column stats on Demand Key: HIVE-7401 URL: https://issues.apache.org/jira/browse/HIVE-7401 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (HIVE-7401) Fetch Column stats on Demand
[ https://issues.apache.org/jira/browse/HIVE-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran resolved HIVE-7401. -- Resolution: Fixed Fetch Column stats on Demand Key: HIVE-7401 URL: https://issues.apache.org/jira/browse/HIVE-7401 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7401) Fetch Column stats on Demand
[ https://issues.apache.org/jira/browse/HIVE-7401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14060990#comment-14060990 ] Laljo John Pullokkaran commented on HIVE-7401: -- Resolved by Fix for HIVE-7395 Fetch Column stats on Demand Key: HIVE-7401 URL: https://issues.apache.org/jira/browse/HIVE-7401 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7367) Support count(distinct)
[ https://issues.apache.org/jira/browse/HIVE-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14061573#comment-14061573 ] Laljo John Pullokkaran commented on HIVE-7367: -- Resolved by fix for HIVE-7369. Support count(distinct) --- Key: HIVE-7367 URL: https://issues.apache.org/jira/browse/HIVE-7367 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (HIVE-7367) Support count(distinct)
[ https://issues.apache.org/jira/browse/HIVE-7367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran resolved HIVE-7367. -- Resolution: Fixed Support count(distinct) --- Key: HIVE-7367 URL: https://issues.apache.org/jira/browse/HIVE-7367 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7407) Handle UDFs generically
[ https://issues.apache.org/jira/browse/HIVE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7407: - Summary: Handle UDFs generically (was: Handle UDF Translations) Handle UDFs generically --- Key: HIVE-7407 URL: https://issues.apache.org/jira/browse/HIVE-7407 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7407) Handle UDF Translations
Laljo John Pullokkaran created HIVE-7407: Summary: Handle UDF Translations Key: HIVE-7407 URL: https://issues.apache.org/jira/browse/HIVE-7407 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7407) Handle UDFs generically
[ https://issues.apache.org/jira/browse/HIVE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7407: - Attachment: HIVE-7407.patch Handle UDFs generically --- Key: HIVE-7407 URL: https://issues.apache.org/jira/browse/HIVE-7407 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7407.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7407) Handle UDFs generically
[ https://issues.apache.org/jira/browse/HIVE-7407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7407: - Status: Patch Available (was: Open) Handle UDFs generically --- Key: HIVE-7407 URL: https://issues.apache.org/jira/browse/HIVE-7407 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7407.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7413) Fall back to Non-CBO optimizer if CBO fails
Laljo John Pullokkaran created HIVE-7413: Summary: Fall back to Non-CBO optimizer if CBO fails Key: HIVE-7413 URL: https://issues.apache.org/jira/browse/HIVE-7413 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7425) Add log info to trace cbo path
Laljo John Pullokkaran created HIVE-7425: Summary: Add log info to trace cbo path Key: HIVE-7425 URL: https://issues.apache.org/jira/browse/HIVE-7425 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7413) Fall back to Non-CBO optimizer if CBO fails
[ https://issues.apache.org/jira/browse/HIVE-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7413: - Status: Patch Available (was: Open) Fall back to Non-CBO optimizer if CBO fails --- Key: HIVE-7413 URL: https://issues.apache.org/jira/browse/HIVE-7413 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7413.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7413) Fall back to Non-CBO optimizer if CBO fails
[ https://issues.apache.org/jira/browse/HIVE-7413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7413: - Attachment: HIVE-7413.patch Fall back to Non-CBO optimizer if CBO fails --- Key: HIVE-7413 URL: https://issues.apache.org/jira/browse/HIVE-7413 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran Attachments: HIVE-7413.patch -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (HIVE-7425) Add log info to trace cbo path
[ https://issues.apache.org/jira/browse/HIVE-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14062948#comment-14062948 ] Laljo John Pullokkaran commented on HIVE-7425: -- Resolved by Fix for Hive-7413 Add log info to trace cbo path -- Key: HIVE-7425 URL: https://issues.apache.org/jira/browse/HIVE-7425 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (HIVE-7425) Add log info to trace cbo path
[ https://issues.apache.org/jira/browse/HIVE-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran resolved HIVE-7425. -- Resolution: Fixed Add log info to trace cbo path -- Key: HIVE-7425 URL: https://issues.apache.org/jira/browse/HIVE-7425 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7284) CBO: create Partition Pruning rules in Optiq
[ https://issues.apache.org/jira/browse/HIVE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7284: - Status: Open (was: Patch Available) CBO: create Partition Pruning rules in Optiq Key: HIVE-7284 URL: https://issues.apache.org/jira/browse/HIVE-7284 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7284.1.patch, HIVE-7284.1.patch NO PRECOMMIT TESTS Create rules in Optiq that do the job of the PartitionPruner. For now we will reuse the logic that evaluates the Partition list from prunedExpr. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7284) CBO: create Partition Pruning rules in Optiq
[ https://issues.apache.org/jira/browse/HIVE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7284: - Attachment: HIVE-7284.2.patch CBO: create Partition Pruning rules in Optiq Key: HIVE-7284 URL: https://issues.apache.org/jira/browse/HIVE-7284 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7284.1.patch, HIVE-7284.1.patch, HIVE-7284.2.patch NO PRECOMMIT TESTS Create rules in Optiq that do the job of the PartitionPruner. For now we will reuse the logic that evaluates the Partition list from prunedExpr. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7284) CBO: create Partition Pruning rules in Optiq
[ https://issues.apache.org/jira/browse/HIVE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7284: - Status: Patch Available (was: Open) Updated Patch to do stats fetching on demand. We need to add rules to push filter through, project, set operators, GB. Need to add rules to combine filters. Also constant folding may improve partition Pruning. CBO: create Partition Pruning rules in Optiq Key: HIVE-7284 URL: https://issues.apache.org/jira/browse/HIVE-7284 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7284.1.patch, HIVE-7284.1.patch, HIVE-7284.2.patch NO PRECOMMIT TESTS Create rules in Optiq that do the job of the PartitionPruner. For now we will reuse the logic that evaluates the Partition list from prunedExpr. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7284) CBO: create Partition Pruning rules in Optiq
[ https://issues.apache.org/jira/browse/HIVE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7284: - Attachment: (was: HIVE-7284.2.patch) CBO: create Partition Pruning rules in Optiq Key: HIVE-7284 URL: https://issues.apache.org/jira/browse/HIVE-7284 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7284.1.patch, HIVE-7284.1.patch NO PRECOMMIT TESTS Create rules in Optiq that do the job of the PartitionPruner. For now we will reuse the logic that evaluates the Partition list from prunedExpr. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (HIVE-7284) CBO: create Partition Pruning rules in Optiq
[ https://issues.apache.org/jira/browse/HIVE-7284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Laljo John Pullokkaran updated HIVE-7284: - Attachment: HIVE-7284.2.patch CBO: create Partition Pruning rules in Optiq Key: HIVE-7284 URL: https://issues.apache.org/jira/browse/HIVE-7284 Project: Hive Issue Type: Sub-task Reporter: Harish Butani Assignee: Harish Butani Attachments: HIVE-7284.1.patch, HIVE-7284.1.patch, HIVE-7284.2.patch NO PRECOMMIT TESTS Create rules in Optiq that do the job of the PartitionPruner. For now we will reuse the logic that evaluates the Partition list from prunedExpr. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (HIVE-7453) Partition Pruning enhancements 1
Laljo John Pullokkaran created HIVE-7453: Summary: Partition Pruning enhancements 1 Key: HIVE-7453 URL: https://issues.apache.org/jira/browse/HIVE-7453 Project: Hive Issue Type: Sub-task Reporter: Laljo John Pullokkaran Assignee: Laljo John Pullokkaran 1. Handle type casts 2. Handle Literal Conversion for Partition Pruning expressions -- This message was sent by Atlassian JIRA (v6.2#6252)
