[
https://issues.apache.org/jira/browse/HIVE-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-10931:
-
Description:
The following set of queries :
{code:sql}
DROP TABLE IF EXISTS test1 ;
DROP TABLE IF EXISTS
[
https://issues.apache.org/jira/browse/HIVE-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-10931:
-
Description:
The following set of queries :
{code:sql}
DROP TABLE IF EXISTS test1 ;
DROP TABLE IF EXISTS
[
https://issues.apache.org/jira/browse/HIVE-11192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616963#comment-14616963
]
Furcy Pin commented on HIVE-11192:
--
My apologies, this was not a bug but the expected
[
https://issues.apache.org/jira/browse/HIVE-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-12258:
-
Description:
When hive.support.concurrency is enabled if you launch a query that reads data
from a
[
https://issues.apache.org/jira/browse/HIVE-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-12258:
-
Description:
When hive.support.concurrency is enabled if you launch a query that reads data
from a
[
https://issues.apache.org/jira/browse/HIVE-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-12258:
-
Description:
When hive.support.concurrency is enabled if you launch a query that reads data
from a
[
https://issues.apache.org/jira/browse/HIVE-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-12258:
-
Description:
When hive.support.concurrency is enabled if you launch a query that reads data
from a
[
https://issues.apache.org/jira/browse/HIVE-12258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14973263#comment-14973263
]
Furcy Pin commented on HIVE-12258:
--
Besides, even after killing beeline, the locks are still active, with
[
https://issues.apache.org/jira/browse/HIVE-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14956499#comment-14956499
]
Furcy Pin commented on HIVE-12028:
--
Exactly, it's the same as "cast(null as int)".
Only shorter and
[
https://issues.apache.org/jira/browse/HIVE-12028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14952901#comment-14952901
]
Furcy Pin commented on HIVE-12028:
--
I found a simpler workaround :
SELECT collect_set(INT(NULL)) ;
This
[
https://issues.apache.org/jira/browse/HIVE-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14616478#comment-14616478
]
Furcy Pin commented on HIVE-10931:
--
I tried to reproduce on a local environment on the
[
https://issues.apache.org/jira/browse/HIVE-10931?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Furcy Pin updated HIVE-10931:
-
Fix Version/s: 1.2.1
Wrong columns selected on multiple joins
[
https://issues.apache.org/jira/browse/HIVE-7483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14714475#comment-14714475
]
Furcy Pin commented on HIVE-7483:
-
I confirm, we are having the same issue on Hive 1.1.0,
[
https://issues.apache.org/jira/browse/HIVE-6050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15711624#comment-15711624
]
Furcy Pin commented on HIVE-6050:
-
Hi,
I ran into the same problem, and found a workaround for my setup,
14 matches
Mail list logo