Controlling Object Sizes | Teradata Access Module for GCS - Controlling Object Sizes - Access Module

Teradata® Tools and Utilities Access Module Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
VMware
Enterprise
IntelliFlex
Lake
Product
Access Module
Release Number
20.00
Published
October 2023
ft:locale
en-US
ft:lastEdition
2025-11-21
dita:mapPath
cya1691484517272.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
hjf1479308836950
Product Category
Teradata Tools and Utilities

This parameter applies only for write operations to GCS. The value of MaxObjectSize can be an integer or an integer followed by, without a space, one of the following multipliers:

  • k (1000)
  • K (1024)
  • m (1000*1000)
  • M (1024*1024)

MaxObjectSize can be used to cause the access module to restrict the size of the object. For example, MaxObjectSize=100m will cause access module to close the current object when it got to 100,000,000 bytes, and then open a new object. The access module will always write an integral number of TPT buffers, so objects may be closed somewhat before the specified size is reached.

The naming convention for the objects changes when MaxObjectSize is used. Each object will be renamed to:

<object-name>-xxx

where xxx is a sequential 3-digit number, beginning with 001.

If the object name has a file extension, the 3-digit number will be appended to the base name, prior to the extension:

<object-name>-xxx.<extension>

If the object name has more than one extension (for example, mydata.csv.gz) the sequential number is appended to the base name, prior to the first file extension (for example, mydata-001.csv.gz).