Troubleshooting UNLOAD from Timestream for LiveAnalytics

S3 Key length

UNLOAD result file key when using the S3 prefix [%s] provided in the destination will exceed the S3 allowed key length. See documentation for more details.

When exporting query results using the UNLOAD statement, the S3 key length, comprising of sum of the length of S3 bucket name and prefix exceeds the maximum supported S3 key length. We recommend to reduce your prefix or bucket name length.

UNLOAD result file key when using partitioned_by [%s] will exceed the S3 allowed key length. See documentation for more details.

When exporting query results using the UNLOAD statement, the S3 Key length using the partitioned_by column exceeds the maximum supported S3 key length. We recommend to partition with an alternate column or reduce the length of the partitioned_column (if feasible).

UNLOAD result file key when using the S3 prefix [%s] along with the partitioned_by [%s] will exceed the S3 allowed key length. See documentation for more details.

When exporting query results using the UNLOAD statement, the S3 Key length, comprising of sum of the length of S3 bucket name, the prefix, and the partitioned_by column name exceeds the maximum supported S3 key length. We recommend to reduce your prefix, bucket name length, or use an alternate column to partition your data.

The generated S3 object key: %s is too long. See documentation for more details.

While processing your query using the UNLOAD statement, one of the values in the partitioned column exceeds the maximum supported S3 key length. The partition column and value can be found in the object key generated.

S3 throttles

We have detected that Amazon S3 is throttling the writes from UNLOAD command. See Amazon Timestream documentation for more information

Refer to S3 documentation here. S3 API call rate could be throttled when multiple readers/writers access the same folder. Please audit the call volume to the bucket provided. If you are using same bucket for multiple concurrent UNLOAD queries, try using different buckets for the same. If you are using same bucket for multiple operations other than Timestream for LiveAnalytics UNLOAD, consider moving UNLOAD results to separate bucket.