Re: Alternatives to Streaming Mutation API in Hive 3.x

[Nandakishore Mm]

Here is some more context of what we are trying out. We have streaming
mutable data in kafka and we want to stream these upserts into Hive ( HDFS
backed) . I gather than hive  has a streaming interface through which
upserts can be streamed into Hive. Have u guys tested this and or done some
POC around this.
When we are trying to POC using the documents available online, the updated
data is not reflecting and multiple records are observed for the same key
when we issue a get.

So wanted to understand if some configuration is missing in our setup.

Here are the cluster details:
 Hadoop version : 2.9.0
 Hive version : 3.1.1

I have attached our sample code.

So following questions:
a) Is our approach not correct?
b) Are we missing any configuration?
c) Is our hadoop dependency in-correct?
d) Issue with the way we are invoking the code?
e) Any other approach that we should take?

Thanks & Regards
Nandakishore

On Wed, Jan 15, 2020 at 11:37 AM Nandakishore Mm <
nandakishore...@flipkart.com> wrote:

> Hi David,
>
> Thanks for the response.
> I'm actually trying to do streaming upserts into hive. Since we already
> use Hive to perform our analytics we are looking for solutions based around
> Hive itself. Also as you mentioned Hive 3.x for upserts, could you point me
> to something specific in Hive that enables this?
>
> On Mon, Jan 13, 2020 at 6:28 PM David Mollitor  wrote:
>
>> Hello,
>>
>> Streaming? NiFi
>>
>> Upserts? HBase, Kudu, Hive 3.x
>>
>> Doing upserts on Hive can be cumbersome, depending on the use case.  If
>> Upserts are being submitted continuously and quickly, it can overwhelm the
>> system because it will require a scan across the data set (for all intents
>> and purposes) for each query submission.
>>
>> On Mon, Jan 13, 2020, 5:56 AM Nandakishore Mm <
>> nandakishore...@flipkart.com> wrote:
>>
>>> Hi Hive Team,
>>> I have a use case where data has to be continuously streamed into a hive
>>> table as well as old records with the same primary key have to be
>>> updated/deleted (i.e. upserts). This document
>>> 
>>>  for
>>> 'HCatalog Streaming Mutation API' seems to be suitable for my use case but
>>> is deprecated from Hive 3 onwards. Is there any alternative for is feature
>>> or any other way to handle my use case with Hive?
>>>
>>> Thanks and Regards,
>>> Nandakishore MM
>>> Software Developer
>>> Flipkart
>>> Mobile : +91 9043412922
>>>
>>>
>>> --
>>> Nandakishore MM
>>> Mobile : +91 9043412922
>>>
>>>
>>> *-*
>>>
>>> *This email and any files transmitted with it are confidential and
>>> intended solely for the use of the individual or entity to whom they are
>>> addressed. If you have received this email in error, please notify the
>>> system manager. This message contains confidential information and is
>>> intended only for the individual named. If you are not the named addressee,
>>> you should not disseminate, distribute or copy this email. Please notify
>>> the sender immediately by email if you have received this email by mistake
>>> and delete this email from your system. If you are not the intended
>>> recipient, you are notified that disclosing, copying, distributing or
>>> taking any action in reliance on the contents of this information is
>>> strictly prohibited.*
>>>
>>>
>>>
>>> *Any views or opinions presented in this email are solely those of the
>>> author and do not necessarily represent those of the organization. Any
>>> information on shares, debentures or similar instruments, recommended
>>> product pricing, valuations and the like are for information purposes only.
>>> It is not meant to be an instruction or recommendation, as the case may be,
>>> to buy or to sell securities, products, services nor an offer to buy or
>>> sell securities, products or services unless specifically stated to be so
>>> on behalf of the Flipkart group. Employees of the Flipkart group of
>>> companies are expressly required not to make defamatory statements and not
>>> to infringe or authorise any infringement of copyright or any other legal
>>> right by email communications. Any such communication is contrary to
>>> organizational policy and outside the scope of the employment of the
>>> individual concerned. The organization will not accept any liability in
>>> respect of such communication, and the employee responsible will be
>>> personally liable for any damages or other liability arising.*
>>>
>>>
>>>
>>> *Our organization accepts no liability for the content of this email, or
>>> for the consequences of any actions taken on the basis of the information *
>>> provided,* unless that information is subsequently confirmed in
>>> writing. If you are not the intended recipient, you are notified that
>>> disclosing, copying, distributing or taking any action in reliance on the
>>> contents of this information is strictly 

