Google Cloud Spanner Writer Parameters

About Web Connections
Connections store authentication information. For general information about web connections, please see Using Web Connections. For information about managing web services (including authorization credentials such as Client Id and Client Secret), please see Managing Web Services. Connection From the Connection parameter in a web service format, you can do one of the following: Select an existing previously defined connection. For information, see the section Reusing a Web Connection in Using Web Connections. Select Add Web Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users.

Project ID

The Google Cloud Platform Project ID.

Instance

The name of the Cloud Spanner instance.

Database

The name of the Cloud Spanner database.

Features Per Transaction

The number of features that FME places in each transaction before a transaction is committed to the database.

If the parameter is set to 0, then the entire write operation occurs in a single transaction.

Default: 1000

Query Timeout (Seconds)

This parameter defines the time, in seconds, after which a query will be terminated if it has not yet returned a result.

If set to 0, there is no timeout. The default is 30.

Note If this value is not set high enough, then the query will return the error Provider Error – Timeout Expired.

Maximum Reconnect Attempts

This parameter defines how many times in succession will FME attempt to recover from a dropped connection.

0 (default) – If a connection is dropped, the writer will fail the translation.
1 or more – If a connection is dropped, the writer will make n attempts to reconnect. The writer will also keep a cache of features that have not yet been committed. After recovering from a dropped connection, the writer will continue writing from its cache, so that no features are dropped along with the connection. Due to the extra step in writing to the cache, overall writing speeds may be slower in this mode.

The counter for reconnection attempts is reset when a connection is successfully recovered.

SQL to Run Before Write

This parameter allows for the execution of SQL statements before writing to a table. For example, it may be necessary to clean up a table before attempting to write to it. The statements will be executed only when the first feature arrives at the writer.

For detailed information about SQL functions, click the corresponding menu item in the SQL to Run editor help Closed .

Available menu options depend on the format.

Multiple SQL commands can be delimited by a character specified using the FME_SQL_DELIMITER directive, embedded at the beginning of the SQL block. The single character following this directive will be used to split the SQL block into SQL statements, which will then be sent to the database for execution. Note: Include a space before the character.

For example:

FME_SQL_DELIMITER ;
DELETE FROM instructors ;
DELETE FROM people
WHERE LastName='Doe' AND FirstName='John'

Multiple delimiters are not allowed and the delimiter character will be stripped before being sent to the database.

Any errors occurring during the execution of these SQL statements will normally terminate the reader or writer (depending on where the SQL statement is executed) with an error. If the specified statement is preceded by a hyphen (“-”), such errors are ignored.

SQL to Run After Write

This parameter allows for the execution of SQL statements after a set of tables has been written. For example, it may be necessary to clean up a temporary view after creating it.