Dictionary Setup Examples

The following content offers a guided tour of a dictionary data source and data sink configuration and processing in a single container node.

Dictionary Data Source

Configure source connection

The default Bucket Name is the name of the source, itself, but you can enter any name here. Note that by default, the web app generates the name of the source as "source."

Configure input mappings

Because source_mapping1 has a non-null entry in the JSON Value field, the file input_file1.txt will be generated in the container with "42"—the specified JSON value.

Because source_mapping2 has a null entry in the JSON Value field, the file input_file2.txt will be generated in the container with whatever value is found in the bucket under source_bucket.source_mapping2.

View source JSON

The contents of data_sources/source.json includes the bucket name and mapping keys.

Dictionary Data Sink

Configure source connection

The default Bucket Name is the name of the sink, itself, but you can enter any name here. Note that by default, the web app generates the name of the sink as "sink."

Configure input mappings

Because sink_mapping1 has defined the Target Variable, the contents of the output_file1.txt file will be written to the runtime variable output_variable.

Because sink_mapping2 has not defined the Target Variable, the contents of the output_file2.txt file will be written to the bucket under sink_bucket.sink_mapping2.

View source JSON

The contents of data_sinks/sink.json includes the bucket name and mapping keys.

Notebook for Node using Dictionary Source & Sink

The contents of notebook.json includes the container mappings.