[
https://issues.apache.org/jira/browse/NIFI-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamas Palfy updated NIFI-7280:
------------------------------
Description:
{{ReportLineageToAtlas}} has the {{Atlas Default Cluster Name}} property which
sets a namespace within Atlas under which the reporting artifacts will be
grouped together.
This (for historical reasons probably) was usually the name of the Atlas
cluster and the NiFi property can be initialised from the Atlas config property
{{atlas.cluster.name}}. The concept cleared up a bit since and Atlas can have a
new corresponding property in it's config file: {{atlas.metadata.namespace}}.
The {{Atlas Default Cluster Name}} NiFi property should be able to handle this
new Atlas config property.
We also want to remain backward compatible so we should still recognise
{{atlas.cluster.name}} if the new {{atlas.metadata.namespace}} is not set.
was:
{{ReportLineageToAtlas}} has the {{Atlas Default Cluster Name}} property which
sets a namespace within Atlas under which the reporting artifacts will be
grouped together.
This (for historical reasons probably) was usually the name of the Atlas
cluster, but the concept cleared up a bit and Atlas can have a new
corresponding property in it's config file: {{atlas.metadata.namespace}}.
The {{Atlas Default Cluster Name}} NiFi property should be able to handle this
new Atlas config property.
We also want to remain backward compatible so we should still recognise
{{atlas.default.clustername}} if the new {{atlas.metadata.namespace}} is not
set.
> Use Atlas metadata namespace in Atlas Reporting Task
> ----------------------------------------------------
>
> Key: NIFI-7280
> URL: https://issues.apache.org/jira/browse/NIFI-7280
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Tamas Palfy
> Priority: Major
>
> {{ReportLineageToAtlas}} has the {{Atlas Default Cluster Name}} property
> which sets a namespace within Atlas under which the reporting artifacts will
> be grouped together.
> This (for historical reasons probably) was usually the name of the Atlas
> cluster and the NiFi property can be initialised from the Atlas config
> property {{atlas.cluster.name}}. The concept cleared up a bit since and Atlas
> can have a new corresponding property in it's config file:
> {{atlas.metadata.namespace}}.
> The {{Atlas Default Cluster Name}} NiFi property should be able to handle
> this new Atlas config property.
> We also want to remain backward compatible so we should still recognise
> {{atlas.cluster.name}} if the new {{atlas.metadata.namespace}} is not set.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
