Skip to main content Skip to complementary content
Close announcements banner

Writing files in Azure Storage

Procedure

  1. Double-click tAzureStoragePut to open its Component view.
  2. Select the component whose connection details will be used to set up the Azure storage connection. In this example, it is tAzureStorageConnection_1.
  3. In the Container name field, enter the name of the container you need to write files in. In this example, it is talendcontainer, a container created in the scenario Creating a container in Azure Storage.
  4. In the Local folder field, enter the path, or browse, to the directory where the files to be used are stored. In this scenario, they are some pictures showing technical process and stored locally in E:/photos. Therefore, put E:/photos; this allows tAzureStoragePut to upload all the files of this folder and its sub-folders into the talendcontainer container.

    For demonstration purposes, the example photos are organized as follows in the E:/photos folder.

    • Directly beneath the E:/photos level:

      components-use_case_triakinput_1.png

      components-use_case_triakinput_2.png

      components-use_case_triakinput_3.png

      components-use_case_triakinput_4.png

    • In the E:/photos/mongodb/step1 directory:

      components-use_case_tmongodbbulkload_1.png

      components-use_case_tmongodbbulkload_2.png

      components-use_case_tmongodbbulkload_3.png

      components-use_case_tmongodbbulkload_4.png

    • In the E:/photos/mongodb/step2 directory:

      components-use_case_tmongodbbulkload_5.png

      components-use_case_tmongodbbulkload_6.png

      components-use_case_tmongodbbulkload_7.png

      components-use_case_tmongodbbulkload_8.png

  5. In the Azure Storage folder field, enter the directory where you want to write files. This directory will be created in the container to be used if it does not exist. In this example, enter photos.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!