atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jon Maron <jma...@hortonworks.com>
Subject Re: Hive Hook property atlas.cluster.name
Date Fri, 28 Aug 2015 23:18:52 GMT



> On Aug 28, 2015, at 7:09 PM, Seetharam Venkatesh <venkatesh@innerzeal.com> wrote:
> 
> We use this as a namespace to avoid collisions from a DR site pushing the
> same set of metadata elements into Atlas.
> 
> If Ambari supported multiple clusters, we could have leaned on it. In the
> absence of such a feature, we are left with this kludge. We may not be able
> to default to a static string since it can apply to a DR site as well.

In that instance it seems a generated GUID per cluster would suffice?

> 
> Thanks!
> 
>> On Fri, Aug 28, 2015 at 10:45 AM Jon Maron <jmaron@hortonworks.com> wrote:
>> 
>> Hi,
>> 
>>  Can someone provide more insight into the ‘atlas.cluster.name’ property
>> and its usage?  It turns out that leveraging the Ambari cluster name could
>> be rather problematic since it can be changed and that change is not
>> necessarily conveyed to the cluster elements.  I am attempting to modify
>> the Ambari service code to leverage the stack advisor to affect the hive
>> changes required for configuring the Atlas hive hook, and in that instance
>> the Ambari cluster name isn’t even currently available.
>> 
>>  Is there another name envisioned for use in this scenario (other than
>> Ambari cluster name)?  Can a default value be leveraged for a given cluster
>> (‘primary’)?
>> 
>> — Jon
>> 
>> 

Mime
View raw message