[
https://issues.apache.org/jira/browse/CASSANDRA-9304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15009674#comment-15009674
]
Tyler Hobbs commented on CASSANDRA-9304:
----------------------------------------
The code changes in the latest commit look good to me. As far as the failure
injection testing goes, you can make it more deterministic -- I was just using
{{random()}} for exploratory testing. For example, have one environment
variable that specifies a number of query failures for a single token range.
Then, if the token range you're handling includes a particular token, fail the
query the specified number of times. This would allow us to test both the case
where the failures are less than {{max_attempts}} and the case where they are
more than {{max_attempts}}. You could use a similar approach with a second
environment variable for child process failure. I know this will make the code
a touch uglier, but I think it's worth it for the improved testability.
> COPY TO improvements
> --------------------
>
> Key: CASSANDRA-9304
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9304
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jonathan Ellis
> Assignee: Stefania
> Priority: Minor
> Labels: cqlsh
> Fix For: 2.1.x, 2.2.x, 3.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)
