[
https://issues.apache.org/jira/browse/CASSANDRA-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15241796#comment-15241796
]
Jim Witschey commented on CASSANDRA-11437:
------------------------------------------
Sorry for the delay, and thank you for the ping. I'm +1, looks great. I ran it
locally and on a parameterized job here:
http://cassci.datastax.com/view/Parameterized/job/parameterized_dtest_multiplexer/67/
> Make number of cores used for copy tasks visible
> ------------------------------------------------
>
> Key: CASSANDRA-11437
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11437
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Jim Witschey
> Assignee: Stefania
> Priority: Minor
> Labels: lhf
> Fix For: 3.x
>
>
> As per this conversation with [~Stefania]:
> https://github.com/riptano/cassandra-dtest/pull/869#issuecomment-200597829
> we don't currently have a way to verify that the test environment variable
> {{CQLSH_COPY_TEST_NUM_CORES}} actually affects the behavior of {{COPY}} in
> the intended way. If this were added, we could make our tests of the one-core
> edge case a little stricter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
