[
https://issues.apache.org/jira/browse/HIVE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265300#comment-14265300
]
Pala M Muthaia commented on HIVE-9223:
--
[~vikram.dixit]
> HiveServer2 on Tez
[
https://issues.apache.org/jira/browse/HIVE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265151#comment-14265151
]
Pala M Muthaia commented on HIVE-9223:
--
Yes, single HS2 session that receive mult
[
https://issues.apache.org/jira/browse/HIVE-9223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260599#comment-14260599
]
Pala M Muthaia commented on HIVE-9223:
--
[~hagleitn] & [~vikram.dixit], c
Pala M Muthaia created HIVE-9223:
Summary: HiveServer2 on Tez doesn't support concurrent queries
Key: HIVE-9223
URL: https://issues.apache.org/jira/browse/HIVE-9223
Project: Hive
Issue
When a user submits multiple queries in the same HS2 session (using thrift
interface), the query goes through the same TezSessionState and ends up
being submitted to the same Tez AM, and then fails with the error "App
master already running a DAG"
Is this by design? I looked into the code, and the
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14205607#comment-14205607
]
Pala M Muthaia commented on HIVE-7949:
--
For Hive 14 this need not be documented s
[
https://issues.apache.org/jira/browse/HIVE-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14170172#comment-14170172
]
Pala M Muthaia commented on HIVE-7782:
--
I am investigating this.
In a hive ses
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14120237#comment-14120237
]
Pala M Muthaia commented on HIVE-7949:
--
[~ashutoshc] & [~navis], can eithe
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119181#comment-14119181
]
Pala M Muthaia commented on HIVE-7949:
--
clientpositive tests do not detect
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-7949:
-
Fix Version/s: 0.13.0
0.13.1
Status: Patch Available (was: Open
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-7949:
-
Attachment: HIVE-7949.1.patch
> Create table LIKE command doesn't set n
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-7949:
-
Description:
'Create table like' command doesn't set the current user as own
[
https://issues.apache.org/jira/browse/HIVE-7949?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-7949:
-
Component/s: Query Processor
Description:
Create table like command doesn'
Pala M Muthaia created HIVE-7949:
Summary: Create table LIKE
Key: HIVE-7949
URL: https://issues.apache.org/jira/browse/HIVE-7949
Project: Hive
Issue Type: Bug
Reporter: Pala M
[
https://issues.apache.org/jira/browse/HIVE-7882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia resolved HIVE-7882.
--
Resolution: Duplicate
Looks like duplicate of HIVE-7635
> Multiple occurrences of s
Pala M Muthaia created HIVE-7882:
Summary: Multiple occurrences of same aggregate function with
different casing results in error
Key: HIVE-7882
URL: https://issues.apache.org/jira/browse/HIVE-7882
[
https://issues.apache.org/jira/browse/HIVE-7882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-7882:
-
Description:
The query
select sum(a), SUM(a) from t;
throws error shown in the stack below but
:10 PM, Pala M Muthaia
wrote:
> Thanks for the response Navis.
>
> I tried the repro again from the beginning, and it doesn't result in hash
> table generation. I may have had some setting that enforced map join. The
> plan generated shows a conditional stage pointing to a sim
14 at 7:20 PM, Navis류승우 wrote:
> I don't think hash table generation is needed for SMB joins. Could you
> check the result of explain extended?
>
> Thanks,
> Navis
>
>
> 2014-07-31 4:08 GMT+09:00 Pala M Muthaia :
>
> > +hive-users
> >
> >
>
+hive-users
On Tue, Jul 29, 2014 at 1:56 PM, Pala M Muthaia wrote:
> Hi,
>
> I am testing SMB join for 2 large tables. The tables are bucketed and
> sorted on the join column. I notice that even though the table is large,
> Hive attempts to generate hash table for the '
Hi,
I am testing SMB join for 2 large tables. The tables are bucketed and
sorted on the join column. I notice that even though the table is large,
Hive attempts to generate hash table for the 'small' table locally,
similar to map join. Since the table is large in my case, the client runs
out of m
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13967001#comment-13967001
]
Pala M Muthaia commented on HIVE-6131:
--
You are right, types of existing columns
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13966111#comment-13966111
]
Pala M Muthaia commented on HIVE-6131:
--
Do you mean allowing schema update statem
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13964556#comment-13964556
]
Pala M Muthaia commented on HIVE-6131:
--
Yes, one case where partition colum
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963641#comment-13963641
]
Pala M Muthaia commented on HIVE-6131:
--
I looked into the failures above
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955767#comment-13955767
]
Pala M Muthaia commented on HIVE-6131:
--
[~szehon], i have reuploaded the patch
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Attachment: HIVE-6131.1.patch
> New columns after table alter result in null values despite d
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Attachment: (was: HIVE-6131.1.patch.txt)
> New columns after table alter result in n
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Attachment: HIVE-6131.1.patch.txt
> New columns after table alter result in null values desp
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Attachment: (was: HIVE-6131.1.patch.txt)
> New columns after table alter result in n
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955727#comment-13955727
]
Pala M Muthaia commented on HIVE-6131:
--
Thanks, will do [~ashutoshc]. However, i
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13955570#comment-13955570
]
Pala M Muthaia commented on HIVE-6131:
--
[~ashutoshc], any thoughts on this?
&
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945773#comment-13945773
]
Pala M Muthaia commented on HIVE-6131:
--
That thought did cross my mind. Howeve
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Affects Version/s: 0.13.0
> New columns after table alter result in null values despite d
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Affects Version/s: 0.11.0
0.12.0
Status: Patch Available
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13945589#comment-13945589
]
Pala M Muthaia commented on HIVE-6131:
--
The above was intended to be code re
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6131:
-
Attachment: HIVE-6131.1.patch.txt
HIVE-6131: Honor latest table schema for partition data
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942410#comment-13942410
]
Pala M Muthaia commented on HIVE-6131:
--
Ok, i'll work on the patch.
[~ashut
[
https://issues.apache.org/jira/browse/HIVE-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941289#comment-13941289
]
Pala M Muthaia commented on HIVE-6131:
--
Browsing the code, it seems like this
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850984#comment-13850984
]
Pala M Muthaia commented on HIVE-6028:
--
Sergey, the same thing above works in hiv
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13848120#comment-13848120
]
Pala M Muthaia commented on HIVE-6028:
--
Thanks for following up Sergey Shelu
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13847924#comment-13847924
]
Pala M Muthaia commented on HIVE-6028:
--
Xuefu, you are right that using st
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6028:
-
Description:
When parsing/analyzing query, hive treats partition predicate value as int
instead
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6028:
-
Attachment: Hive-6028-explain-plan.txt
> Partition predicate literals are not interpre
[
https://issues.apache.org/jira/browse/HIVE-6028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pala M Muthaia updated HIVE-6028:
-
Description:
When parsing/analyzing query, hive treats partition predicate value as int
instead
Pala M Muthaia created HIVE-6028:
Summary: Partition predicate literals are not interpreted
correctly.
Key: HIVE-6028
URL: https://issues.apache.org/jira/browse/HIVE-6028
Project: Hive
[
https://issues.apache.org/jira/browse/HIVE-5149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750551#comment-13750551
]
Pala M Muthaia commented on HIVE-5149:
--
Currently, there is a workaround to a
> >>> optimization to work the group bys partitioning should be on the column
> >>> 1 only.
> >>>
> >>> It wont effect the correctness of group by, can make it slow but int
> >>> this case will fasten the overall query performance.
> &g
I have attached the hive 10 and 11 query plans, for the sample query below,
for illustration.
On Fri, Aug 23, 2013 at 5:35 PM, Pala M Muthaia wrote:
> Hi,
>
> We are using DISTRIBUTE BY with custom reducer scripts in our query
> workload.
>
> After upgrade to Hive 0.11, que
Hi,
We are using DISTRIBUTE BY with custom reducer scripts in our query
workload.
After upgrade to Hive 0.11, queries with GROUP BY/DISTRIBUTE BY/SORT BY and
custom reducer scripts produced incorrect results. Particularly, rows with
same value on DISTRIBUTE BY column ends up in multiple reducers
50 matches
Mail list logo