?????? Alternatives to Streaming Mutation API in Hive 3.x

[????????]

You sent it to the wrong person


----
??:"Nandakishore Mm"

Re: Alternatives to Streaming Mutation API in Hive 3.x

[Nandakishore Mm]

Hi David,

Thanks for the response.
I'm actually trying to do streaming upserts into hive. Since we already use
Hive to perform our analytics we are looking for solutions based around
Hive itself. Also as you mentioned Hive 3.x for upserts, could you point me
to something specific in Hive that enables this?

On Mon, Jan 13, 2020 at 6:28 PM David Mollitor  wrote:

> Hello,
>
> Streaming? NiFi
>
> Upserts? HBase, Kudu, Hive 3.x
>
> Doing upserts on Hive can be cumbersome, depending on the use case.  If
> Upserts are being submitted continuously and quickly, it can overwhelm the
> system because it will require a scan across the data set (for all intents
> and purposes) for each query submission.
>
> On Mon, Jan 13, 2020, 5:56 AM Nandakishore Mm <
> nandakishore...@flipkart.com> wrote:
>
>> Hi Hive Team,
>> I have a use case where data has to be continuously streamed into a hive
>> table as well as old records with the same primary key have to be
>> updated/deleted (i.e. upserts). This document
>> 
>>  for
>> 'HCatalog Streaming Mutation API' seems to be suitable for my use case but
>> is deprecated from Hive 3 onwards. Is there any alternative for is feature
>> or any other way to handle my use case with Hive?
>>
>> Thanks and Regards,
>> Nandakishore MM
>> Software Developer
>> Flipkart
>> Mobile : +91 9043412922
>>
>>
>> --
>> Nandakishore MM
>> Mobile : +91 9043412922
>>
>>
>> *-*
>>
>> *This email and any files transmitted with it are confidential and
>> intended solely for the use of the individual or entity to whom they are
>> addressed. If you have received this email in error, please notify the
>> system manager. This message contains confidential information and is
>> intended only for the individual named. If you are not the named addressee,
>> you should not disseminate, distribute or copy this email. Please notify
>> the sender immediately by email if you have received this email by mistake
>> and delete this email from your system. If you are not the intended
>> recipient, you are notified that disclosing, copying, distributing or
>> taking any action in reliance on the contents of this information is
>> strictly prohibited.*
>>
>>
>>
>> *Any views or opinions presented in this email are solely those of the
>> author and do not necessarily represent those of the organization. Any
>> information on shares, debentures or similar instruments, recommended
>> product pricing, valuations and the like are for information purposes only.
>> It is not meant to be an instruction or recommendation, as the case may be,
>> to buy or to sell securities, products, services nor an offer to buy or
>> sell securities, products or services unless specifically stated to be so
>> on behalf of the Flipkart group. Employees of the Flipkart group of
>> companies are expressly required not to make defamatory statements and not
>> to infringe or authorise any infringement of copyright or any other legal
>> right by email communications. Any such communication is contrary to
>> organizational policy and outside the scope of the employment of the
>> individual concerned. The organization will not accept any liability in
>> respect of such communication, and the employee responsible will be
>> personally liable for any damages or other liability arising.*
>>
>>
>>
>> *Our organization accepts no liability for the content of this email, or
>> for the consequences of any actions taken on the basis of the information *
>> provided,* unless that information is subsequently confirmed in writing.
>> If you are not the intended recipient, you are notified that disclosing,
>> copying, distributing or taking any action in reliance on the contents of
>> this information is strictly prohibited.*
>>
>>
>> *-*
>>
>>

-- 
Nandakishore MM
Mobile : +91 9043412922

-- 



*-*


*This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify the 
system manager. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee, 
you should not disseminate, distribute or copy this email. Please notify 
the sender immediately by email if you have received this email by mistake 
and delete this email from your system. If you are not the intended 
recipient, you are notified that disclosing, copying, distributing or 
taking any action in reliance on the contents of this information is 
strictly prohibited.*

 

*Any views or opinions presented in this 
email are solely those of the author and 

Re: Alternatives to Streaming Mutation API in Hive 3.x

[David Mollitor]

Hello,

Streaming? NiFi

Upserts? HBase, Kudu, Hive 3.x

Doing upserts on Hive can be cumbersome, depending on the use case.  If
Upserts are being submitted continuously and quickly, it can overwhelm the
system because it will require a scan across the data set (for all intents
and purposes) for each query submission.

