[
https://issues.apache.org/jira/browse/CSV-253?focusedWorklogId=620591&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-620591
]
ASF GitHub Bot logged work on CSV-253:
--------------------------------------
Author: ASF GitHub Bot
Created on: 08/Jul/21 16:38
Start Date: 08/Jul/21 16:38
Worklog Time Spent: 10m
Work Description: garydgregory commented on pull request #51:
URL: https://github.com/apache/commons-csv/pull/51#issuecomment-876585336
commit ac280e705d99cc1168f93f7d9a5f92618bebbb97
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 620591)
Time Spent: 1h 50m (was: 1h 40m)
> Handle absent values in input (null)
> ------------------------------------
>
> Key: CSV-253
> URL: https://issues.apache.org/jira/browse/CSV-253
> Project: Commons CSV
> Issue Type: Improvement
> Components: Parser
> Reporter: Lars Bruun-Hansen
> Priority: Major
> Fix For: 1.9.0
>
> Attachments: 2019-10-30 20_31_39-Apache Commons CSV 1.8-SNAPSHOT
> API.png, Parser-setting-absentIsNull-Javadoc.png
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> The parser must be able to handle absent values in input and translate that
> into {{null}} as required. I see several tickets on this matter in the
> history, but none seem to have addressed the issue, at least not for parsing.
> For this problem, I see a need to introduce a new term:
> Definition: _Absent value_ is when there are zero characters between field
> delimiters.
> Specifically the aim is to be able to parse the following:
> {noformat}
> "John",,"Doe" // 2nd element is absent
> ,"AA",123 // 1st element is absent
> "John",90, // 3rd element is absent
> "",,90 // 2nd element is absent (1st element isn't)
> {noformat}
>
> See also CSV-93 which I think never addressed the issue, probably because the
> reporter was happy with having the issue fixed for CSV output, not for
> parsing.
> A PR is coming...
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
