[
https://issues.apache.org/jira/browse/CASSANDRA-11588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15245314#comment-15245314
]
Alex Petrov edited comment on CASSANDRA-11588 at 4/18/16 8:45 AM:
------------------------------------------------------------------
The only reason for that was to make {{Value}} building a bit simpler (e.g.
calculating CellPath and preparing Values).
But I think you're right, there's no critical need for that. I'd probably wait
until {{7826}} is in a better shape. I'll reopen if I can find a better
motivation for that change.
was (Author: ifesdjeen):
The only reason for that was to make {{Value}} building a bit simpler (e.g.
calculating CellPath and preparing Values).
But I think you're right, there's no critical need for that. I'd probably wait
until {{7826}} is in a better shape. I'll reopen if I can find a better
motivation.
> Unify CollectionType#{getValuesType|getElementsType}
> ----------------------------------------------------
>
> Key: CASSANDRA-11588
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11588
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Fix For: 3.x
>
>
> Currently, {{ListType}} and {{SetType}} have {{getElementsType}}, while
> {{MapType}} has {{getValuesType}} (along with {{getKeysType}}).
> It might make sense to unify these types and make all three types have
> {{getValuesType}}, which would simply mean renaming for {{Set}} and {{List}}
> and pulling the method up to {{CollectionType}}. This would make
> [#7826|https://issues.apache.org/jira/browse/CASSANDRA-7826] a bit simpler.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
