You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when user records with random partition keys are aggregated - they are sent to different shards as expected.
But the partition key of a "parent" / "container" record always equals "a". Thus, it's not possible to effectively use AWS Lambda Kinesis event source with a parallelization option called "Concurrent batches per shard" > 1, because records with the same partition key are read sequentially.
Is it possible to set a random partition key for the "parent" / "container" record?
Thank you
The text was updated successfully, but these errors were encountered:
Hello,
Currently, when user records with random partition keys are aggregated - they are sent to different shards as expected.
But the partition key of a "parent" / "container" record always equals "a". Thus, it's not possible to effectively use AWS Lambda Kinesis event source with a parallelization option called "Concurrent batches per shard" > 1, because records with the same partition key are read sequentially.
Is it possible to set a random partition key for the "parent" / "container" record?
Thank you
The text was updated successfully, but these errors were encountered: