Deploying the ListenHTTP filter to Kafka ReadyFlow
Learn how to use the Deployment wizard to deploy the ListenHTTP filter to Kafka ReadyFlow using the information you collected using the prerequisites checklist.
The CDF Catalog is where you manage the flow definition lifecycle, from initial import, through versioning, to deploying a flow definition.
In DataFlow, from the left navigation pane, click
Flow definitions available for you to deploy are displayed, one definition per row.
Launch the Deployment wizard.
- Click the row to display the flow definition details and versions.
- Click a row representing a flow definition version to display flow definition version details and the Deploy button.
- Click Deploy to launch the Deployment wizard.
Select the environment to which you want to deploy this version of your
flow definition, and click Continue.
In the Overview, give your flow deployment a unique
You can use this name to distinguish between different versions of a flow definition, flow definitions deployed to different environments, and similar.
In NiFi Configuration:
- Select a NiFi Runtime Version for your flow deployment. Cloudera recommends that you always use the latest available version, if possible.
- Autostart Behavior is on by default, allowing your flow to start automatically after successful deployment. You can clear selection if you do not want the automatic start.
In Parameters, specify parameter values like connection
strings, usernames and similar, and upload files like truststores, and similar.
For parameters specific to this ReadyFlow, see the Example with the configuration parameters table below.
Specify your Sizing & Scaling configurations.
- NiFi node sizing
- You can adjust the size of your cluster from Extra Small to Large
- Number of NiFi nodes
- You can set whether you want to automatically scale your cluster depending on resource demands. When you enable autoscaling, the minimum NiFi nodes are used for initial size and the workload scales up or down depending on resource demands.
- You can set the number of nodes from 1 to 32.
In Key Performance Indicators, you can set up your
metrics system with specific KPIs to track the performance of a deployed
flow. You can also define when and how to receive alerts about the KPI
See Working with KPIs for more information about the KPIs available and how you can monitor them.
- Review the summary of the information you provided in the Deployment wizard and make any necessary edits by clicking Previous. When you are finished, complete your flow deployment by clicking Deploy.
Once you click Deploy, you are redirected to the Alerts tab in the Flow Deployment Detail view where you can track its progress.
For the ListenHTTP filter to Kafka Readyflow, the following parameters are required. Use the information you collected in the Meeting the prerequisites section.
|ListenHTTP filter to Kafka ReadyFlow configuration parameters|
|CDP Workload User||Specify the CDP machine user or workload user name that you want to use to authenticate to Kafka. Ensure this user has the appropriate access rights to the destination Kafka topic.|
|CDP Workload User Password||Specify the password of the CDP machine user or workload user you are using to authenticate against Kafka.|
|CSV Delimiter||If your source data is CSV, specify the delimiter here.|
|Data Input Format||Specify the format of your input data. You can use "CSV", "JSON", or "AVRO" with this ReadyFlow.|
|Data Output Format||Specify the desired format for your output data. You can use "CSV", "JSON" or "AVRO" with this ReadyFlow.|
|Filter Rule||Specify the filter rule expressed in SQL to filter streaming events for the destination topic. Records matching the filter will be written to the destination topic. The default value forwards all records.|
|Kafka Broker Endpoint||Specify the Kafka bootstrap servers string as a comma separated list.|
|Kafka Destination Topic||Specify the destination topic name.|
|Kafka Producer ID||Specify the id for the Kafka producer writing into the destination topic.|
|Listening Port||Specify the port to listen on for incoming connections.|
|Schema Name||Specify the schema name to be looked up in the Schema Registry.|
|Schema Registry Hostname||Specify the hostname of the Schema Registry you want to connect to. This must be the direct hostname of the Schema Registry itself, not the Knox Endpoint.|