You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2016/01/19 04:29:39 UTC

[jira] [Commented] (CSV-143) CSVPrinter ill-suited in multithreaded environment

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

Gary Gregory commented on CSV-143:
----------------------------------

In order call the Appendable once, we'd need to buffer our writes to a buffer, which would be slower and fatter. I still could see a subclass specializing in a thread-safe implementation. Patches welcome.

> CSVPrinter ill-suited in multithreaded environment
> --------------------------------------------------
>
>                 Key: CSV-143
>                 URL: https://issues.apache.org/jira/browse/CSV-143
>             Project: Commons CSV
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Andras Sereny
>
> CSVPrinter doesn't support multiple threads writing to the same appendable. The class itself is not thread safe and, what's worse, it also invalidates any thread-safety guarantees provided by the underlying appendable, as in one CSVPrinter.print method there are multiple calls to out.append.
> OpenCSV does better here: in CSVWriter.writeNext there is one single call to PrintWriter.writer, thus it conveniently propagates PrintWriter thread-safety.



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