回复： hive 0.11 auto convert join bug report

Hi Navis, My colleague chenchun finds that hashcode of 'deal' and 'dim_pay_date' are the same and the code in MapJoinProcessor.java ignores the order of rowschema. I look at your patch and it's exactly the same place we are working on. Thanks for your patch. 在 2013年8月11日星期日，下午9:38，Navis류승우 写道：

回复： hive 0.11 auto convert join bug report

Hi all: when I change the table alias dim_pay_date to A, the query pass in hive 0.11(https://gist.github.com/code6/6187569#file-hive11_auto_convert_join_change_alias_pass): use test; create table if not exists src ( `key` int,`val` string); load data local inpath '/Users/code6/git/hive/data/files

hive 0.11 auto convert join bug report

Hi all: I'm currently testing hive11 and encounter one bug with hive.auto.convert.join, I construct a testcase so everyone can reproduce it(or you can reach the testcase here:https://gist.github.com/code6/6187569#file-hive11_auto_convert_join_bug): use test; create table src ( `key` int,`val`

回复： BUG IN HIVE-4650 seems not fixed

Hi Yin: Thanks for the patch, I patch it and pass this testcase, I will use it with our hive11 production test. 在 2013年8月1日星期四，上午5:09，Yin Huai 写道： > I just uploaded a patch to https://issues.apache.org/jira/browse/HIVE-4968. > You can try it and see if the problem has been resolved for you

回复： BUG IN HIVE-4650 seems not fixed

Hi: I attach the output of EXPLAIN, and the hive I use is compiled from trunk and my hadoop version is 1.0.1. I use default hive configuration. -- wzc1...@gmail.com 已使用 Sparrow (http://www.sparrowmailapp.com/?sig) 已使用 Sparrow (http://www.sparrowmailapp.com/?sig) 在 2013年7月29日星期一，下午1:08，Yi

回复： BUG IN HIVE-4650 seems not fixed

What I mean by "not pass the testcase in HIVE-4650" is that I compile the trunk code and run the query in HIVE-4650: SELECT * FROM (SELECT VAL001 x1, VAL002 x2, VAL003 x3, VAL004 x4, VAL005 y FROM (SELECT /*+ mapjoin(v2) */ (VAL001- mu1) * 1/(sd1

BUG IN HIVE-4650 seems not fixed

hi all: We are currently testing hive 0.11 against our production environment and run into some problems. Some of them are related to the param "hive.auto.convert.join". We disable this param and some failed testcases passed. By searching in hive jira issues I find that the patch in HIVE-465

回复： different outer join plan between hive 0.9 and hive 0.10

oblem :) -- wzc1989 已使用 Sparrow (http://www.sparrowmailapp.com/?sig) 在 2013年7月2日星期二，上午8:24，Navis류승우 写道： > Yes, a little bit. > > IMHO, these flags could be assigned only for aliases with condition on > 'on' clause. Then, I think, even a byte (8 flags) could be enough in > most cas

回复： different outer join plan between hive 0.9 and hive 0.10

ong/int in every row cost too much? -- wzc1989 已使用 Sparrow (http://www.sparrowmailapp.com/?sig) 在 2013年5月14日星期二，下午2:17，Navis류승우 写道： > In short, hive tags rows a filter mask as a short for outer join, > which can contain 16 flags. (see HIVE-3411, plz) > > I'll survey for

回复： different outer join plan between hive 0.9 and hive 0.10

hive 0.10 while we run such query well under hive 0.9. I believe it's due to the diff of query plan. I wonder why hive 0.10 cannot merge join 16+ aliases into single stage while hive 0.9 doesn't have such issue. could you explain this or give me some hint? Thanks! -- wzc19

回复： different outer join plan between hive 0.9 and hive 0.10

.key left outer join default.test_join z on a.key = z.key -- wzc1989 已使用 Sparrow (http://www.sparrowmailapp.com/?sig) 在 2013年3月29日星期五，上午9:34，Navis류승우 写道： > The problem is mixture of issues (HIVE-3411, HIVE-4209, HIVE-4212, > HIVE-3464) and still not completely fixed even in trunk. &