commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <>
Subject [jira] [Work logged] (CSV-253) Handle absent values in input (null)
Date Mon, 28 Oct 2019 21:33:00 GMT


ASF GitHub Bot logged work on CSV-253:

                Author: ASF GitHub Bot
            Created on: 28/Oct/19 21:32
            Start Date: 28/Oct/19 21:32
    Worklog Time Spent: 10m 
      Work Description: coveralls commented on issue #51: [CSV-253] Handle absent values in
   [![Coverage Status](](
   Coverage increased (+0.1%) to 93.032% when pulling **0f441a395907eb87063d2de1848b091fa8f76e80
on lbruun:null-handling** into **53be2154bf5488f2860c425d8a445f4338679e66 on apache:master**.
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:

Issue Time Tracking

    Worklog Id:     (was: 335206)
    Time Spent: 20m  (was: 10m)

> Handle absent values in input (null)
> ------------------------------------
>                 Key: CSV-253
>                 URL:
>             Project: Commons CSV
>          Issue Type: Improvement
>          Components: Parser
>            Reporter: Lars Bruun-Hansen
>            Priority: Major
>          Time Spent: 20m
>  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

View raw message