Thank you all for the help. I'm preparing the patch for reviewing.
秦凯捷
Tel: +86-13810485829
E-mail: daniel...@gmail.com
On Tue, Dec 19, 2017 at 12:49 AM, Eugene Koifman
wrote:
> +1 to Alex’ comment
>
> On 12/14/17, 3:27 PM, "Alexander Kolbasov" wrote:
>
> Kaijie,
>
> can you describe
+1 to Alex’ comment
On 12/14/17, 3:27 PM, "Alexander Kolbasov" wrote:
Kaijie,
can you describe in more details why would you need such functionality?
What problem does it actually solve?
I do not think that HMS should do more "atomic" compound operations then it
doe
Thanks Kaijie.
One concern is that the new functions effectively expand the size of the
transactions and the work that must be undone if they fail. So the question
is whether the benefit is large enough to justify adding complexity.
If no-one else has comments then you should probably think about
Kaijie,
can you describe in more details why would you need such functionality?
What problem does it actually solve?
I do not think that HMS should do more "atomic" compound operations then it
does now - IMO it should do less instead. This is especially the case when
operations involve a mix of m
Hi Andrew,
Thanks for you response. For your comments:
-Functionality:
Support adding and altering multiple partitions for multiple tables in one
SQL and API request as one transaction.
- what happens in the case of a failure when part way through the
operations.
For altering and adding partitio
Hi Kaijie,
I think this is an area that other the Hive community is interested in. So
please do go ahead and describe your functionality.
I think that it is important to describe
- what happens in the case of a failure when part way through the
operations.
- what impact on the system there will be
Hi dev,
I'm wondering if Hive community have ever considered support adding and
altering multiple partitions for multiple tables?
I'm using Hive Metastore to manage the metadata for Presto querying. Our
business requires that we should publish some partitions of data for
multiple tables at the sa
