Deploying the ADLS to ADLS Avro ReadyFlow

Learn how to use the Deployment wizard to deploy the ADLS to ADLS Avro 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.

  1. In DataFlow, from the left navigation pane, click Catalog.
    Flow definitions available for you to deploy are displayed, one definition per row.
  2. Launch the Deployment wizard.
    1. Click the row to display the flow definition details and versions.
    2. Click a row representing a flow definition version to display flow definition version details and the Deploy button.
    3. Click Deploy to launch the Deployment wizard.
  3. Select the environment to which you want to deploy this version of your flow definition, and click Continue.
  4. In the Overview, give your flow deployment a unique name.

    You can use this name to distinguish between different versions of a flow definition, flow definitions deployed to different environments, and similar.

  5. In NiFi Configuration:
    1. Select a NiFi Runtime Version for your flow deployment. Cloudera recommends that you always use the latest available version, if possible.
    2. 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.
  6. 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.

  7. 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.
  8. 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 metrics tracking.

    See Working with KPIs for more information about the KPIs available and how you can monitor them.

  9. 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 ADLS to ADLS Avro Readyflow, the following parameters are required. Use the information you collected in the Meeting the prerequisites section.

ADLS to ADLS Avro ReadyFlow configuration parameters
Parameter Name Description Example
CDP Workload User Specify the CDP machine user or workload username that you want to use to authenticate to the object stores and to the Schema Registry. Ensure this user has the appropriate access rights to the object store locations and to the Schema Registry in Ranger or IDBroker.
CDP Workload User Password Specify the password of the CDP machine user or workload user you are using to authenticate against the object stores (via IDBroker) and the Schema Registry.
CSV Delimiter If your source data is CSV, specify the delimiter here.
Data Input Format Specify the format of your input data.
  • CSV
  • JSON
  • AVRO
Destination ADLS File System Specify the file system name you want to write to. The full path will be constructed from: abfs://#{Destination ADLS File System}@#{Destination ADLS Storage Account}.dfs.core.windows.net/#{Destination ADLS Path}
Destination ADLS Path Specify the path within the ADLS data container where you want to write to without any leading characters. The full path will be constructed from: abfs://#{Destination ADLS File System}@#{Destination ADLS Storage Account}.dfs.core.windows.net/#{Destination ADLS Path}
Destination ADLS Storage Account Specify the storage account name you want to write to. The full path will be constructed from: abfs://#{Destination ADLS File System}@#{Destination ADLS Storage Account}.dfs.core.windows.net/#{Destination ADLS Path}
Schema Name Specify the schema name to be looked up in the Schema Registry used to parse the source files.
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.
Source ADLS File System Specify the file system name you want to read from. The full path will be constructed from: abfs://#{Source ADLS File System}@#{Source ADLS Storage Account}.dfs.core.windows.net/#{Source ADLS Path}
Source ADLS Path Specify the path within the ADLS data container where you want to read from without any leading characters. The full path will be constructed from: abfs://#{Source ADLS File System}@#{Source ADLS Storage Account}.dfs.core.windows.net/#{Source ADLS Path}
Source ADLS Storage Account Specify the storage account name you want to read from. The full path will be constructed from: abfs://#{Source ADLS File System}@#{Source ADLS Storage Account}.dfs.core.windows.net/#{Source ADLS Path}