[
https://issues.apache.org/jira/browse/CSV-253?focusedWorklogId=523306&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-523306
]
ASF GitHub Bot logged work on CSV-253:
--------------------------------------
Author: ASF GitHub Bot
Created on: 11/Dec/20 21:02
Start Date: 11/Dec/20 21:02
Worklog Time Spent: 10m
Work Description: divijvaidya commented on pull request #51:
URL: https://github.com/apache/commons-csv/pull/51#issuecomment-743425288
Hi @lbruun
Are you planning to work on this PR? I was wondering what was it that is
left to do here.
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 523306)
Time Spent: 40m (was: 0.5h)
> 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
> Attachments: 2019-10-30 20_31_39-Apache Commons CSV 1.8-SNAPSHOT
> API.png, Parser-setting-absentIsNull-Javadoc.png
>
> Time Spent: 40m
> 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)
