Table of Contents

Search

  1. Preface
  2. Introduction to Big Data Streaming
  3. Big Data Streaming Configuration
  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: Data Type Reference
  10. Appendix C: Sample Files

Big Data Streaming User Guide

Big Data Streaming User Guide

Microsoft Azure Data Lake Store Connection Properties

Microsoft Azure Data Lake Store Connection Properties

When you set up a Microsoft Azure Data Lake Store connection, you must configure the connection properties.
The following table describes the Microsoft Azure Data Lake Store connection properties:
Property
Description
Name
The name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters: ~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
ID
String that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection.
Default value is the connection name.
Description
The description of the connection. The description cannot exceed 4,000 characters.
Location
The domain where you want to create the connection.
Type
The connection type. Select Microsoft Azure Data Lake Store.
The following table describes the properties for metadata access:
Property
Description
ADLS Account Name
The name of the Microsoft Azure Data Lake Store.
ClientID
The ID of your application to complete the OAuth Authentication in the Active Directory.
Client Secret
The client secret key to complete the OAuth Authentication in the Active Directory.
Directory
The Microsoft Azure Data Lake Store directory that you use to read data or write data. The default is root directory.
AuthEndpoint
The OAuth 2.0 token endpoint from where access code is generated based on based on the Client ID and Client secret is completed.
For more information about creating a client ID, client secret, and auth end point, contact the Azure administrator or visit the Microsoft Azure website at the following link:

0 COMMENTS

We’d like to hear from you!