"ORDER BY" clause in schema breaks code generation

[relops]

"ORDER BY" clause in schema breaks code generation

[0x6e6562]

@jamesjackson - can you post the schema example that causes this issue so that I can take a look?

[jamesjackson]

Sure, here's one of the tables:

CREATE TABLE messages (
    subscriber_id text,
    msg_id timeuuid,
    msg text,
read boolean,
fav boolean,
    PRIMARY KEY(subscriber_id, msg_id)
) WITH CLUSTERING ORDER BY (msg_id DESC);

[0x6e6562]

Thanks for the example. I've just pushed a patch out that maps the type so that you can get going. The test schema now contains a CF definition with the reverse cluster order. I'm not sure whether any changes to the runtime are necessary, so I'm going to look at whether this needs its own test or not.

[0x6e6562]

OK, the test and build for this are passing so I think this issue is resolved for now - let me know if the latest version does not fix your issue.

[jamesjackson]

This looks great. Thanks !