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 Engineering Streaming 10.4.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Introduction to Data Engineering Streaming
  3. Data Engineering Streaming Administration
  4. Sources in a Streaming Mapping
  5. Targets in a Streaming Mapping
  6. Streaming Mappings
  7. Window Transformation
  8. Appendix A: Connections
  9. Appendix B: Monitoring REST API Reference
  10. Appendix C: Sample Files

User Guide

User Guide

Back Next

FileName Port in ADLS Gen2

FileName Port in ADLS Gen2

When you create a data object read or write operation for Microsoft Azure Data Lake Store Gen2 (ADLS Gen2) files, the FileName port appears by default.
When the Spark engine writes to ADLS Gen2 files using a FileName port, it uses the following process to write the data:
  1. The Data Integration Service creates separate directories for each value in the FileName port and adds the target files within the directories.
  2. The file rollover process closes the current file to which data is being written to and creates a new file based on the configured rollover value.
    Effective in 10.4.1, you can configure the following rollover parameters at the design-time based on time and size:
    • Stream Rollover Time in Hours. Specify the rollover time in hours for a target file when a certain period of time has elapsed.
    • Stream Rollover Size in GB. Specify the size in GB for a target file when the target file reaches a certain size.
    Technical preview functionality is supported for evaluation purposes but is unwarranted and is not production-ready. Informatica recommends that you use in non-production environments only. Informatica intends to include the preview functionality in an upcoming release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.
  3. When a target file reaches the configured rollover value, the target file is rolled over and moved to the specified ADLS Gen2 target location.
  4. The Spark engine creates sub-directories in the specified ADLS Gen2 target location for each value in the FileName port.
  5. The Spark engine moves the rolled over target files to the sub-directories created for each value in the FileName port in the ADLS Gen2 target location.
You can configure both rollover schemes for an ADLS Gen2 target file. The Spark engine rolls over to based on the first event that triggers. For example, if you configure rollover time to 1 hour and rollover size to 1 GB, the target service rolls the file over when the file reaches a size of 1 GB even if the 1 hour period has not elapsed.
0 COMMENTS
We’d like to hear from you!