[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180627#comment-13180627
]
Eric Evans commented on CASSANDRA-2474:
---------------------------------------
bq. -0 here, I don't think it really provides anything other than a CYA for us.
("We TOLD you it was experimental, you even had to turn on the option!")
Otherwise it's common sense that new-this-release features are going to be less
stable
I don't think it's about CYA, I see it as setting a clear expectation.
IMO (and recent experience bares this out), we can't in any confidence
introduce a new CQL feature like this without learning something after the
fact, and wishing we could go back and do it differently (or flat having no
choice). By that point, the Cat is out of the bag. Either we live with it
(and provide repeated explanations), or we fix it. Both of which are sources
of frustrations for users.
Some would say (have said) that we should do better QA to avoid this happening,
but there is only so much you can do without wider testing, and unfortunately
beta releases just don't cut it.
An experimental mode let's us Smoke Test a new feature like this while being
honest with our users that that's what we're doing. If we need to make
breaking changes, it gives us the freedom to do it (in this case without a CQL
major bump), because we've set that expectation. Users who value stability
were spared those landmines.
bq. ...it doesn't do much besides leave people just that much frustrated when
they go to try feature X and have to edit-and-bounce their server first.
I understand you probably meant s/edit-and-bounce/anything/, but we could also
make this settable though JMX and add a {{nodetool}} command for it (making a
skooch easier).
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Sylvain Lebresne
> Labels: cql
> Fix For: 1.1
>
> Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG,
> 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG,
> raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg
>
>
> For the most part, this boils down to supporting the specification of
> compound column names (the CQL syntax is colon-delimted terms), and then
> teaching the decoders (drivers) to create structures from the results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
