Github user apiri commented on a diff in the pull request:

    https://github.com/apache/nifi/pull/224#discussion_r61939505
  
    --- Diff: 
nifi-nar-bundles/nifi-aws-bundle/nifi-aws-processors/src/main/java/org/apache/nifi/processors/aws/dynamodb/PutDynamoDB.java
 ---
    @@ -0,0 +1,182 @@
    +/*
    + * Licensed to the Apache Software Foundation (ASF) under one or more
    + * contributor license agreements.  See the NOTICE file distributed with
    + * this work for additional information regarding copyright ownership.
    + * The ASF licenses this file to You under the Apache License, Version 2.0
    + * (the "License"); you may not use this file except in compliance with
    + * the License.  You may obtain a copy of the License at
    + *
    + *     http://www.apache.org/licenses/LICENSE-2.0
    + *
    + * Unless required by applicable law or agreed to in writing, software
    + * distributed under the License is distributed on an "AS IS" BASIS,
    + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    + * See the License for the specific language governing permissions and
    + * limitations under the License.
    + */
    +package org.apache.nifi.processors.aws.dynamodb;
    +
    +import java.io.ByteArrayOutputStream;
    +import java.io.IOException;
    +import java.util.Arrays;
    +import java.util.Collections;
    +import java.util.HashMap;
    +import java.util.List;
    +import java.util.Map;
    +
    +import org.apache.commons.io.IOUtils;
    +import org.apache.commons.lang3.StringUtils;
    +import org.apache.nifi.annotation.behavior.InputRequirement;
    +import org.apache.nifi.annotation.behavior.ReadsAttribute;
    +import org.apache.nifi.annotation.behavior.ReadsAttributes;
    +import org.apache.nifi.annotation.behavior.InputRequirement.Requirement;
    +import org.apache.nifi.annotation.behavior.SupportsBatching;
    +import org.apache.nifi.annotation.behavior.WritesAttribute;
    +import org.apache.nifi.annotation.behavior.WritesAttributes;
    +import org.apache.nifi.annotation.documentation.CapabilityDescription;
    +import org.apache.nifi.annotation.documentation.SeeAlso;
    +import org.apache.nifi.annotation.documentation.Tags;
    +import org.apache.nifi.components.PropertyDescriptor;
    +import org.apache.nifi.flowfile.FlowFile;
    +import org.apache.nifi.processor.ProcessContext;
    +import org.apache.nifi.processor.ProcessSession;
    +
    +import com.amazonaws.AmazonClientException;
    +import com.amazonaws.AmazonServiceException;
    +import com.amazonaws.services.dynamodbv2.document.BatchWriteItemOutcome;
    +import com.amazonaws.services.dynamodbv2.document.DynamoDB;
    +import com.amazonaws.services.dynamodbv2.document.Item;
    +import com.amazonaws.services.dynamodbv2.document.TableWriteItems;
    +import com.amazonaws.services.dynamodbv2.model.AttributeValue;
    +import com.amazonaws.services.dynamodbv2.model.WriteRequest;
    +
    +@SupportsBatching
    +@SeeAlso({DeleteDynamoDB.class, GetDynamoDB.class})
    +@InputRequirement(Requirement.INPUT_REQUIRED)
    +@Tags({"Amazon", "DynamoDB", "AWS", "Put", "Insert"})
    +@CapabilityDescription("Puts a document from DynamoDB based on hash and 
range key.  The table can have either hash and range or hash key alone."
    +        + " Currently the keys supported are string and number and value 
can be json document. "
    +        + "In case of hash and range keys both key are required for the 
operation."
    +        + " The FlowFile content must be JSON. FlowFile content is mapped 
to the specified Json Document attribute in the DynamoDB item.")
    +@WritesAttributes({
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_KEY_ERROR_UNPROCESSED, description = "Dynamo 
db unprocessed keys"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_RANGE_KEY_VALUE_ERROR, description = 
"Dynamod db range key error"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_KEY_ERROR_NOT_FOUND, description = "Dynamo 
db key not found"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_EXCEPTION_MESSAGE, description = 
"Dynamo db exception message"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_CODE, description = "Dynamo db error 
code"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_MESSAGE, description = "Dynamo db 
error message"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_TYPE, description = "Dynamo db error 
type"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_SERVICE, description = "Dynamo db 
error service"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_RETRYABLE, description = "Dynamo db 
error is retryable"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_REQUEST_ID, description = "Dynamo db 
error request id"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ERROR_STATUS_CODE, description = "Dynamo db 
error status code"),
    +    @WritesAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ITEM_IO_ERROR, description = "IO exception 
message on creating item")
    +    })
    +@ReadsAttributes({
    +    @ReadsAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ITEM_HASH_KEY_VALUE, description = "Items 
hash key value" ),
    +    @ReadsAttribute(attribute = 
AbstractDynamoDBProcessor.DYNAMODB_ITEM_RANGE_KEY_VALUE, description = "Items 
range key value" )
    +    })
    +public class PutDynamoDB extends AbstractWriteDynamoDBProcessor {
    +
    +   public static final List<PropertyDescriptor> properties = 
Collections.unmodifiableList(
    +            Arrays.asList(TABLE, HASH_KEY_NAME, RANGE_KEY_NAME, 
HASH_KEY_VALUE, RANGE_KEY_VALUE,
    +                HASH_KEY_VALUE_TYPE, RANGE_KEY_VALUE_TYPE, JSON_DOCUMENT, 
DOCUMENT_CHARSET, BATCH_SIZE,
    +                REGION, ACCESS_KEY, SECRET_KEY, CREDENTIALS_FILE, 
AWS_CREDENTIALS_PROVIDER_SERVICE, TIMEOUT, SSL_CONTEXT_SERVICE));
    +
    +    @Override
    +    protected List<PropertyDescriptor> getSupportedPropertyDescriptors() {
    +        return properties;
    +    }
    +
    +    @Override
    +    public void onTrigger(final ProcessContext context, final 
ProcessSession session) {
    +        List<FlowFile> flowFiles = 
session.get(context.getProperty(BATCH_SIZE).asInteger());
    +        if (flowFiles == null || flowFiles.size() == 0) {
    +            return;
    +        }
    +
    +        Map<ItemKeys,FlowFile> keysToFlowFileMap = new HashMap<>();
    +
    +        final String table = context.getProperty(TABLE).getValue();
    +
    +        final String hashKeyName = 
context.getProperty(HASH_KEY_NAME).getValue();
    +        final String hashKeyValueType = 
context.getProperty(HASH_KEY_VALUE_TYPE).getValue();
    +        final String rangeKeyName = 
context.getProperty(RANGE_KEY_NAME).getValue();
    +        final String rangeKeyValueType = 
context.getProperty(RANGE_KEY_VALUE_TYPE).getValue();
    +        final String jsonDocument = 
context.getProperty(JSON_DOCUMENT).getValue();
    --- End diff --
    
    Hey @Paul424!
    
    Sorry for missing your previous question, my filters consumed the 
notification email, but saw that you got a resolution and your approach sounds 
great.
    
    The key thing to underscore is that a FlowFile is a set of attributes and a 
content section.  Expression Language (EL) is a way to do some quick operations 
on those attributes.  Attributes are effectively metadata about the content and 
aid in making decisions and characterizing the data upfront so that the content 
can make its way through the appropriate pipeline and processing. 
    
    If you happen to run into anything else in terms of AWS processors, or even 
NiFi in general, feel free to reach out to the community.  
(http://nifi.apache.org/mailing_lists.html)  Any feedback on how we could make 
this or anything else easier is always greatly appreciated!


---
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 [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to