---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44783/#review123610
---
Ship it!
Ship It!
- Amareshwari Sriramadasu
On March 15, 201
Jesus Camacho Rodriguez created HIVE-13287:
--
Summary: Add logic to estimate stats for IN operator
Key: HIVE-13287
URL: https://issues.apache.org/jira/browse/HIVE-13287
Project: Hive
Jeff Zhang created HIVE-13288:
-
Summary: Confusing exception message in DagUtils.localizeResource
Key: HIVE-13288
URL: https://issues.apache.org/jira/browse/HIVE-13288
Project: Hive
Issue Type: I
Andy Rosa created HIVE-13289:
Summary: LazyBinaryColumnarSerDe: 0 length VARCHAR values are
serialized as NULL
Key: HIVE-13289
URL: https://issues.apache.org/jira/browse/HIVE-13289
Project: Hive
Hi Team,
I have a query where I am joining with 10 other entities
Like
Select a.col1,b1.col1,b2.col1 from
A a
Left outer join b1 on
Left outer join b2 on
Left outer join b3….
A is my driver entity which a 20 million data. Most of the other entities
are small just 10 to 20 rows
You can think of map joins.If cluster is configured by default it must be
happening already check query profile
On Tue, 15 Mar 2016 21:12 Himabindu sanka,
wrote:
> Hi Team,
>
>
>
> I have a query where I am joining with 10 other entities
>
>
>
> Like
>
>
>
> Select a.col1,b1.col1,b2.col1 from
>
Hari Sankar Sivarama Subramaniyan created HIVE-13290:
Summary: Support primary keys/foreign keys constraint as part of
create table command in Hive
Key: HIVE-13290
URL: https://issues.apache.or
As suggested, looking at the explain plan should tell you if map-join
is getting used.
Using a recent version with hive-on-tez would also give you further
speedup as map-joins are optimized further in it.
On Tue, Mar 15, 2016 at 9:32 AM, sreebalineni . wrote:
> You can think of map joins.If clus
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/44756/#review123813
---
ql/src/java/org/apache/hadoop/hive/ql/parse/SemanticAnalyzer.java
There seems to be increasing interest in supporting MariaDB as an
option for storing metastore metadata. Supporting it as a database
option is also easy as it is compatible with mysql. I thought it would
be useful to discuss supporting it in the dev list before creating any
jiras.
There are two as
Prasanth Jayachandran created HIVE-13291:
Summary: ORC BI Split strategy should consider block size instead
of file size
Key: HIVE-13291
URL: https://issues.apache.org/jira/browse/HIVE-13291
P
Xin Hao created HIVE-13292:
--
Summary: Different DOUBLE type precision issue between Spark and
MR engine
Key: HIVE-13292
URL: https://issues.apache.org/jira/browse/HIVE-13292
Project: Hive
Issue Typ
Lifeng Wang created HIVE-13293:
--
Summary: Query occurs performance degradation after enabling
parallel order by for Hive on sprak
Key: HIVE-13293
URL: https://issues.apache.org/jira/browse/HIVE-13293
Pro
13 matches
Mail list logo