Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

EndpointS3Settings missing TimestampColumnName setting

See original GitHub issue

Hello!

Vote on this issue by adding a 👍 reaction
To contribute a fix for this issue, leave a comment (and link to your pull request, if you’ve opened one already)

Issue details

The TimestampColumnName parameter was added in DMS versions 3.1.4 and later, but is not available to be set as an s3 Endpoint setting using Pulumi. See: https://docs.aws.amazon.com/dms/latest/APIReference/API_S3Settings.html

Steps to reproduce

Attempt to create an s3 target endpoint using the following s3_setting: “timestamp_column_name”: “SomeColumnName”

Expected: The endpoint is updated with the Timestamp Column Name. Actual: Pulumi produces this error:

error: aws:dms/endpoint:Endpoint resource 'xxxxx' has a problem: Invalid or unknown key. Examine values at 'Endpoint.S3Settings.TimestampColumnName'.

Issue Analytics

State:
Created 2 years ago
Reactions:1
Comments:8 (1 by maintainers)

Top GitHub Comments

2reactions

casey-robertson-paypalcommented, Sep 19, 2022

This is supported by AWS. In fact I’m running into issues with terraform because while the API and Terraform docs show it as optional, the AWS API keeps telling me InvalidParameterValueException: TimestampColumnName cannot be an empty string.

1reaction

casey-robertson-paypalcommented, Oct 17, 2022

I haven’t solved it. I just had to add a timestamp column and worked with our data lake to team to ignore it in their ingest and/or use this new column as their timestamp instead of a derived one. It’s not the end of the world but it seems clear that something is amiss with the APIs and their stated allowed configurations

Top Results From Across the Web

S3Settings - AWS Database Migration Service

Setting ParquetTimestampInMillisecond has no effect on the string format of the timestamp column value that is inserted by setting the TimestampColumnName ...