On Mon, Jan 13, 2020, 5:56 AM Nandakishore Mm 
wrote:

> Hi Hive Team,
> I have a use case where data has to be continuously streamed into a hive
> table as well as old records with the same primary key have to be
> updated/deleted (i.e. upserts). This document
> 
>  for
> 'HCatalog Streaming Mutation API' seems to be suitable for my use case but
> is deprecated from Hive 3 onwards. Is there any alternative for is feature
> or any other way to handle my use case with Hive?
>
> Thanks and Regards,
> Nandakishore MM
> Software Developer
> Flipkart
> Mobile : +91 9043412922
>
>
> --
> Nandakishore MM
> Mobile : +91 9043412922
>
>
> *-*
>
> *This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they are
> addressed. If you have received this email in error, please notify the
> system manager. This message contains confidential information and is
> intended only for the individual named. If you are not the named addressee,
> you should not disseminate, distribute or copy this email. Please notify
> the sender immediately by email if you have received this email by mistake
> and delete this email from your system. If you are not the intended
> recipient, you are notified that disclosing, copying, distributing or
> taking any action in reliance on the contents of this information is
> strictly prohibited.*
>
>
>
> *Any views or opinions presented in this email are solely those of the
> author and do not necessarily represent those of the organization. Any
> information on shares, debentures or similar instruments, recommended
> product pricing, valuations and the like are for information purposes only.
> It is not meant to be an instruction or recommendation, as the case may be,
> to buy or to sell securities, products, services nor an offer to buy or
> sell securities, products or services unless specifically stated to be so
> on behalf of the Flipkart group. Employees of the Flipkart group of
> companies are expressly required not to make defamatory statements and not
> to infringe or authorise any infringement of copyright or any other legal
> right by email communications. Any such communication is contrary to
> organizational policy and outside the scope of the employment of the
> individual concerned. The organization will not accept any liability in
> respect of such communication, and the employee responsible will be
> personally liable for any damages or other liability arising.*
>
>
>
> *Our organization accepts no liability for the content of this email, or
> for the consequences of any actions taken on the basis of the information *
> provided,* unless that information is subsequently confirmed in writing.
> If you are not the intended recipient, you are notified that disclosing,
> copying, distributing or taking any action in reliance on the contents of
> this information is strictly prohibited.*
>
>
> *-*
>
>

Fwd: Alternatives to Streaming Mutation API in Hive 3.x

[Nandakishore Mm]

Hi Hive Team,
I have a use case where data has to be continuously streamed into a hive
table as well as old records with the same primary key have to be
updated/deleted (i.e. upserts). This document

for
'HCatalog Streaming Mutation API' seems to be suitable for my use case but
is deprecated from Hive 3 onwards. Is there any alternative for is feature
or any other way to handle my use case with Hive?

Thanks and Regards,
Nandakishore MM
Software Developer
Flipkart
Mobile : +91 9043412922


-- 
Nandakishore MM
Mobile : +91 9043412922

-- 



*-*


*This email and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed. If you have received this email in error, please notify the 
system manager. This message contains confidential information and is 
intended only for the individual named. If you are not the named addressee, 
you should not disseminate, distribute or copy this email. Please notify 
the sender immediately by email if you have received this email by mistake 
and delete this email from your system. If you are not the intended 
recipient, you are notified that disclosing, copying, distributing or 
taking any action in reliance on the contents of this information is 
strictly prohibited.*

 

*Any views or opinions presented in this 
email are solely those of the author and do not necessarily represent those 
of the organization. Any information on shares, debentures or similar 
instruments, recommended product pricing, valuations and the like are for 
information purposes only. It is not meant to be an instruction or 
recommendation, as the case may be, to buy or to sell securities, products, 
services nor an offer to buy or sell securities, products or services 
unless specifically stated to be so on behalf of the Flipkart group. 
Employees of the Flipkart group of companies are expressly required not to 
make defamatory statements and not to infringe or authorise any 
infringement of copyright or any other legal right by email communications. 
Any such communication is contrary to organizational policy and outside the 
scope of the employment of the individual concerned. The organization will 
not accept any liability in respect of such communication, and the employee 
responsible will be personally liable for any damages or other liability 
arising.*

 

*Our organization accepts no liability for the 
content of this email, or for the consequences of any actions taken on the 
basis of the information *provided,* unless that information is 
subsequently confirmed in writing. If you are not the intended recipient, 
you are notified that disclosing, copying, distributing or taking any 
action in reliance on the contents of this information is strictly 
prohibited.*


_-_