Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Data Integration Connectors
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Microsoft Azure Blob Storage V3 Connector
  3. Connections for Microsoft Azure Blob Storage V3
  4. Mappings for Microsoft Azure Blob Storage V3
  5. Data type reference
  6. Troubleshooting

Microsoft Azure Blob Storage V3 Connector

Microsoft Azure Blob Storage V3 Connector

Back Next

Microsoft Azure Blob Storage V3 sources in mappings

Microsoft Azure Blob Storage V3 sources in mappings

In a mapping, you can configure a Source transformation to represent a Microsoft Azure Blob Storage V3 object.
The following table describes the Microsoft Azure Blob Storage V3 source properties that you can configure in a Source transformation:
Property
Description
Connection
Name of the source connection. Select a source connection or click
New Parameter
 to define a new parameter for the source connection.
Source Type
Source type. Select one of the following types:
  • Single Object
  • Parameter: Select Parameter to define the source type when you configure the mapping task.
Object
Name of the source object.
You can drill-down and select an object from a sub-folder to fetch metadata from a particular object. When you run a task, the Secure Agent reads data from the container you specified either in connection properties or in the advance properties.
Parameter
Select an existing parameter for the source object or click
New Parameter
 to define a new parameter for the source object.
The
Parameter
 property appears only if you select Parameter as the source type.
Format
Specifies the file format that the Microsoft Azure Blob Storage V3 Connector uses to read data from Microsoft Azure Blob Storage.
You can select the following file format types:
  • Flat
  • Avro
  • Parquet
  • JSON
Default is
None
.
You must select the
Format Type
 as
None
 to read binary files.
For more information, see File formatting options.
The following table describes the Microsoft Azure Blob Storage V3 advanced source properties that you can configure in a Source transformation:
Property
Description
Number of concurrent connections to Blob Store
The number of concurrent connections to Blob Store to upload files. Default is 4.
Source Type
Select the type of source from which you want to read data. You can select the following source types:
  • File
  • Directory
Default is File.
Blob Name Override
Overrides the default file name.
Blob Container Override
Overrides the default container name.
When you read data from a directory and override the Blob container, ensure that files in the Blob container that you override with are not empty.
When you generate the SAS token at the container-level, the default container name and the container name that you specify for the container override must be the same.
Compression Format
Decompresses data when you read data from Microsoft Azure Blob Storage. You can decompress the data in the following formats:
  • None. Select None to decompress deflate and snappy file formats.
  • Gzip
  • Bzip2
  • Lzo
Default is None.
Tracing Level
Sets the amount of detail that appears in the log file.
You can choose terse, normal, verbose initialization, or verbose data.
Default is normal.
0 COMMENTS
We’d like to hear from you!
Erick Maps - March 14, 2023

I get this error when I try to read from v3 azure blob json file:

Cannot create read operation. All fields support write operation only

If I switch to string, it doesn't show

Informatica Documentation Team - March 15, 2023

Hi Eric Maps, 

If you are reading from a JSON file, ensure that you are using a single-line JSON file. You cannot read and write nested and multi-line indented JSON files. See the support statement covered in the following topic: Microsoft Azure Blob Storage V3 Connector
If you still face issues, you can contact Informatica Global Customer Support.

Thanks, 
Informatica Documentation Team