Is this a bug in the DataParser?

CloverDX Platform
1

This file does not parse using the standard DataReader:

col1,colb
f,4
0,7

This however does parse (note the missing trailing 4 on the first record):

col1,colb
f,
0,7

The error message I get is:

Parsing error: Unexpected record delimiter, probably record has too few fields. in field # 2 of record # 1, value: 'f,4
'

What it looks like is happening is that I’m getting to the last record and the data in the field buffer is “4\r\n” and it doesnt recognize that 4 is a field value and then the delimiter, it just assumes the whole thing is the delimiter and dies since it thinks its missing the last field.

I have seen similar cases where the \r\n at the end of a line is not recognized and the last value of one record is concatenated with the first value of the next record and that completely throws off parsing.

The data is a CSV created on a windows machine. The delimiter on the last field of my metadata is defined as delimiter=“,\\|;\\|:” and the rest are delimiter=“,” and the Record element itself declares: fieldDelimiter=“,” recordDelimiter=“\n”

Is this a bug, or have I just not yet hit upon the magical incantation for actually getting delimited data to parse?

This is with Clover 3.1.0.

2

Hello Mike,
I tried it with following metadata:

<Metadata id="Metadata1" previewAttachmentCharset="ISO-8859-1">
<Record fieldDelimiter="," name="sample_txt" previewAttachmentCharset="ISO-8859-1" recordDelimiter="\n" type="delimited">
<Field delimiter=",\\|;\\|:" name="cola" type="string"/>
<Field name="colb" type="string"/>
</Record>

And the parsing works properly. Of course there is unneeded /r on the end in the last field, but the exception is not thrown.