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 reading from and writing to a partition folder

Rules and guidelines for reading from and writing to a partition folder

Consider the following rules and guidelines when you read from and write to a partition folder:
  • You must import a directory that contains only partition folders and select the source type as
    Directory
    in the advanced source property.
  • If you import a partition directory that does not have data, a validation error is encountered.
  • If you import a partition directory that contains only files but no partition folders, a validation error is encountered.
  • If you import a partition directory that has a partition folder but no files in the partition folder, a validation error is encountered.
  • You can read data from or write data to partition folders with Avro, Parquet, and Orc files.
  • The FileName field has 0 as the partition order.
  • The partitioned directory that you select cannot have a partitioned column named FileName. The name is case insensitive.
  • When you import an existing target object or create a new target object with a partition directory, the FileName field does not appear for the target objects. The FileName field appears only when you import the source objects.
  • You can push down a Filter transformation on a partition column for an Amazon S3 source.
  • When you pass a timestamp value in a partition column, the value gets encoded. For example,
    03:26:01
    gets encoded as
    03%3A26%3A01
    .
  • When you pass a value with special characters in a partition column, the value gets encoded. For example,
    @#$#$%%?*
    gets encoded as
    @%23$%23$%25%25%3F%2A
    .
  • When you import a directory that has a partition folder, the data type for the partition column is imported as a String.
  • You cannot edit the data type for a partition column.
  • You cannot use columns of hierarchical data type as partition columns.
  • You cannot use the
    Edit Metadata
    option with partition columns.
  • You cannot use the
    View Schema
    option for a partition directory at source and target side.
  • You cannot use the
    Import from Schema File
    option for partition directory at source because the schema file does not have information for partition columns.
  • You cannot use the
    Data Preview
    option with partition columns.
  • You cannot select the partition columns in a mapping task if the target object is parameterized.
  • For
    Create Target
    , you can add partition fields and arrange the partition columns in an order. You cannot add partition fields and arrange the partition columns in an order for an existing target.
  • At
    Create Target
    , the
    Label
    column in the
    Partitions
    tab denotes the partition column name.
  • When you import an Amazon S3 object that has partition columns, the partition fields are listed at the end of the list.
  • If a partition column contains data that has more than 255 characters, the data is truncated and only 255 characters are written in the partition column.
  • If a partition column name contains more than 74 characters, the name is truncated and only 74 characters are written in the partition column name.
  • The value of the partition directory file path formed using the combination of the partition column name and the target file within the partition directory must not exceed 1024 characters. Otherwise, the mapping will fail.

0 COMMENTS

We’d like to hear from you!