[
https://issues.apache.org/jira/browse/CASSANDRA-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625254#comment-13625254
]
Sylvain Lebresne commented on CASSANDRA-5378:
---------------------------------------------
I'm not sure what you are talking about. The example above have always worked
and does not require the row key to be added to the indexedNames (which is an
addition of this patch). The row key is "primarily" indexed but it's not
indexed by a secondary index. And adding a secondary index on the row key is
not something supported (largely because it would be useless).
So anyway, I have removed that line in commit
69f05a704aafa90f2151db721312f3c5907abb2f if only because that restore the
behavior of before that patch and let all cql dtests pass. If you still think
there is a problem, please open a separate issue with a test case showing the
problem you are talking about.
> Fat Client: No longer works in 1.2
> ----------------------------------
>
> Key: CASSANDRA-5378
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5378
> Project: Cassandra
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Carl Yeksigian
> Assignee: Carl Yeksigian
> Labels: client
> Fix For: 1.2.4
>
> Attachments: 5378-1.2.txt, 5378.txt, 5378-v2.txt
>
>
> The current client only example doesn't compile. After doing some updates,
> the fat client still won't work, mainly because the schema is not being
> pushed to the fat client.
> I've made changes to the client to support CQL3 commands, to the
> ServiceManager to wait until a migration has completed before starting the
> client, and to the MigrationManager to not try to pull schemas from a fat
> client.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
