Write Document

Operation name

Write Document

Function overview

Writes input data to Microsoft Azure Cosmos DB collection.

Data model

The data model of this component is table model type.

Properties

= Remarks =

For details on use of variables, refer to Variables.

Basic settings

Item name

Required/Optional

Use of variables

Description

Remarks

Name

Required

Not available

Enter a name that is used on the script canvas.

 

Input data

Required

Not available

Select a component on the script canvas.

 

Required settings

Item name

Required/Optional

Use of variables

Description

Remarks

Destination

Required

Not available

Select a connection resource.

Add

A new connection resource can be added.

Edit list

Connection resource settings can be edited in > HULFT INTEGRATE > Connections.

 

Collection

Required

Available

Select or enter a collection name to be read.

 

Update when id value matches

Optional

Not available

Select whether or not to overwrite with input data when there's a document in the collection with the same id value as that of the input data.

  • When not selected, if there's a document with the same id value, then it results in an error.

Schema definition

Required

-

Specify item list for the collection specified in Collection.

Added rows will be the target items to write.

Each target item can be operated with the following buttons:

Up

Move the selected target item upwards by one row.

Down

Move the selected target item downwards by one row.

Add

Add a target item.

Delete

Delete the target item.

  • Make sure to create String type item named "id".

  • If the collection specified in Collection is unlimited, the item corresponding to the partition key of the collection will be a write target regardless of the setting.

    • If the item corresponding to the partition key isn't specified, a null value will be inserted.

Schema definition/Item name

Required

Available

Enter an item name of the collection specified in Collection.

  • Specified item name will be displayed in Mapper schema.

Schema definition/Type

Required

Not available

Select the type of Item name.

Property actions

Item name

Description

Remarks

Update collection list

Get collections from the specified destination and set them in Collection.

 

Update schema definition

Get type information from the document registered in the specified collection and set it to Schema definition.

  • Get the latest 100 items from the collection specified in Collection and extract item names and types.

    • One or more documents must be registered in collection.

  • If item type information can't be determined or if the type isn't supported, the item type will be blank.

  • Disabled when Destination or Collection isn't specified.

Comment

Item name

Required/Optional

Use of variables

Description

Remarks

Comment

Optional

Not available

You can write a short description of this connector.

 

Schemas

Input schema

The number of columns varies depending on the Attribute list settings.

= Remarks =

For schema structure, refer to Table model type .

Output schema

None.

Loading schema in Mapper

The schema is loaded automatically.

= Remarks =

For details, refer to Edit Schema.

Mass data processing

Mass data processing isn't supported.

Parallel Stream Processing

PSP is supported.

= Remarks =

For details on PSP, refer to Parallel Stream Processing.

Available component variables

Component variable name

Description

Remarks

count

The number of added or updated documents (insert_count + update_count) is stored.

  • The default value is null.

insert_count

The number of added documents is stored.

  • The default value is null.

update_count

The number of updated documents is stored.

  • The default value is null.

message_category

When an error occurs, the category of the message code corresponding to the error is stored.

  • The default value is null.

message_code

When an error occurs, the code of the message code corresponding to the error is stored.

  • The default value is null.

message_level

When an error occurs, the severity of the message code corresponding to the error is stored.

  • The default value is null.

error_type

When an error occurs, the error type is stored.

  • The default value is null.

  • The format of the error type is as follows.

    Example: java.io.FileNotFoundException

error_message

When an error occurs, the error message is stored.

  • The default value is null.

error_trace

When an error occurs, the trace information for the error is stored.

  • The default value is null.

Message codes, exception messages, and limitations

Connector

Message code

Exception message

Limitations

Messages and limitations of the Azure Cosmos DB connector

check

check

check

Notes

  • The specifications are subject to change without any prior notification depending on the changes in Azure Cosmos DB specifications.