[
https://issues.apache.org/jira/browse/NIFI-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15121693#comment-15121693
]
Joseph Percivall commented on NIFI-1382:
----------------------------------------
I appreciate the review Bryan, here are responses to each point:
* I went back and forth on this. I believe I decided to leave it out because I
noticed PutDistributedMapCache only serialized to UTF_8. Looking again I
believe I misinterpreted that and we should in fact have a char set property.
will add
* For other processors that I have done that output to an attribute I've used a
length as well. I believe it's much easier for the user to think about the
length of a string in terms of number of characters instead of data size.
Keeping as a length.
* Last I did a work-flow like this (put to attribute or content), I got the
feedback to make it one attribute. This eliminates having a property which is
completely ignored in at least 50% of the cases. Once we have dependent
properties I am 100% for having it split into two properties. Gonna keep as two
properties unless if you have strong feelings it shouldn't be.
* Definitely agree, will add
* I believe you're right, will remove
Thanks again!
> Create GetDistributedMapCache Processor
> ---------------------------------------
>
> Key: NIFI-1382
> URL: https://issues.apache.org/jira/browse/NIFI-1382
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
> Fix For: 0.5.0
>
> Attachments:
> 0001-NIFI-1382-Created-GetDistributeMapCache-processor.patch
>
>
> Currently there is a PutDistributedMapCache processor but no way to get that
> information back out. There needs to be analogous processor, a
> GetDistributedMapCache processor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
