Table of Contents

Search

  1. Preface
  2. Introduction to Informatica Data Engineering Integration
  3. Mappings
  4. Mapping Optimization
  5. Sources
  6. Targets
  7. Transformations
  8. Python Transformation
  9. Data Preview
  10. Cluster Workflows
  11. Profiles
  12. Monitoring
  13. Hierarchical Data Processing
  14. Hierarchical Data Processing Configuration
  15. Hierarchical Data Processing with Schema Changes
  16. Intelligent Structure Models
  17. Blockchain
  18. Stateful Computing
  19. Appendix A: Connections Reference
  20. Appendix B: Data Type Reference
  21. Appendix C: Function Reference

Kudu Connection Properties

Kudu Connection Properties

Use a Kudu connection to access Kudu.
The order of the connection properties might vary depending on the tool where you view them.
You can create and manage a Kudu connection in the Administrator tool or the Developer tool. The following table describes the Kudu 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 Kudu.
The following table describes the properties for metadata access:
Property
Description
Kudu Master URLs
The URLs of the Kudu master tables.
Kudu Library Version
The version number of the Kudu library.
Cluster Configuration
The Hadoop cluster that you use for the connection.

0 COMMENTS

We’d like to hear from you!