nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mans2singh <>
Subject [GitHub] nifi pull request: Nifi 1516 - AWS DynamoDB Get/Put/Delete Process...
Date Mon, 15 Feb 2016 23:19:46 GMT
GitHub user mans2singh opened a pull request:

    Nifi 1516 - AWS DynamoDB Get/Put/Delete Processors

    The current implementation supports string and numbers for hash and range keys.  For put
operations, a json document can be inserted to a specified field and for get the the json
attribute can be retrieved from the item.

You can merge this pull request into a Git repository by running:

    $ git pull Nifi-1516

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #224
commit a68f85f0324f2182f6a29dbfec64ffc60ba18422
Author: mans2singh <>
Date:   2016-02-15T06:53:52Z

    Support for nifi dynamodb get/put/delete

commit e08df1040e606e1f23581f02fe50159a2105f9dc
Author: mans2singh <>
Date:   2016-02-15T19:42:51Z

    code refactoring and added test cases

commit a8a292e7497211a374106c62f1d08539f301a545
Author: mans2singh <>
Date:   2016-02-15T19:47:17Z

    contrib related formatting corrections

commit a05d3d08d4fd292f5b0d25959089ee220f7d3f0f
Author: mans2singh <>
Date:   2016-02-15T22:37:50Z

    code refactoring and tests

commit 1b91025d1f9b246ded50f3f55aa8cdbd59a1a109
Author: mans2singh <>
Date:   2016-02-15T22:47:45Z

    update test cases

commit 56fc5eeadb49d83dc702bcd27a88de325e115544
Author: mans2singh <>
Date:   2016-02-15T23:07:00Z

    contrib related error correction

commit d506058f24b737a48f5e7d19258c414e6873385b
Author: mans2singh <>
Date:   2016-02-15T23:17:10Z

    ignore integration tests


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message