[
https://issues.apache.org/jira/browse/CASSANDRA-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne updated CASSANDRA-1054:
----------------------------------------
Attachment: 0001-Removing-unused-and-wrongly-set-isSuper-flag-in-cfst.patch
> isSuper flag in cfstore is wrongly set in 0.7
> ---------------------------------------------
>
> Key: CASSANDRA-1054
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1054
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 0.7
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Priority: Trivial
> Fix For: 0.7
>
> Attachments:
> 0001-Removing-unused-and-wrongly-set-isSuper-flag-in-cfst.patch
>
>
> In 0.7, following CASSANDRA-16, the isSuper in ColumnFamilyStore is not set
> correctly (if I'm correct).
> This is because when the model is applied (AddColumnFamily.applyModels()) the
> columnFamilyStore
> is created before the call to DataDescriptor.setTableDefinition. But the
> createColumnFamilyStore()
> function retrieve the columnType. This thus always return a null that end up
> in a "Super".equals(null)
> that always sets the flag to false.
> That being said, the isSuper flag of columnFamilyStore is never used.
> I propose thus to get ride of this flag completely since if needed in the
> future, the column type can
> always be retrieved from the table and cfname directly (the attached patch do
> just that).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
