[
https://issues.apache.org/jira/browse/NIFI-4637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458308#comment-16458308
]
ASF GitHub Bot commented on NIFI-4637:
--------------------------------------
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/2518#discussion_r184911299
--- Diff:
nifi-nar-bundles/nifi-hbase-bundle/nifi-hbase-processors/src/main/java/org/apache/nifi/hbase/PutHBaseCell.java
---
@@ -82,6 +79,8 @@ protected PutFlowFile createPut(final ProcessSession
session, final ProcessConte
final String columnQualifier =
context.getProperty(COLUMN_QUALIFIER).evaluateAttributeExpressions(flowFile).getValue();
final String timestampValue =
context.getProperty(TIMESTAMP).evaluateAttributeExpressions(flowFile).getValue();
+ final String visibilityStringToUse =
pickVisibilityString(columnFamily, columnQualifier, flowFile, context);
--- End diff --
When I was configured the processor like below:
- Row Identifier: ${hbase.rowid}
- Column Family: ${hbase.column.family}
- Column Qualifier: ${hbase.column.qualifier}
I was looking for a property for visibility expression to specify EL
similarly, e.g. '${hbase.visibility}'. Currently, in order to add visibility, a
FlowFile must have an attribute named 'visibility.family.qualifier', or a
dynamic property is needed. I think I wanted to put the configuration directory
without adding a dynamic property. But it should be fine since we now have a
detailed docs. Thanks, no change is needed for the comment.
> Add support for HBase visibility labels to HBase processors and controller
> services
> -----------------------------------------------------------------------------------
>
> Key: NIFI-4637
> URL: https://issues.apache.org/jira/browse/NIFI-4637
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Mike Thomsen
> Assignee: Mike Thomsen
> Priority: Major
>
> HBase supports visibility labels, but you can't use them from NiFi because
> there is no way to set them. The existing processors and services should be
> upgraded to handle this capability.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
