[jira] [Commented] (CASSANDRA-9426) Provide a per-table text-text map for storing extra metadata

2015-08-07 Thread Aleksey Yeschenko (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662659#comment-14662659
 ] 

Aleksey Yeschenko commented on CASSANDRA-9426:
--

Well, technically, you can put anything in a text column too (:

That said, the initial goal was to not even expose this via CQL, but have it 
available for internal consumers. I suggest in v1 we don't expose it.

 Provide a per-table text-text map for storing extra metadata
 -

 Key: CASSANDRA-9426
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9426
 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 maptext,text}} table param for just that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-9426) Provide a per-table text-text map for storing extra metadata

2015-08-07 Thread Tyler Hobbs (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14662225#comment-14662225
 ] 

Tyler Hobbs commented on CASSANDRA-9426:


Since this will likely end up being used in some interesting ways, maybe 
{{maptext, blob}} is a better choice?  It has the downside of being a little 
harder to inspect manually, but the upside is that we can allow anything to be 
stored there.

 Provide a per-table text-text map for storing extra metadata
 -

 Key: CASSANDRA-9426
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9426
 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 maptext,text}} table param for just that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-9426) Provide a per-table text-text map for storing extra metadata

2015-08-05 Thread Jeremiah Jordan (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658359#comment-14658359
 ] 

Jeremiah Jordan commented on CASSANDRA-9426:


Do you have a proposed syntax for setting values into the map from CQL?

 Provide a per-table text-text map for storing extra metadata
 -

 Key: CASSANDRA-9426
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9426
 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 maptext,text}} table param for just that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-9426) Provide a per-table text-text map for storing extra metadata

2015-08-05 Thread Aleksey Yeschenko (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658364#comment-14658364
 ] 

Aleksey Yeschenko commented on CASSANDRA-9426:
--

{{... WITH extensions = \{'anything': 'goes', 'here': 'too'\};}}

 Provide a per-table text-text map for storing extra metadata
 -

 Key: CASSANDRA-9426
 URL: https://issues.apache.org/jira/browse/CASSANDRA-9426
 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 maptext,text}} table param for just that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Commented] (CASSANDRA-9426) Provide a per-table text-text map for storing extra metadata

2015-08-05 Thread Blake Eggleston (JIRA)

[ 
https://issues.apache.org/jira/browse/CASSANDRA-9426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14658492#comment-14658492
 ] 

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: https://issues.apache.org/jira/browse/CASSANDRA-9426
 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 maptext,text}} table param for just that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)