Hey guys, i saw that as of R78 - Kinesis partition keys were set to random (unless specified for using IP address in config). I was wondering if you guys ever thought about using one of the ID’s instead, to guarantee event order by user.
I understand the argument for flooding by one user/IP/etc. packing a shard full, but seems like a high price to pay by randomly assigning and losing guaranteed order by user.
We were having a discussion similar to Uber/Lyft and taxi rides by user, and if events got out of sync, it would def. muddy up the waters on who rode in what cab to where and which driver.
I saw @alex had a thought of allowing a configurable partition key using Kinesis Tee - have you thought about or can you provide reasoning behind not having that option in stream enrich and sink?