# tDynamoDBOutput properties for Apache Spark Streaming (deprecated) Availability-note[Deprecated](https://help.talend.com/r/en-US/Cloud/labels-on-talend-help-center/availability-deprecated) This content is deprecated. These properties are used to configure tDynamoDBOutput running in the Spark Streaming Job framework. Information noteDeprecation: Spark Streaming is deprecated beginning with the R2026-09 release. Use Spark Structured Streaming instead. The Spark Streaming tDynamoDBOutput component belongs to the Databases family. This component is available in Talend Real-Time Big Data Platform and Talend Data Fabric. ## Basic settings | Properties | Description | | --- | --- | | Use an existing connection | Select this check box and in the Component
List drop-down list, select the desired connection component to
reuse the connection details you already defined. | | Access
Key | Enter the access
key ID that uniquely identifies an AWS Account. For further information about how to
get your Access Key and Secret Key, see [Getting Your AWS Access
Keys](http://docs.aws.amazon.com/ses/latest/DeveloperGuide/get-aws-keys.html). | | Secret
Key | Enter the secret access key,
constituting the security credentials in combination with the access Key.

To enter the secret key, click the [...]
button next to the secret key field, and then in the pop-up dialog box enter the password
between double quotes and click OK to save the
settings. | | Use End Point | Select this check box and in the Server URL
field displayed, specify the Web service URL of the DynamoDB database service. | | Region | Specify the AWS region by selecting or entering a region name between double
quotation marks (e.g. *"us-east-1"*). For more information about the
AWS Region, see [Regions and Endpoints](http://docs.aws.amazon.com/general/latest/gr/rande.html#s3_region). | | Schema and Edit
schema |

A schema is a row description. It defines the number of fields (columns) to be processed and passed on to the next component. When you create a Spark Job, avoid the reserved word line when naming the fields.
- Built-In: You create and store the schema locally for this component only.
- Repository: You have already created the schema and stored it in the Repository. You can reuse it in various projects and Job designs.
Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available:
- View schema: choose this option to view the schema only.
- Change to built-in property: choose this option to change the schema to Built-in for local changes.
- Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion.
  
  If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the Repository Content window.

| | Table Name | Specify the name of the table in which you need to write data. This table must already
exist. | | Die on error | Select the checkbox to stop the execution of the Job when an error
occurs. | ## Advanced settings | Properties | Description | | --- | --- | | Throughput write percent | Enter, without using quotation marks, the percentage (expressed in decimal) to be used of
the write capacity pre-defined in Amazon. For further information about this write capacity,
see [Provision throughput for write](http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/HowItWorks.ProvisionedThroughput.html#HowItWorks.ProvisionedThroughput.Writes). | | Advanced properties | Add properties to define extra operations you need tDynamoDBOutput to perform when writing data.

This table is present for future evolution of the component and using it requires the
high-level knowledge of DynamoDB development. Currently, there are no interesting user
configurable properties. | ## Usage | Usage guidance | Description | | --- | --- | | **Usage rule** | This component is used as an end component and requires an input link.

This component should use a tDynamoDBConfiguration
component present in the same Job to connect to a DynamoDB database. You need to drop a
tDynamoDBConfiguration component alongside this
component and configure the Basic settings of this
component to use tDynamoDBConfiguration.

This component, along with the Spark Streaming component Palette it belongs to, appears
only when you are creating a Spark Streaming Job.

Note that in this documentation, unless otherwise explicitly stated, a scenario presents
only Standard Jobs, that is to say traditional
Talend
data
integration Jobs. | | Spark Connection | In the Spark
Configuration tab in the Run
view, define the connection to a given Spark cluster for the whole Job. In
addition, since the Job expects its dependent jar files for execution, you must
specify the directory in the file system to which these jar files are
transferred so that Spark can access these files:

Yarn mode (Yarn client or Yarn cluster):
- When using Google Dataproc, specify a bucket in the Google Storage staging bucket field in the Spark configuration tab.
- When using HDInsight, specify the blob to be used for Job deployment in the Windows Azure Storage configuration area in the Spark configuration tab.
- When using Altus, specify the S3 bucket or the Azure Data Lake Storage for Job deployment in the Spark configuration tab.
- When using on-premises distributions, use the configuration component corresponding to the file system your cluster is using. Typically, this system is HDFS and so use tHDFSConfiguration.
Standalone mode: use the configuration component corresponding to the file system your cluster is using, such as tHDFSConfiguration Apache Spark Batch or tS3Configuration Apache Spark Batch.

If you are using Databricks without any configuration component present in your Job, your business data is written directly in DBFS (Databricks Filesystem).

This connection is effective on a per-Job basis. |