PutAzureDataLakeStorage 2.0.0

Bundle
org.apache.nifi | nifi-azure-nar
Description
Writes the contents of a FlowFile as a file on Azure Data Lake Storage Gen 2
Tags
adlsgen2, azure, cloud, datalake, microsoft, storage
Input Requirement
REQUIRED
Supports Sensitive Dynamic Properties
false
  • Additional Details for PutAzureDataLakeStorage 2.0.0

    PutAzureDataLakeStorage

    This processor is responsible for uploading files to Azure Data Lake Storage Gen2.

    File uploading and cleanup process in case of “Write and Rename” strategy

    New file upload

    1. A temporary file is created with random prefix under the given path in ‘_nifitempdirectory’.
    2. Content is appended to temp file.
    3. Temp file is moved to the final destination directory and renamed to its original name.
    4. In case of appending or renaming failure, the temp file is deleted.
    5. In case of temporary file deletion failure, the temp file remains on the server.

    Existing file upload

    • Processors with “fail” conflict resolution strategy will direct the FlowFile to “Failure” relationship.
    • Processors with “ignore” conflict resolution strategy will direct the FlowFile to “Success” relationship.
    • Processors with “replace” conflict resolution strategy:
    1. A temporary file is created with random prefix under the given path in ‘_nifitempdirectory’.
    2. Content is appended to temp file.
    3. Temp file is moved to the final destination directory and renamed to its original name, the original file is overwritten.
    4. In case of appending or renaming failure, the temp file is deleted and the original file remains intact.
    5. In case of temporary file deletion failure, both temp file and original file remain on the server.

    File uploading and cleanup process in case of “Simple Write” strategy

    New file upload

    1. An empty file is created at its final destination.
    2. Content is appended to the file.
    3. In case of appending failure, the file is deleted.
    4. In case of file deletion failure, the file remains on the server.

    Existing file upload

    • Processors with “fail” conflict resolution strategy will direct the FlowFile to “Failure” relationship.
    • Processors with “ignore” conflict resolution strategy will direct the FlowFile to “Success” relationship.
    • Processors with “replace” conflict resolution strategy:
    1. An empty file is created at its final destination, the original file is overwritten.
    2. Content is appended to the file.
    3. In case of appending failure, the file is deleted and the original file is not restored.
    4. In case of file deletion failure, the file remains on the server.
Properties
Relationships
Name Description
failure Files that could not be written to Azure storage for some reason are transferred to this relationship
success Files that have been successfully written to Azure storage are transferred to this relationship
Writes Attributes
Name Description
azure.filesystem The name of the Azure File System
azure.directory The name of the Azure Directory
azure.filename The name of the Azure File
azure.primaryUri Primary location for file content
azure.length The length of the Azure File
See Also