+1
On Jun 30, 2017 17:05, "Owen O'Malley" wrote:
> On Fri, Jun 30, 2017 at 3:26 PM, Chao Sun wrote:
>
> > and maybe a different project name?
> >
>
> Yes, it certainly needs a new name. I'd like to suggest Riven.
>
> .. Owen
>
Timothy Miron created HIVE-17009:
Summary: ifnull() compatibility with explain or use of constants
Key: HIVE-17009
URL: https://issues.apache.org/jira/browse/HIVE-17009
Project: Hive
Issue Ty
Dan Burkert created HIVE-17008:
--
Summary: HiveMetastore.drop_database can return NPE if database
does not exist
Key: HIVE-17008
URL: https://issues.apache.org/jira/browse/HIVE-17008
Project: Hive
On Fri, Jun 30, 2017 at 3:26 PM, Chao Sun wrote:
> and maybe a different project name?
>
Yes, it certainly needs a new name. I'd like to suggest Riven.
.. Owen
Daniel Dai created HIVE-17007:
-
Summary: NPE introduced by HIVE-16871
Key: HIVE-17007
URL: https://issues.apache.org/jira/browse/HIVE-17007
Project: Hive
Issue Type: Bug
Components: Met
Yeah, this is good idea. +1
On Fri, Jun 30, 2017 at 3:26 PM, Chao Sun wrote:
> HMS has become the shared catalog service for multiple projects outside
> Hive,
> so +1 on this move (and maybe a different project name?).
>
> On Fri, Jun 30, 2017 at 2:10 PM, Owen O'Malley
> wrote:
>
>> I'm +1 on se
HMS has become the shared catalog service for multiple projects outside
Hive,
so +1 on this move (and maybe a different project name?).
On Fri, Jun 30, 2017 at 2:10 PM, Owen O'Malley
wrote:
> I'm +1 on separating out the metastore. It recognizes the reality that a
> lot of different projects use
Sergey Shelukhin created HIVE-17006:
---
Summary: LLAP: Parquet caching
Key: HIVE-17006
URL: https://issues.apache.org/jira/browse/HIVE-17006
Project: Hive
Issue Type: Bug
Reporter
I'm +1 on separating out the metastore. It recognizes the reality that a
lot of different projects use the Hive Metastore and opening up the
community is a great move.
..Owen
On Fri, Jun 30, 2017 at 1:30 PM, Xuefu Zhang wrote:
> +1, sounds like a good idea!
>
> On Fri, Jun 30, 2017 at 1:24 PM,
Sushanth Sowmyan created HIVE-17005:
---
Summary: Ensure REPL DUMP and REPL LOAD are authorized properly
Key: HIVE-17005
URL: https://issues.apache.org/jira/browse/HIVE-17005
Project: Hive
Iss
BELUGA BEHR created HIVE-17004:
--
Summary: Calculating Number Of Reducers Looks At All Files
Key: HIVE-17004
URL: https://issues.apache.org/jira/browse/HIVE-17004
Project: Hive
Issue Type: Improv
+1, sounds like a good idea!
On Fri, Jun 30, 2017 at 1:24 PM, Harsha wrote:
> Thanks for the proposal Alan. I am +1 on separating the Hive Metastore.
> This is a great opportunity for building a Metastore to not only address
> schemas for the data at rest but also for the data in motion. We have
Thanks for the proposal Alan. I am +1 on separating the Hive Metastore.
This is a great opportunity for building a Metastore to not only address
schemas for the data at rest but also for the data in motion. We have a
SchemaRegistry (http://github.com/hortonworks/registry) project that
allows users
Great, thanks Alan for putting all this in the email.
+1
Allowing other components to continue to use the Metastore without the need
to use Hive dependencies is a big plus for them. I agree with everything
you mention on the email.
- Sergio
On Fri, Jun 30, 2017 at 1:49 PM, Julian Hyde wrote:
>
+1
As a Calcite PMC member, I am very pleased to see this change. Calcite reads
metadata from a variety of sources (including JDBC databases, NoSQL databases
such as Cassandra and Druid, and streaming systems), and if more of those
sources choose to store their metadata in the metastore it will
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60259/
---
(Updated June 30, 2017, 6:07 p.m.)
Review request for hive, Sergey Shelukhin an
On 2017-06-30 07:56 (-0700), Alan Gates wrote:
> A few of us have been talking and come to the conclussion that it would be
> a good thing to split out the Hive metastore into its own Apache project.
> Below and in the linked wiki page we explain what we see as the advantages
> to this and how
Pau Tallada Crespí created HIVE-17003:
-
Summary: WebHCat Hive jobs lost progress info since
HIVE_CLI_SERVICE_PROTOCOL_V10
Key: HIVE-17003
URL: https://issues.apache.org/jira/browse/HIVE-17003
Proj
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60445/#review179380
---
Ship it!
Ship It!
- Peter Vary
On June 30, 2017, 4:18 p.m.,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60445/
---
(Updated June 30, 2017, 4:18 p.m.)
Review request for hive and Sahil Takiar.
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/60445/#review179369
---
Thanks for the fast update! LGTM, just one little nit :)
Peter
A few of us have been talking and come to the conclussion that it would be
a good thing to split out the Hive metastore into its own Apache project.
Below and in the linked wiki page we explain what we see as the advantages
to this and how we would go about it.
Hive’s metastore has long been used
Artur Tamazian created HIVE-17002:
-
Summary: decimal (binary) is not working when creating external
table for hbase
Key: HIVE-17002
URL: https://issues.apache.org/jira/browse/HIVE-17002
Project: Hive
Barna Zsombor Klara created HIVE-17001:
--
Summary: Insert overwrite table doesn't clean partition directory
on HDFS if partition is missing from HMS
Key: HIVE-17001
URL: https://issues.apache.org/jira/browse/H
Hi,
HIVE-10790 (
https://issues.apache.org/jira/secure/attachment/12739023/HIVE-10790.0.patch.txt)
fixed an issue where files could not be written on a federated cluster in
Hive 1.0 (and subsequent versions). Libraries that depend on Hive 1.0,
therefore, cannot write to a federated cluster because
25 matches
Mail list logo