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

Jukka Zitting commented on TIKA-833:
------------------------------------

It's good that we monitor changes in POI and make sure that Tika works properly 
with the latest versions, but until the changes in POI have been released and 
relevant dependency in Tika trunk updated, this is not an bug in Tika and IMHO 
shouldn't be tracked as one.

The POI bug #52389 is more appropriate, and rather than resolving this issue as 
fixed for Tika 1.1 I think we should resolve this as Invalid or Duplicate (of 
POI bug #52389) to keep the 1.1 release notes clean.
                
> POI Daily beta6 as of 12/27 breaks ExcelParserTest.testExcelParserFormatting()
> ------------------------------------------------------------------------------
>
>                 Key: TIKA-833
>                 URL: https://issues.apache.org/jira/browse/TIKA-833
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.1
>            Reporter: Jeremy Anderson
>              Labels: excel, poi, test
>             Fix For: 1.1
>
>
> Attn Nick:
> Changes made to POI(v1221126) for POI-52349 causes the 
> ExcelParserTest.testExcelParserFormatting() junit test case to go out to 
> lunch within POI's DataFormatter.FractionFormat().  Specifically within the 
> nested for loops at line 1000.  These nested loops both have extremely high 
> values that cause the test case to hang for an extremely long duration during 
> the new OfficeParser().parse(input, handler, metadata, context); call at line 
> 73.  This appears to happen due to the Custom Date value in the test file not 
> being identified as a date.
> I'm not sure if the proper resolution lies in modifying TIKA's test case or 
> if a new bug needs to be opened on POI's side, but I wanted to bring this 
> issue to light.
> Regards,
> Jeremy  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to