Table of Contents

Search

  1. Preface
  2. Introduction to Amazon S3 V2 Connector
  3. Connections for Amazon S3 V2
  4. Amazon S3 V2 sources and targets
  5. Mappings and mapping tasks with Amazon S3 V2
  6. Migrating a mapping
  7. Upgrading to Amazon S3 V2 Connector
  8. Data type reference
  9. Troubleshooting

Amazon S3 V2 Connector

Amazon S3 V2 Connector

Rules and guidelines for creating a target

Rules and guidelines for creating a target

Consider the following rules and guidelines when you use the
Create Target
property:
  • The target name can contain alphanumeric characters. You can use only a period (.), an underscore (_), an at the rate sign (@), a dollar sign ($), and a percentage sign (%) special characters in the file name.
  • When you write an Avro, ORC, or Parquet file using
    Create Target
    and the target directory has a file name that contains a colon (:), the mapping fails.
  • If you specify a target name that already exists, you do not get a warning message. However, the Secure Agent overwrites the existing target with the same file name.
  • When you write an Avro, ORC, or Parquet file using the
    Create Target
    option, you cannot provide a Null data type.
  • When you configure the precision of a string column of a JSON file in the source and select
    Create Target
    , the default precision of the string column is retained.
  • When you select the file or directory source type, select
    Create New at Runtime
    , and run the mapping, the tomcat log shows the following exception even if the mapping succeeds:
    Internal error. Encountered an error because invalid path element [Partition] was encountered. Contact Informatica Global Customer Support.
  • When you run a mapping on the advanced mode with an Amazon S3 source, and create a new target object by selecting
    Create New at Runtime
    , the mapping is successful, but the special characters in the source are replaced by an underscore (_).
  • When you write data to a flat file created at runtime, the target flat file contains a blank line at the end of the file.
Rules and guidelines for the path in target object
Consider the following rules and guidelines when you specify a path in the
Create Target
property:
  • If you specify the path, the Secure Agent creates target object in the path you specify in this property and within the bucket that you specify in the
    Folder Path
    connection property. The Secure Agent creates target object in the following format:
    <bucket_name>/<path_name>/<target_object_name>
    .
  • The Secure Agent only considers the bucket and ignores the path you specify in the
    Folder Path
    connection property.
    For example, specify the path as
    folder1/folder2
    and target object name as
    Records
    . Specify
    <bucket_name>/folder3
    as the
    Folder Path
    in the connection property. The Secure Agent creates the target object in the following location:
    <bucket_name>/folder1/folder2/Records
    .
  • If you do not specify the path, the Secure Agent creates target object name within the bucket that you specify in the
    Folder Path
    connection property in the following format:
    <bucket_name>/<target_object_name>
    .
    For example, if you do not specify the path and specify the target object name as
    Records
    , the Secure Agent creates the target object within the bucket that you specify in the
    Folder Path
    connection property in the following location:
    <bucket_name>/Records
    .
  • Do not specify a bucket name in the path.
    • For mappings, if you specify a bucket name in the path, the bucket name is considered as a folder in the folder path. For example, if you specify the path as
      <bucket_name>/<path_name>
      ,
      <bucket_name>
      is considered as a folder.
    • For mappings in advanced mode, if you specify a bucket name in the path, the bucket name is ignored.

0 COMMENTS

We’d like to hear from you!