[ 
https://issues.apache.org/jira/browse/TIKA-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17888301#comment-17888301
 ] 

Tim Allison edited comment on TIKA-4278 at 10/10/24 2:03 PM:
-------------------------------------------------------------

On TIKA-4280's regression tests 
(https://corpora.tika.apache.org/base/reports/tika-3.0.0-SNAPSHOT-reports.tgz), 
we saw quite a few false positives for colon separated csvs. Two options that 
come to mind:

1) remove the colon as an option
2) allow users to configure the separators available

Other options? What's the preference?



was (Author: talli...@mitre.org):
On TIKA-4280, we saw quite a few false positives for colon separated csvs. Two 
options that come to mind:

1) remove the colon as an option
2) allow users to configure the separators available

Other options? What's the preference?


> TextAndCSVParser doesn't detect semicolon separated file
> --------------------------------------------------------
>
>                 Key: TIKA-4278
>                 URL: https://issues.apache.org/jira/browse/TIKA-4278
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 2.9.2
>            Reporter: Tilman Hausherr
>            Priority: Major
>              Labels: csv, csvparser
>             Fix For: 3.0.0, 2.9.3
>
>         Attachments: reports_csv_2.9.2_vs_2.9.3.tar.xz, 
> reports_csv_2.9.2_vs_2.9.3_3.tar.xz, reports_csv_2.9.2_vs_2.9.3_4.tar.xz
>
>
> I ran the code from the attached SO issue and yes it doesn't detect semicolon 
> separated files. The reason is this line in {{TextAndCSVParser.java}}:
> {code:java}
> private static final char[] DEFAULT_DELIMITERS = new char[]\{',', '\t'};
> {code}
> This is later used by {{CSVSniffer}}. For some reason the other delimiters 
> (pipe, colon and semicolon) aren't in that array, although they are in 
> {{CHAR_TO_STRING_DELIMITER_MAP}}. I modified {{DEFAULT_DELIMITERS}} and now 
> it works for semicolon.
> Can I change this by adding the missing delimiters or was there a reason that 
> I missed? Proposed change would change CSVSniffer so that delimiters is a set 
> and then pass {{CHAR_TO_STRING_DELIMITER_MAP.keySet()}}.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to