[
https://issues.apache.org/jira/browse/CASSANDRA-11437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15215243#comment-15215243
]
Stefania commented on CASSANDRA-11437:
--------------------------------------
Let's fix this after CASSANDRA-11320 is committed, a static {{printdebug()}}
method would be really handy and 11320 introduces it.
> 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: Bug
> Reporter: Jim Witschey
> Assignee: Stefania
> Priority: Minor
>
> 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)
