Sergey's idea is creative, although it leads to confusion about JIRA fix
versions. Issues would be given fix versions based on assumptions about
whether SA or Hive will be released first. (That's hard to predict when
it's months away.)
Keeping the version numbers tied together is very appealing.
Harsh J created HIVE-14593:
--
Summary: Non-canonical integer partition columns do not work with
IN operations
Key: HIVE-14593
URL: https://issues.apache.org/jira/browse/HIVE-14593
Project: Hive
Issu
I am suggesting we always skip the number. So only one component gets the
next one :) In your example Hive trunk would be 2.3, and if SA is released
again it would become 2.4. Otherwise we’d need a compat table cause
versions will be totally out of sync.
On 16/8/19, 16:31, "Owen O'Malley" wrote:
Kapil Rastogi created HIVE-14592:
Summary: In LDAP authentication 'group filter' match should be
case insensitive
Key: HIVE-14592
URL: https://issues.apache.org/jira/browse/HIVE-14592
Project: Hive
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51046/
---
(Updated Aug. 19, 2016, 11:58 p.m.)
Review request for hive and Ashutosh Chauha
Tao Li created HIVE-14591:
-
Summary: HS2 is shut down unexpectedly during the startup time
Key: HIVE-14591
URL: https://issues.apache.org/jira/browse/HIVE-14591
Project: Hive
Issue Type: Bug
That won't necessarily work, especially in the beginning. If we release SA
2.2.0 and use it for Hive trunk with the assumption that the next Hive
release will be 2.2. What do we do when we need to make an incompatible
change in SA? I guess we could release SA as 2.3.0 and when hive makes its
next r
Can we just run the versions thru? I.e. increment it every time but
release only one component (or both if they happen to align I guess).
E.g. storage-api will be released at 2.2, and say 2.3 if it moves fast,
then Hive 2.4, then storage-api 2.5, etc.
That might make it easier to reason about compa
Ashutosh Chauhan created HIVE-14590:
---
Summary: CBO (Calcite Return Path) Incorrect result set when limit
is present in one of the union branches
Key: HIVE-14590
URL: https://issues.apache.org/jira/browse/HIVE-14
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51251/#review146226
---
Ship it!
Ship It!
- Sergio Pena
On Aug. 19, 2016, 8:50 p.m.,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51251/
---
(Updated Aug. 19, 2016, 8:50 p.m.)
Review request for hive and Sergio Pena.
R
Sergey Shelukhin created HIVE-14589:
---
Summary: add consistent node replacement to LLAP for splits
Key: HIVE-14589
URL: https://issues.apache.org/jira/browse/HIVE-14589
Project: Hive
Issue T
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51251/#review146215
---
common/src/java/org/apache/hadoop/hive/conf/HiveConf.java (line 3
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51251/
---
(Updated Aug. 19, 2016, 8:13 p.m.)
Review request for hive and Sergio Pena.
R
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/51251/
---
Review request for hive and Sergio Pena.
Repository: hive-git
Description
---
Gabor Szadovszky created HIVE-14588:
---
Summary: Add S3 credentials to the hidden configuration variable
supported on HIVE-14207
Key: HIVE-14588
URL: https://issues.apache.org/jira/browse/HIVE-14588
P
Jesus Camacho Rodriguez created HIVE-14587:
--
Summary: Support for average post-aggregation in Druid
Key: HIVE-14587
URL: https://issues.apache.org/jira/browse/HIVE-14587
Project: Hive
Amit Pathak created HIVE-14586:
--
Summary: Hive : with multi insert query: FAILED: SemanticException
Should not happened
Key: HIVE-14586
URL: https://issues.apache.org/jira/browse/HIVE-14586
Project: Hive
GitHub user prasanthj opened a pull request:
https://github.com/apache/hive/pull/97
HIVE-14585: Add travis.yml and update README to show build status
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/prasanthj/hive HIVE-14585
Alte
I see Parquet is currently using the SearchArgument class for predicates
push down.
Will this class be part of the new sub-module or project?
Following Sushanth idea, can we have other API interfaces in the new
project that other components can use?
Perhaps having this may be a good reason to crea
Prasanth Jayachandran created HIVE-14585:
Summary: Add travis.yml to show build status in github
Key: HIVE-14585
URL: https://issues.apache.org/jira/browse/HIVE-14585
Project: Hive
Is
Prasanth Jayachandran created HIVE-14584:
Summary: Pass Context to Orc tree readers
Key: HIVE-14584
URL: https://issues.apache.org/jira/browse/HIVE-14584
Project: Hive
Issue Type: Imp
22 matches
Mail list logo