You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "James Wing (JIRA)" <ji...@apache.org> on 2016/11/04 05:16:58 UTC
[jira] [Updated] (NIFI-2948) AWS DynamoDB Processors Do Not Update
Credentials
[ https://issues.apache.org/jira/browse/NIFI-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Wing updated NIFI-2948:
-----------------------------
Status: Patch Available (was: Open)
> AWS DynamoDB Processors Do Not Update Credentials
> -------------------------------------------------
>
> Key: NIFI-2948
> URL: https://issues.apache.org/jira/browse/NIFI-2948
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.7.0, 1.0.0
> Reporter: James Wing
> Priority: Minor
>
> Following a report to the dev email list, there appears to be a bug in the AWS DynamoDB processors where the AWS credentials are cached by the processor once started, and not updated even if the processor is stopped, reconfigured, and started.
> The problem appears to be [AbstractDynamoDBProcessor::getDynamoDB|https://github.com/apache/nifi/blob/rel/nifi-1.0.0/nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/AbstractDynamoDBProcessor.java#L218], which assigns the dynamo client object to a class variable only once.
> *Repro Steps*
> # Add GetDynamoDB processor
> # Configure GetDynamoDB required properties but *not* any credential fields
> # Start the processor
> # Run a flowfile through - it should fail with "MissingAuthenticationTokenException" error
> # Stop the GetDynamoDB processor
> # Configure valid AWS credentials
> # Start the processor
> # Run a flowfile through - it should fail again with "MissingAuthenticationTokenException" still using the old credentials
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)