Owen O'Malley created HIVE-10798:
Summary: Remove dependence on VectorizedBatchUtil from
VectorizedOrcAcidRowReader
Key: HIVE-10798
URL: https://issues.apache.org/jira/browse/HIVE-10798
Project: Hive
On May 21, 2015, 7:18 p.m., Sergio Pena wrote:
ql/src/java/org/apache/hadoop/hive/ql/io/parquet/MapredParquetOutputFormat.java,
line 59
https://reviews.apache.org/r/34473/diff/2/?file=966160#file966160line59
Could you separate words with _? Like ENABLE_ACID_SCHEMA_INFO. It helps
Owen O'Malley created HIVE-10796:
Summary: Remove dependencies on NumericHistogram and
NumDistinctValueEstimator from JavaDataModel
Key: HIVE-10796
URL: https://issues.apache.org/jira/browse/HIVE-10796
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34473/
---
(Updated May 22, 2015, 6:26 a.m.)
Review request for hive, Alan Gates, Owen
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34455/#review84876
---
ql/src/java/org/apache/hadoop/hive/ql/exec/spark/ReduceTran.java
Owen O'Malley created HIVE-10797:
Summary: Simplify the test for vectorized input
Key: HIVE-10797
URL: https://issues.apache.org/jira/browse/HIVE-10797
Project: Hive
Issue Type: Sub-task
Owen O'Malley created HIVE-10795:
Summary: Remove use of PerfLogger from Orc
Key: HIVE-10795
URL: https://issues.apache.org/jira/browse/HIVE-10795
Project: Hive
Issue Type: Sub-task
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34455/
---
(Updated May 22, 2015, 6:18 a.m.)
Review request for hive, Chao Sun, Jimmy
Owen O'Malley created HIVE-10799:
Summary: Refactor the SearchArgumentFactory to remove the
dependence on ExprNodeGenericFuncDesc
Key: HIVE-10799
URL: https://issues.apache.org/jira/browse/HIVE-10799
I understand the motivation and benefits of creating a branch-2 where more
disruptive work can go on without affecting branch-1. While not necessarily
against this approach, from Yahoo's standpoint, I do have some questions
(concerns).
Upgrading to a new version of Hive requires a significant
On Fri, May 22, 2015 at 1:19 PM, Alan Gates alanfga...@gmail.com wrote:
I see your point on saying the contributor may not understand where best
to put the patch, and thus the committer decides. However, it would be
very disappointing for a contributor who uses branch-1 to build a new
Pengcheng Xiong created HIVE-10804:
--
Summary: CBO: Calcite Operator To Hive Operator (Calcite Return
Path): optimizer for limit 0 does not work
Key: HIVE-10804
URL:
I agree with *All* features with the exception that some features might
be branch-1 specific (if it's a feature on something no longer supported
in master, like hadoop-1). Without this we prevent new features for
older technology, which doesn't strike me as reasonable.
I see your point on
Aihua Xu created HIVE-10802:
---
Summary: Table join query with some constant field in select fails
Key: HIVE-10802
URL: https://issues.apache.org/jira/browse/HIVE-10802
Project: Hive
Issue Type: Bug
Thejas M Nair created HIVE-10803:
Summary: document jdbc url format properly
Key: HIVE-10803
URL: https://issues.apache.org/jira/browse/HIVE-10803
Project: Hive
Issue Type: Bug
Matt McCline created HIVE-10805:
---
Summary: OOM in vectorized reduce
Key: HIVE-10805
URL: https://issues.apache.org/jira/browse/HIVE-10805
Project: Hive
Issue Type: Bug
Reporter:
anup b created HIVE-10806:
-
Summary: Incorrect example for exploding map function in hive wiki
Key: HIVE-10806
URL: https://issues.apache.org/jira/browse/HIVE-10806
Project: Hive
Issue Type: Bug
Selina Zhang created HIVE-10809:
---
Summary: HCat FileOutputCommitterContainer leaves behind empty
_SCRATCH directories
Key: HIVE-10809
URL: https://issues.apache.org/jira/browse/HIVE-10809
Project: Hive
Naveen Gangam created HIVE-10808:
Summary: Inner join on Null throwing Cast Exception
Key: HIVE-10808
URL: https://issues.apache.org/jira/browse/HIVE-10808
Project: Hive
Issue Type: Bug
Ashutosh Chauhan created HIVE-10807:
---
Summary: Invalidate basic stats for insert queries if
autogather=false
Key: HIVE-10807
URL: https://issues.apache.org/jira/browse/HIVE-10807
Project: Hive
Hari Sankar Sivarama Subramaniyan created HIVE-10801:
Summary: 'drop view' fails throwing java.lang.NullPointerException
Key: HIVE-10801
URL: https://issues.apache.org/jira/browse/HIVE-10801
See
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/HIVE-TRUNK-JAVA8/72/
--
Started by timer
Building in workspace
http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/job/HIVE-TRUNK-JAVA8/ws/
git rev-parse --is-inside-work-tree #
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34593/
---
(Updated May 22, 2015, 11:57 a.m.)
Review request for hive.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/34593/
---
Review request for hive.
Repository: hive-git
Description
---
Jesus Camacho Rodriguez created HIVE-10800:
--
Summary: CBO (Calcite Return Path): Setup correct information if
CBO succeeds
Key: HIVE-10800
URL: https://issues.apache.org/jira/browse/HIVE-10800
I think branch-2 doesn’t need to be framed as particularly adventurous
(other than due to general increase of the amount of work done in Hive by
community).
All the new features that normally go on trunk/master will go to branch-2.
branch-2 is just trunk as it is now, in fact there will be no
+1 on the new proposal. Feedback below:
New features must be put into master. Whether to put them into branch-1
is at the discretion of the developer.
How about we change this to *All* features must be put into master.
Whether to put them into branch-1 is at the discretion of the *committer*.
Looks like we discussing 3 options:
1. Support hadoop 1, 2 and 3 in master branch.
2. Support hadoop 1 in branch-1, hadoop 2 in branch-2, hadoop 3 in branch-3
3. Support hadoop 2 and 3 in master
I DO not think option 2 is good solution because it is much more difficuilt
to manage 3 active prod
Alan, your email client is not compatible with gmail viewer. For some
reason your reply contains the whole thread of the discussion
On May 22, 2015 10:58 AM, Alan Gates alanfga...@gmail.com wrote:
I don't think anyone is advocating for option 2, as that would be
disastrous. Option 3 is closest
I don't think anyone is advocating for option 2, as that would be
disastrous. Option 3 is closest to what I'm proposing, though again
dropping support for Hadoop 1 is only a part of it.
Alan.
Alexander Pivovarov mailto:apivova...@gmail.com
May 22, 2015 at 10:03
Looks like we discussing 3
Thanks for your feedback Chris. It sounds like there are a couple of
reasonable concerns being voiced repeatedly:
1) Fragmentation, the two branches will drift too far apart.
2) Stagnation, branch-1 will effectively become a dead-end.
So I modify the proposal as follows to deal with those:
1)
31 matches
Mail list logo
