cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake Eggleston (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9426) Provide a per-table text->text map for storing extra metadata
Date Wed, 05 Aug 2015 16:48:06 GMT


Blake Eggleston commented on CASSANDRA-9426:

What about something like {code}... WITH EXTENSION anything = goes AND EXTENSION something_else
= {'a':'b', 'c': 'd'}{code}

I don't think you'd need to change the way they're stored in the schema table, but this would
make ddl statements easier to read/write when working with more than one extension. It would
also let you do alter statements on individual extensions without having to include the entire
extensions map.

Also, would this add hooks for validating the extension key value pairs?

> Provide a per-table text->text map for storing extra metadata
> -------------------------------------------------------------
>                 Key: CASSANDRA-9426
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Aleksey Yeschenko
>            Assignee: Sam Tunnicliffe
>              Labels: client-impacting
>             Fix For: 3.0 beta 1
> For some applications that build on Cassandra it's important to be able to attach extra
metadata to tables, and have it be distributed via regular Cassandra schema paths.
> I propose a new {{extensions map<text,text>}} table param for just that.

This message was sent by Atlassian JIRA

View raw message