The Tuple to JSON Java operator converts StreamBase tuples to JSON-encoded data. Each tuple enqueued to the operator results in a single JSON string emitted on its output port.
The operator's input schema determines the set of fields that appear in the generated JSON output. The hierarchy of the fields
in the schema matches that of the elements in the JSON. Fields containing
null are optionally discarded and may not appear in the JSON output. The incoming schema is duplicated to the output schema and
a new user defined field is added which contains the JSON output.
This section describes the properties you can set for a Tuple to JSON operator, using the various tabs of the Properties view in StreamBase Studio.
Name: Use this required field to specify or change the name of this instance of this component, which must be unique in the current EventFlow module. The name must contain only alphabetic characters, numbers, and underscores, and no hyphens or other special characters. The first character must be alphabetic or an underscore.
Operator: A read-only field that shows the formal name of the operator.
Class name: Shows the fully qualified class name that implements the functionality of this operator. If you need to reference this class name elsewhere in your application, you can right-click this field and select Copy from the context menu to place the full class name in the system clipboard.
Start with application: If this field is set to Yes (default) or to a module parameter that evaluates to
true, this instance of this operator starts as part of the JVM engine that runs this EventFlow fragment. If this field is set
to No or to a module parameter that evaluates to
false, the operator instance is loaded with the engine, but does not start until you send an epadmin container resume command (or its sbadmin equivalent), or until you start the component with StreamBase Manager.
Enable Error Output Port: Select this check box to add an Error Port to this component. In the EventFlow canvas, the Error Port shows as a red output port, always the last port for the component. See Using Error Ports to learn about Error Ports.
Description: Optionally enter text to briefly describe the component's purpose and function. In the EventFlow Editor canvas, you can see the description by pressing Ctrl while the component's tooltip is displayed.
|Output Field Name||The name of the field to be created in the output schema that contains the JSON converted from the incoming tuple.|
|Tuple Field||The field in the inbound tuple that contains the tuple to convert to JSON. Leave blank to convert the entire inbound tuple.|
|Enable Status Port||If enabled, the status port is made available to receive output status messages.|
|Log Level||Controls the level of verbosity the adapter uses to send notifications to the console. This setting can be higher than the containing application's log level. If set lower, the system log level is used. Available values, in increasing order of verbosity, are: OFF, ERROR, WARN, INFO, DEBUG, TRACE.|
|Include Null Fields||Include null fields in the JSON output.|
|Timestamps as long||If enabled, timestamp fields are converted to a long value.|
|Timestamp Format||The format to use when converting timestamp values to a string.|
|Encode Sub Type||The type of transformation that should be used when there are sub-tuples to process.
Use the settings in this tab to allow this operator or adapter to start and stop based on conditions that occur at runtime in a cluster with more than one node. During initial development of the fragment that contains this operator or adapter, and for maximum compatibility with TIBCO Streaming releases before 10.5.0, leave the Cluster start policy control in its default setting, Start with module.
Cluster awareness is an advanced topic that requires an understanding of StreamBase Runtime architecture features, including clusters, quorums, availability zones, and partitions. See Cluster Awareness Tab Settings on the Using Cluster Awareness page for instructions on configuring this tab.
Use the Concurrency tab to specify parallel regions for this instance of this component, or multiplicity options, or both. The Concurrency tab settings are described in Concurrency Options, and dispatch styles are described in Dispatch Styles.
Concurrency settings are not suitable for every application, and using these settings requires a thorough analysis of your application. For details, see Execution Order and Concurrency, which includes important guidelines for using the concurrency options.
The operator has one input port and two output ports to communicate with the surrounding application.
The Tuple to JSON operator's ports are used as follows:
TupleIn: The tuple to be converted to JSON. The TupleIn port can be any schema.
DataOut: This output port contains all the fields of the TupleIn port with an added user defined field which contains the contents of the generated JSON string
Status: A tuple is emitted on this port when an attempt to convert a tuple to an JSON message fails. The Status port has the following schema:
type, string: Contains the following value describing the type of event that occurred:
action, string: Contains the following value indicating the conversion failed:
object, string: Contains a string representation of the input tuple.
message, string: Contains a human-readable description of the conversion failure.
time, timestamp: Contains the time of the conversion failure.
inputTuple, tuple: Contains a copy of the input tuple.