[Bug 31114] HSSFWorkbook(POIFSFileSystem fs) - constructor throwing exception

https://bz.apache.org/bugzilla/show_bug.cgi?id=31114 --- Comment #4 from vandrouny --- Created attachment 35584 --> https://bz.apache.org/bugzilla/attachment.cgi?id=35584&action=edit Example file with exception java.lang.ArrayIndexOutOfBoundsException: 2 at org.apache.poi.hssf.record.M

[Bug 31114] HSSFWorkbook(POIFSFileSystem fs) - constructor throwing exception

https://bz.apache.org/bugzilla/show_bug.cgi?id=31114 vandrouny changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[Bug 33951] constructor call HSSFWorkbook(POIFSFileSystem) -> IndexOutOfBoundsException / InvocationTargetException

https://bz.apache.org/bugzilla/show_bug.cgi?id=33951 Bug 33951 depends on bug 31114, which changed state. Bug 31114 Summary: HSSFWorkbook(POIFSFileSystem fs) - constructor throwing exception https://bz.apache.org/bugzilla/show_bug.cgi?id=31114 What|Removed |Add

[Bug 61858] New: Getting double value from the method "cell" of interface "SheetContentsHandler" of "XSSFSheetXMLHandler" class

https://bz.apache.org/bugzilla/show_bug.cgi?id=61858 Bug ID: 61858 Summary: Getting double value from the method "cell" of interface "SheetContentsHandler" of "XSSFSheetXMLHandler" class Product: POI Version: unsp

RE: Test document Tika-792

getText(includeDeleted) is on the right track, I think. Given that a run can have ruby text and/or be a formula and/or be any one of the many things on 4139-4140, should we be more specific? getDeletedText(), getRuby(), etc... -Original Message- From: Murphy, Mark [mailto:murphym...@me

[Bug 61859] New: Limited support for array operands

https://bz.apache.org/bugzilla/show_bug.cgi?id=61859 Bug ID: 61859 Summary: Limited support for array operands Product: POI Version: 3.17-FINAL Hardware: Macintosh Status: NEW Severity: normal Priority: P2

RE: Test document Tika-792

I thought about that, but then how does the user know when deleted text or a Ruby exists. As it is, getText retrieves Ruby text. Or if we just retrieve Deleted text, how does the user know where it came from? My thought concerning getText(includeDeleted) is that all the text including deleted t

[Bug 61841] Unnecessary long computation when evaluating VLOOKUP on all column reference

https://bz.apache.org/bugzilla/show_bug.cgi?id=61841 --- Comment #4 from Greg Woolsey --- It looks to me like the sheet is available: Vlookup.evalutate() receives a ValueEval that is converted to a TwoDEval via LookupUtils.resolveTableArrayArg(). TwoDEval interface has only one base class imple

[GitHub] poi pull request #84: Simplify code for writing SXSSF chars

GitHub user pjfanning opened a pull request: https://github.com/apache/poi/pull/84 Simplify code for writing SXSSF chars Related to https://bz.apache.org/bugzilla/show_bug.cgi?id=61792 I think this code is easier to read than the existing code. The unit tests pass but I sus

[Bug 61858] Getting double value from the method "cell" of interface "SheetContentsHandler" of "XSSFSheetXMLHandler" class

https://bz.apache.org/bugzilla/show_bug.cgi?id=61858 --- Comment #1 from PJ Fanning --- Thanks Phaneeswar for the proposed patch. It does modify a public API (the cell method) and this is not something that we don't do without deprecating the existing method. The replacement method can be added a

[Bug 61841] Unnecessary long computation when evaluating VLOOKUP on all column reference

https://bz.apache.org/bugzilla/show_bug.cgi?id=61841 --- Comment #5 from Greg Woolsey --- Changes in r1817252 Interesting. In a local test with the attached sample file, I found these results: 45s (second run) with current codebase issuing FormulaEvaluator.evaluateAll() on the workbook. 19s

Build failed in Jenkins: POI-DSL-Windows-1.8 #94

See Changes: [gwoolsey] Bug #61841 - Unnecessary long computation when evaluating VLOOKUP on all column reference Found some optimizations in the general evaluation framework related to blank cells in rows be

Build failed in Jenkins: POI-DSL-OpenJDK #329

See Changes: [gwoolsey] Bug #61841 - Unnecessary long computation when evaluating VLOOKUP on all column reference Found some optimizations in the general evaluation framework related to blank cells in rows beyon

Build failed in Jenkins: POI-DSL-1.8 #317

See Changes: [gwoolsey] Bug #61841 - Unnecessary long computation when evaluating VLOOKUP on all column reference always with the missing license... [gwoolsey] Bug #61841 - Unnecessary long computation when evaluati