> But CQL3 doesn't provide a way for this.
That's not true. But the syntax is probably a bit more verbose than what you
were hoping for. Your example (where I assume user_name is you partition key)
can be achieved with:
UPDATE users SET password = 'aaaaaa' WHERE user_name='xamry' USING TTL 44444;
UPDATE users SET gender = 'm' WHERE user_name='xamry' USING TTL 11111;
UPDATE users SET state = 'UP' WHERE user_name='xamry' USING TTL 66666;
Granted that is a tad verbose, but in term of the actual query performed this
is *absolutely* equivalent to what you would do in thrift.
So should we provide a shorter syntax to achieve this? It's worth discussing
and nobody said CQL3 is not meant to evolve. Though my initial opinion on this
is that setting different TTL on different columns in the same CQL3 row and the
same query is probably not all that common overall, so I'm not totally
convinced it's worth adding complexity to the syntax for such a shortcut (yes,
a shorter syntax would mean less bytes to transfer to the server for the query
and less to parse but if you care about performance you should be using
prepared statement which makes that issue moot).