Allow to override Keyspace in schema

[pierreis]

Currently, the keyspace is defined once and for all in the ORM initial configuration.

Sometimes, in order to accommodate with different workloads, some data must be treated differently from some other, requiring its storage in different keyspaces.
One example of such cases would be logs requiring lower replication than live data, or a replication in a datacenter running data analytics.

Although it is obviously possible today to create two ORM instances to accommodate these different keyspaces, it is unpractical and is less and less as the number of keyspaces grows.

Would it be possible to add a keyspace option in the schema configuration, allowing to override the keyspace on a per-table basis?

[guharajan]

Is this support available now ?