Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Introduction

A batch sink that pushes data from hydrator pipelines into dynamoDb tables.

Use case(s)

  • An organization wants to parse the logs generated by a system and want to store the metadata in dynamodb tables.

User Storie(s)

    • User should be able to provide the table name in DynamoDb. 
    • User should be able to provide the primary key of the table. 
    • User should be able to provide the type of primary key (hash or range).
    • The table should be created if it is not already existing. 
    • User should be able to provide the AWS endpoint url for DynamoDb instance.
    • User should be able to provide the AWS region id for DynamoDb instance.
    • User should be able to provide the AWS access id.
    • User should be able to provide the AWS access key.

Plugin Type

  • Batch Source
  • Batch Sink 
  • Real-time Source
  • Real-time Sink
  • Action
  • Post-Run Action
  • Aggregate
  • Join
  • Spark Model
  • Spark Compute

Configurables

This section defines properties that are configurable for this plugin. 

User Facing Name
Type
Description
Constraints
Table nameStringName of the dynamo db tableNaming convention constraints from AWS
Primary key fieldsList<Map<String,String>>Primary key fields of the tableThere should be at least 1 primary key
endpoint urlStringAWS endpoint url for DynamoDb instance

Optional, could be reconstructed using regionId

region idStringAWS region id for DynamoDb instance. 
throughputIntIntended throughput for DynamoDb(Optional)
access idStringAWS access id 
access keypasswordAWS access key 

Design / Implementation Tips

Design

Approach(s)

Properties

  • regionId: The region for AWS Dynamo DB to connect to.
  • accessKey: Access key for AWS Dynamo DB.
  • secretAccessKey: Secret access key for AWS Dynamo DB.

  • tableName: The table to read the data from.

  • primaryKey: The field name to be used as priary key.

Security

Limitation(s)

Future Work

Test Case(s)

Sample Pipeline

 

Table of Contents

Checklist

  • User stories documented 
  • User stories reviewed 
  • Design documented 
  • Design reviewed 
  • Feature merged 
  • Examples and guides 
  • Integration tests 
  • Documentation for feature 
  • Short video demonstrating the feature
  • No labels