The TIBCO StreamBase® Output Adapter for Apache Kafka Admin allows StreamBase applications to perform various administration requests to an Apache Kafka broker.
This section describes the properties you can set for this adapter, 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.
Adapter: A read-only field that shows the formal name of the adapter.
Class name: Shows the fully qualified class name that implements the functionality of this adapter. 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 options: This field provides a link to the Cluster Aware tab, where you configure the conditions under which this adapter starts.
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.
A comma-separated list of address:ports specifying one or more Apache
ZooKeeper servers to connect to for issuing commands. The default value is
|Enable Topics Port||check box||When selected, specifies that the adapter sends topic information on its topics port when the adapter receives a topics command. The default value is selected.|
|Enable Brokers Port||check box||When selected, specifies that the adapter sends broker information on its brokers port when the adapter receives a brokers command. The default value is selected.|
|Enable Read Value Port||check box||When selected, specifies that the adapter outputs value information on its read value Port based on a readValue command. The default value is selected.|
|Enable Status Port||check box||When selected, the adapter sends out informational data on its Status Port about various states of the adapter. The default value is cleared.|
|Session Timeout (MS)||int||The Zookeeper session timeout in milliseconds. Default: 6000 milliseconds.|
|Connection Timeout (MS)||int||The Zookeeper connection timeout in milliseconds. Default: 6000 milliseconds.|
|Log Level||INFO||Controls the level of verbosity the adapter uses to issue informational traces to the console. This setting is independent of the containing application's overall log level. Available values, in increasing order of verbosity, are: OFF, ERROR, WARN, INFO, DEBUG, TRACE.|
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 Command input port is always enabled by default. Use the command port to send action commands to the Kafka Admin adapter.
The minimum schema for the command input port is a single field named
command of type string. A command port with this schema can accept
commands, to generate output on the brokers and topics output ports.
The suggested full schema for the command input port is the following:
command, string. The command to send to the adapter. Valid values are: createTopic, deleteTopic, brokers, writeValue, readValue, topics.
topic (optional), string. The topic from which to subscribe and unsubscribe.
partition (optional), integer. The partition to subscribe to, leave null for default of 0.
properties, list(tuple). Where the tuple's schema is key (string), value (string).
The topics port, when enabled in the Adapter Properties tab of the Properties view, emits
tuples in response to a
The brokers port, when enabled in the Adapter Properties tab of the Properties view, emits
tuples in response to a
The read value port, when enabled in the Adapter Properties tab of the Properties view, emits
tuples in response to a
The status port is used to send status information tuples downstream to inform the user of changes.
The status port, when enabled in the Adapter Properties tab of the Properties view, emits status information tuples downstream to inform the user of changes.
type, string. The type of status information emitted on this port. Status types are:
Error — This message relates to an error that occurred.
Warn —This message relates to a warning that the user should be aware of.
Info — This message relates to extra status information.
action, string. A specific action related to this status message.
object, string. This value may be null. If it is not null, it contains a value relevant to the status message.
message, string. This is a formatted human readable message that explains the status message.
time, timestamp. The time the status message occurred.