considering:
row size large or not
update a lot or not - update is insert actually
read heavy or not
overall read performance
if row size large , you may consider table:user_detail , add column id in
all tables.
In application side, merge/join by id.
But paid read price, 2nd query to user_de
How many rows in average per partition? around 10K. Let me get this straight :
You are bifurcating your partitions on either email or username , essentially
potentially doubling the data because you don’t have a way to manage a central
system of record of users ? We are just analyzing output log
How many rows in average per partition?
Let me get this straight : You are bifurcating your partitions on either email
or username , essentially potentially doubling the data because you don’t have
a way to manage a central system of record of users ?
I would do this: (my opinion)
Migrate to a
