cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-9304) COPY TO improvements
Date Tue, 20 Oct 2015 09:28:27 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964855#comment-14964855
] 

Stefania commented on CASSANDRA-9304:
-------------------------------------

[~thobbs] I've resumed this today, sorry for the delay. To retry in {{err_callback()}} when
we get an {{OperationTimedOut}}, we either have to create a fresh new query being careful
to avoid passing data for the pages that we already retrieved, or use the protected methods
and properties of {{ReponseFuture}} to retry the current page, which is more efficient. Do
you have any preferences? We should perhaps go with the second choice and log a driver enhancement
request? Ideally the retry policy should cover {{OperationTimedOut}} as well, so we only have
one path of execution?

> COPY TO improvements
> --------------------
>
>                 Key: CASSANDRA-9304
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9304
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Stefania
>            Priority: Minor
>              Labels: cqlsh
>             Fix For: 3.x, 2.1.x, 2.2.x
>
>
> COPY FROM has gotten a lot of love.  COPY TO not so much.  One obvious improvement could
be to parallelize reading and writing (write one page of data while fetching the next).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message