[
https://issues.apache.org/jira/browse/CASSANDRA-7789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tyler Hobbs updated CASSANDRA-7789:
-----------------------------------
Attachment: 7789-alternate.txt
I think the original patch is quite a bit more complex than it needs to be. I
would prefer to not add another dependency. Also, I'm not sure that there is
value in separating read speeds from write speeds (since they closely limit
each other).
I'm attaching an alternate patch that takes a much simpler approach.
While testing, I also noticed that CTRL-C can't stop the import process anymore
(due to fun Python multithreading behavior). To fix that, I think we'll need
the main thread to do a bit of busy waiting. I'll open a separate ticket for
that.
> cqlsh COPY Command should display progress
> ------------------------------------------
>
> Key: CASSANDRA-7789
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7789
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Michaël Figuière
> Assignee: Mikhail Stepura
> Priority: Minor
> Labels: cqlsh
> Fix For: 2.1.1
>
> Attachments: 7789-alternate.txt, CASSANDRA-2.1-7789.patch
>
>
> While CASSANDRA-7405 is on its way to make the {{COPY}} command much faster,
> it's still likely to hang for many minutes when transferring a large amount
> of data.
> This gives the feeling to the newcomers that something went wrong. Even if
> the user expect cqlsh to hang for a long moment, it's not very convenient as
> you have no idea of when the copy will be complete.
> I believe it would be very pleasant if the {{COPY}} command could display an
> in-place progress output while it's executed with probably:
> * Rows copied
> * avg Rows/s
> * CSV File R/W MB
> * avg CSV File R/W MB/s
--
This message was sent by Atlassian JIRA
(v6.2#6252)
