[
https://issues.apache.org/jira/browse/NIFI-4867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-4867:
--------------------------------
Description:
The change introduced in #4866 caches the identity of the HBase master. It
should have a configurable refresh period where the client verifies that the
master has not changed, and if it has, changes the information cached so
provenance can stay up to date.
Also, it may be useful if HBase ClusterId is reported to NiFi provenance event
somehow, by a FlowFile attribute, or a query parameter of transit URI. As
ClusterId will remain consistent while master address can change overtime.
was:The change introduced in #4866 caches the identity of the HBase master.
It should have a configurable refresh period where the client verifies that the
master has not changed, and if it has, changes the information cached so
provenance can stay up to date.
> Have HBase Client Service periodically poll the HBase cluster for the
> master's identity
> ---------------------------------------------------------------------------------------
>
> Key: NIFI-4867
> URL: https://issues.apache.org/jira/browse/NIFI-4867
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Priority: Major
>
> The change introduced in #4866 caches the identity of the HBase master. It
> should have a configurable refresh period where the client verifies that the
> master has not changed, and if it has, changes the information cached so
> provenance can stay up to date.
> Also, it may be useful if HBase ClusterId is reported to NiFi provenance
> event somehow, by a FlowFile attribute, or a query parameter of transit URI.
> As ClusterId will remain consistent while master address can change overtime.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
