GoogleCloudPubSubConnector
Connects to the Google Cloud Pub/Sub service. Supports creation of topics and subscriptions and sending or receiving messages.
Typical Uses
- Processing of event logging
- Interoperability with Big Data analytics platforms
Configuration
Input Ports
This transformer accepts any feature.
Output Ports
The output of this transformer will vary depending on the action performed. Message data and metadata are presented as feature attributes.
- After a Receive action, output features represent messages received from the subscription.
- After a Send action, output features represent messages sent to the topic.
The incoming feature is output through this port.
Features that cause the operation to fail are output through this port. An fme_rejection_code attribute, having the value ERROR_DURING_PROCESSING, will be added, along with a more descriptive fme_rejection_message attribute which contains more specific details as to the reason for the failure.
Note: If a feature comes in to the GoogleCloudPubSubConnector already having a value for fme_rejection_code, this value will be removed.
Rejected Feature Handling: can be set to either terminate the translation or continue running when it encounters a rejected feature. This setting is available both as a default FME option and as a workspace parameter.
Parameters
Credential Source |
Required for authentication. Using a web connection integrates best with FME, but in some cases, you may wish to use a key file.
|
Account |
Available when the credential source is Web Connection. To create a Google Cloud connection, click the 'Account' drop-down box and select 'Add Web Connection...'. The connection can then be managed via Tools > FME Options... > Web Connections. |
Project ID | The Google Cloud project ID. |
Action |
The type of operation to perform. Choices are:
|
The remaining parameters available depend on the value of the Request > Action parameter. Parameters for each Action are detailed below.
Subscription
Subscription |
The subscription to subscribe to messages. A topic can have multiple subscriptions. |
Create Subscription |
If Yes is selected, the subscription will be created automatically with the following subscription options. |
Create Subscription Options
Topic |
The topic to subscribe to. |
Acknowledgment Deadline (secs) |
The approximate amount of time that the service waits for the subscriber to acknowledge receipt of the message before resending. The default and minimum is 10 seconds. The maximum is 10 minutes. |
Receive Messages Options
Mode |
Two message receiving options are available:
|
Max Number of Messages |
In Batch mode, up to the specified number of messages. Often the service will return less. |
Encoding |
By default, the _value attribute contains the raw bytes received from the server. If an encoding is selected, the connector will instead attempt to decode the value of received message to a string using the selected encoding. |
Topics
Topics |
The topics where the message is sent. Multiple topics are space separated. |
Create Missing Topics |
If Yes is selected, topics will be created automatically if they do not exist. |
Send Messages Options
Message Value |
The actual message data. This must be a string or binary value. The value must match the encoding type. |
Encoding |
The encoding of the message value. The encoding must be appropriate for the message value. |
Attributes |
Additional attributes for the message. An attribute has a key and a value, which may be text strings or byte strings. |
The following attributes can be selected for inclusion on the output features. Each output feature represents a message that was either sent or received.
_id |
The id of the message |
_value |
The value of the message |
_timestamp |
The message creation timestamp. Note that timestamps for sent messages are not available. |
_partition |
The partition the message is stored in |
_attributes{}.name |
Structured list attributes containing the header keys and values of a received message. Note that the order of attributes may be arbitrary. |
Editing Transformer Parameters
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
Defining Values
There are several ways to define a value for use in a Transformer. The simplest is to simply type in a value or string, which can include functions of various types such as attribute references, math and string functions, and workspace parameters. There are a number of tools and shortcuts that can assist in constructing values, generally available from the drop-down context menu adjacent to the value field.
Using the Text Editor
The Text Editor provides a convenient way to construct text strings (including regular expressions) from various data sources, such as attributes, parameters, and constants, where the result is used directly inside a parameter.
Using the Arithmetic Editor
The Arithmetic Editor provides a convenient way to construct math expressions from various data sources, such as attributes, parameters, and feature functions, where the result is used directly inside a parameter.
Conditional Values
Set values depending on one or more test conditions that either pass or fail.
Parameter Condition Definition Dialog
Content
Expressions and strings can include a number of functions, characters, parameters, and more - whether entered directly in a parameter or constructed using one of the editors.
These functions manipulate and format strings. | |
A set of control characters is available in the Text Editor. | |
Math functions are available in both editors. | |
These operators are available in the Arithmetic Editor. | |
These return primarily feature-specific values. | |
FME and workspace-specific parameters may be used. | |
Working with User Parameters | Create your own editable parameters. |
Reference
Processing Behavior |
|
Feature Holding |
No |
Dependencies | Google Cloud account |
FME Licensing Level | FME Base Edition and above |
Aliases | |
History | Released FME 2019.0 |
Categories |
FME Community
The FME Community is the place for demos, how-tos, articles, FAQs, and more. Get answers to your questions, learn from other users, and suggest, vote, and comment on new features.
Search for all results about the GoogleCloudPubSubConnector on the FME Community.
Examples may contain information licensed under the Open Government Licence – Vancouver