You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by Mich Talebzadeh <mi...@gmail.com> on 2018/07/05 18:49:25 UTC
Hive Metada as a microservice
Hi,
My understanding is that in later releases of Hive, the metadata will be a
separate offerings. Will this be a type of microservice offering providing
loose coupling to various other artefact?
Thanks
Dr Mich Talebzadeh
LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
http://talebzadehmich.wordpress.com
*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
Re: Hive Metada as a microservice
Posted by Mich Talebzadeh <mi...@gmail.com>.
Thanks
I believe we can classify it as a microservice as it provides metadata
service for various other artefacts and it falls into the definition of loosely
coupled service.
HTH
Dr Mich Talebzadeh
LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
<https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
http://talebzadehmich.wordpress.com
*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.
On Thu, 5 Jul 2018 at 20:14, Alan Gates <al...@gmail.com> wrote:
> In 3.0, you can download the metastore as a separate artifact, either
> source or binary (e.g.
> http://ftp.wayne.edu/apache/hive/hive-standalone-metastore-3.0.0/). It
> does not require any other parts of Hive beyond what's released in that
> artifact. I'm not sure if this meets your definition of a loosely coupled
> microservice or not.
>
> Alan.
>
> On Thu, Jul 5, 2018 at 11:49 AM Mich Talebzadeh <mi...@gmail.com>
> wrote:
>
>> Hi,
>>
>> My understanding is that in later releases of Hive, the metadata will be
>> a separate offerings. Will this be a type of microservice offering
>> providing loose coupling to various other artefact?
>>
>> Thanks
>>
>> Dr Mich Talebzadeh
>>
>>
>>
>> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
>> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>>
>>
>>
>> http://talebzadehmich.wordpress.com
>>
>>
>> *Disclaimer:* Use it at your own risk. Any and all responsibility for
>> any loss, damage or destruction of data or any other property which may
>> arise from relying on this email's technical content is explicitly
>> disclaimed. The author will in no case be liable for any monetary damages
>> arising from such loss, damage or destruction.
>>
>>
>>
>
Re: Hive Metada as a microservice
Posted by Alan Gates <al...@gmail.com>.
In 3.0, you can download the metastore as a separate artifact, either
source or binary (e.g.
http://ftp.wayne.edu/apache/hive/hive-standalone-metastore-3.0.0/). It
does not require any other parts of Hive beyond what's released in that
artifact. I'm not sure if this meets your definition of a loosely coupled
microservice or not.
Alan.
On Thu, Jul 5, 2018 at 11:49 AM Mich Talebzadeh <mi...@gmail.com>
wrote:
> Hi,
>
> My understanding is that in later releases of Hive, the metadata will be a
> separate offerings. Will this be a type of microservice offering providing
> loose coupling to various other artefact?
>
> Thanks
>
> Dr Mich Talebzadeh
>
>
>
> LinkedIn * https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw
> <https://www.linkedin.com/profile/view?id=AAEAAAAWh2gBxianrbJd6zP6AcPCCdOABUrV8Pw>*
>
>
>
> http://talebzadehmich.wordpress.com
>
>
> *Disclaimer:* Use it at your own risk. Any and all responsibility for any
> loss, damage or destruction of data or any other property which may arise
> from relying on this email's technical content is explicitly disclaimed.
> The author will in no case be liable for any monetary damages arising from
> such loss, damage or destruction.
>
>
>