yujunjun/OpenMetadata
1
0
Fork 0
mirror of https://github.com/open-metadata/OpenMetadata.git synced 2025-07-07 00:58:46 +00:00
Code Issues Packages Projects Releases Wiki Activity
OpenMetadata/openmetadata-docs/content/v1.7.x/connectors/pipeline/nifi/index.md
Rounak Dhillon f696227ead
Doc: SEO Title Updation (#21842) 
* Doc: SEO Title Updation

* Doc: Data Discovery Gif Updation

* Doc: SEO title updation

* Doc: SEO Title Updation

---------

Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”>
2025-06-20 07:16:38 -07:00

3.3 KiB
Raw Permalink Blame History

title slug
Nifi Connector | OpenMetadata Data Pipeline Integration /connectors/pipeline/nifi

{% connectorDetailsHeader name="NiFi" stage="PROD" platform="OpenMetadata" availableFeatures=["Pipelines", "Usage"] unavailableFeatures=["Pipeline Status", "Owners", "Tags", "Lineage"] / %}

In this section, we provide guides and references to use the NiFi connector.

Configure and schedule NiFi metadata workflows from the OpenMetadata UI:

{% partial file="/v1.7/connectors/ingestion-modes-tiles.md" variables={yamlPath: "/connectors/pipeline/nifi/yaml"} /%}

Requirements

Metadata

OpenMetadata supports 2 types of connection for the NiFi connector:

  • basic authentication: use username/password to authenticate to NiFi.
  • client certificate authentication: use CA, client certificate and client key files to authenticate.

The user should be able to send request to the NiFi API and access the Resources endpoint.

Metadata Ingestion

{% partial file="/v1.7/connectors/metadata-ingestion-ui.md" variables={ connector: "Nifi", selectServicePath: "/images/v1.7/connectors/nifi/select-service.png", addNewServicePath: "/images/v1.7/connectors/nifi/add-new-service.png", serviceConnectionPath: "/images/v1.7/connectors/nifi/service-connection.png", } /%}

{% stepsContainer %} {% extraContent parentTagName="stepsContainer" %}

Connection Details

  • Host and Port: Pipeline Service Management/UI URI. This should be specified as a string in the format 'hostname:port'.

  • NiFi Config: OpenMetadata supports username/password or client certificate authentication.

    1. Basic Authentication
      • Username: Username to connect to NiFi. This user should be able to send request to the Nifi API and access the Resources endpoint.
      • Password: Password to connect to NiFi.
      • Verify SSL: Whether SSL verification should be perform when authenticating.
    2. Client Certificate Authentication
      • Certificate Authority Path: Path to the certificate authority (CA) file. This is the certificate used to store and issue your digital certificate. This is an optional parameter. If omitted SSL verification will be skipped; this can present some sever security issue. important: This file should be accessible from where the ingestion workflow is running. For example, if you are using OpenMetadata Ingestion Docker container, this file should be in this container.
      • Client Certificate Path: Path to the certificate client file. important: This file should be accessible from where the ingestion workflow is running. For example, if you are using OpenMetadata Ingestion Docker container, this file should be in this container.
      • Client Key Path: Path to the client key file. important: This file should be accessible from where the ingestion workflow is running. For example, if you are using OpenMetadata Ingestion Docker container, this file should be in this container.

{% /extraContent %}

{% partial file="/v1.7/connectors/test-connection.md" /%}

{% partial file="/v1.7/connectors/pipeline/configure-ingestion.md" /%}

{% partial file="/v1.7/connectors/ingestion-schedule-and-deploy.md" /%}

{% /stepsContainer %}