Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Big segments, seperate DynamoDB tables per environement and autoconfiguration #199

Closed
hughevans opened this issue Jul 27, 2022 · 3 comments

Comments

@hughevans
Copy link

Big segment data does not populate the DynamoDB when you use this configuration combination:

  1. Autoconfiguration and supplying ENV_DATASTORE_TABLE_NAME="table-name-$CID"
  2. USE_DYNAMODB="true"

You end up with this in the logs:

BigSegmentSynchronizer: Synchronization failed: InvalidParameter: 1 validation error(s) found.
- minimum field size of 3, GetItemInput.TableName.

That’s an AWS error from calling DynamoDB GetItem with a blank TableName.

I think the issue is that on this line you’re using the table name from allConfig and not envConfig.

Apart from the big segments everything else has been functioning fine with this Relay Proxy.

Perhaps big segments only works with DynamoDB if you use a single table for all environments?

@eli-darkly
Copy link
Contributor

That does look like a mistake - thanks for reporting it. We'll look into it and if that's right, it should be a simple fix that we can release a patch for soon.

@eli-darkly
Copy link
Contributor

The 6.7.12 release should fix this. I'll close the issue but please feel free to reopen if you still see a similar issue.

@hughevans
Copy link
Author

Thanks @eli-darkly! Really appreciate the fast response!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants