[ https://issues.apache.org/jira/browse/CSV-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory updated CSV-182: ----------------------------- Attachment: commons-csv-182.diff > Allow some printing operations directly from CSVFormat > ------------------------------------------------------ > > Key: CSV-182 > URL: https://issues.apache.org/jira/browse/CSV-182 > Project: Commons CSV > Issue Type: Improvement > Components: Printer > Affects Versions: 1.3 > Environment: Apache Maven 3.3.9 > (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T08:41:47-08:00) > Maven home: E:\Java\apache-maven-3.3.9\bin\.. > Java version: 1.7.0_79, vendor: Oracle Corporation > Java home: C:\Program Files\Java\jdk1.7.0_79\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows" > Reporter: Gary Gregory > Assignee: Gary Gregory > Fix For: 1.4 > > Attachments: commons-csv-182.diff > > > Over in Apache Log4j-land, we are working on a GC-free logging epic. > We try hard to generate as few objects as possible. Right now, we create one > CSVPrinter per logging event to create a CSV line for that event. > In order to get the best memory profile and performance, this ticket proposes > to refactor the CSVPrinter and CSVFormat objects to allow a subset of print > operations directly from the CSVFormat object. > I tested this patch with the Log4j Git master and it works. -- This message was sent by Atlassian JIRA (v6.3.4#6332)