[ 
https://issues.apache.org/jira/browse/NIFI-4543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Koji Kawamura updated NIFI-4543:
--------------------------------
    Description: 
HBase related processors report NiFi provenance events with transit URLs in a 
format as 'hbase://tablename/rowid'. However, the URL is not descriptive enough 
if a NiFi interacts with multiple HBase clusters having the same table names.

HBase processors transit URL should include host information it operates with, 
so that an URL can identify a HBase cluster.

Target Processors:
* FetchHBaseRow
* GetHBase
* PutHBaseCell
* PutHBaseJSON
* PutHBaseRecord

  was:
HBase related processors reports NiFi provenance events with transit URLs in a 
format as 'hbase://tablename/rowid'. However, the URL is not descriptive enough 
if a NiFi interacts with multiple HBase clusters having the same table names.

HBase processors transit URL should include host information it operates with, 
so that an URL can identify a HBase cluster.

Target Processors:
* FetchHBaseRow
* GetHBase
* PutHBaseCell
* PutHBaseJSON
* PutHBaseRecord


> Improve HBase processors provenance transit URL
> -----------------------------------------------
>
>                 Key: NIFI-4543
>                 URL: https://issues.apache.org/jira/browse/NIFI-4543
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Koji Kawamura
>            Assignee: Koji Kawamura
>
> HBase related processors report NiFi provenance events with transit URLs in a 
> format as 'hbase://tablename/rowid'. However, the URL is not descriptive 
> enough if a NiFi interacts with multiple HBase clusters having the same table 
> names.
> HBase processors transit URL should include host information it operates 
> with, so that an URL can identify a HBase cluster.
> Target Processors:
> * FetchHBaseRow
> * GetHBase
> * PutHBaseCell
> * PutHBaseJSON
> * PutHBaseRecord



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to