Skip to content

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

@hughevans

Description

@hughevans

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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions