So I just saw a post about how Kundera translates all JPQL to CQL.
On Mon, Oct 21, 2013 at 4:45 PM, Jon Haddad wrote:
> If you're working with CQL, you don't need to worry about the column
> names, it's handled for you.
>
> If you specify multiple keys as part of the primary key, they become
>
What if you plan on using Kundera and JPQL and not CQL?
Les
On Oct 21, 2013 4:45 PM, "Jon Haddad" wrote:
> If you're working with CQL, you don't need to worry about the column
> names, it's handled for you.
>
> If you specify multiple keys as part of the primary key, they become
> clustering key
If you're working with CQL, you don't need to worry about the column names,
it's handled for you.
If you specify multiple keys as part of the primary key, they become clustering
keys and are mapped to the column names. So if you have a sensor_id /
time_stamp, all your sensor readings will be i
So looking at Patrick McFadin's data modeling videos I now know about using
compound keys as a way of partitioning data on a by-day basis.
My other questions probably go more to the storage engine itself. How do
you refer to the columns in the wide row? What kind of names are assigned
to the colum
Please correct me if I'm not describing this correctly. But if I am
collecting sensor data and have a table defined as follows:
create table sensor_data (
sensor_id int,
time_stamp int, // time to the hour granularity
voltage float,
