[
https://issues.apache.org/jira/browse/CASSANDRA-9445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14588246#comment-14588246
]
Philip Thompson commented on CASSANDRA-9445:
--------------------------------------------
[~chengren311], I am unable to reproduce this with you schema against 2.0.15.
Since you encountered the issue on 2.0.4, you might best be served by upgrading
to the latest 2.0 series release. It is likely the issue you are running into
has been resolved.
> Read timeout on the tables where we recreated previously dropped column with
> different type
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-9445
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9445
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Cheng Ren
>
> We had 10%~20% read request timeout on one specific table in our cassandra
> cluster.
> This happened since we added the column to that table with type of
> map<text,text>, ran the pipeline against it adding data and then dropped the
> column and re-added it as a blob with the same name. The pipeline run to
> populate the blob data happened as the problem began.
> The issue got fixed as soon as we dropped the column.
> Any clue why this is happening ? is there any similar issue been reported
> with this kind of column change?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
