You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tika.apache.org by "Hudson (Jira)" <ji...@apache.org> on 2023/05/10 15:49:00 UTC

[jira] [Commented] (TIKA-4029) commons-csv 1.10 changed IllegalStateException to IOException

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

Hudson commented on TIKA-4029:
------------------------------

FAILURE: Integrated in Jenkins build Tika » tika-main-jdk8 #1079 (See [https://ci-builds.apache.org/job/Tika/job/tika-main-jdk8/1079/])
TIKA-4029 -- change catch logic based on change in commons-csv 1.10.0 (tallison: [https://github.com/apache/tika/commit/de89f69c7fc4e8390ba9a9bea3af1ba608002177])
* (edit) tika-parsers/tika-parsers-standard/tika-parsers-standard-modules/tika-parser-text-module/src/main/java/org/apache/tika/parser/csv/TextAndCSVParser.java


> commons-csv 1.10 changed IllegalStateException to IOException
> -------------------------------------------------------------
>
>                 Key: TIKA-4029
>                 URL: https://issues.apache.org/jira/browse/TIKA-4029
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Minor
>             Fix For: 2.8.0
>
>
> In the CSVParser, we had a catch statement in case the csv file was malformed.  In the catch statement we read the rest of the stream and wrote it as one big paragraph.  We then threw the exception.
>  
> In commons-csv 1.10.0, it looks like they changed the IllegalStateException to an UncheckedIOException.  So, we're now missing a bunch of text that we used to extract from csv files.
>  
> This issue was discovered during our regression tests in preparation for the release of 2.8.0-rc1
>  



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