James,
Hmmm. I'm not too familiar with DynamoDB or NiFi, but having a
processor that can only return one attribute at a time doesn't seem very
useful. I would think the processor would retrieve all the attributes
and package them into one variable and send it back as one unit so when
the user configures the processor they could do something like set the
json attribute value to "ALL" or something like that. I tried modifying
the processor source code to call item.getJSON() to populate the return
value with everything, but something isn't liking { brace in the string
value that gets sent back. Its complaining about unacceptable characters
in the string. I might need to swich to MongoDB as my datasource and see
if that works.
Thanks,
Mike
On 07/01/2016 02:41 AM, James Wing wrote:
Mike,
I believe it was an intentional design choice to separate the
hash/range keys from the flowfile content for validation and
handling. There is currently no option in PutDynamoDB or GetDynamoDB
to match the entire flowfile content to the entire DynamoDB item, but
I believe that is certainly a possible extension.
Thanks,
James
On Thu, Jun 30, 2016 at 9:57 AM, Mike Connolly
<mike.conno...@oracle.com <mailto:mike.conno...@oracle.com>> wrote:
I checked out the master branch of Nifi and noticed the
GetDynamoDB processor which was something I really needed for a
workflow. I tried using it to return the json representation of a
DynamoDB item. It looks like it will only return a json
representation of a a single attribute of a DynamoDB item. I'm
wondering it this was the intention or if there is a specific
value you need to set in the processor configuration that will
return the whole item. Anybody ever use this?
Thanks,
Mike Connolly