let's say I have a table like this
CREATE TABLE request( transaction_id text, request_date timestamp, data text, PRIMARY KEY (transaction_id) );
The transaction_id is unique, so as far as I understand each partition in this table would have one row only and I'm not sure if this situation causes a performance issue in the OS, maybe because Cassandra creates a file for each partition causing lots of files to manage for its hosting OS, as a note I'm not sure how Cassandra creates its files fot its tables.
In this scenario I can find a request by its transaction_id like
select data from request where transaction_id = 'abc';
If the previous assumption is correct, a different approach could be the next one?
CREATE TABLE request( the_date date, transaction_id text, request_date timestamp, data text, PRIMARY KEY ((the_date), transaction_id) );
The field the_date would change every next day, so the partitions in each table would change for each day.
In this scenario I would have to have the_date data always available to the client so I can find a request using the next query
select data from request where the_date = '2020-09-23' and transaction_id = 'abc';
Thank you in advance for your kind help!