Bug 61928 - Incorrext XLSB extraction
Summary: Incorrext XLSB extraction
Status: RESOLVED LATER
Alias: None
Product: POI
Classification: Unclassified
Component: XSSF (show other bugs)
Version: 3.17-FINAL
Hardware: PC Linux
: P2 enhancement (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-26 04:29 UTC by grimmreaperph
Modified: 2018-04-05 19:38 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description grimmreaperph 2017-12-26 04:29:25 UTC 
Supposed I have a Sample.xlsb file that contains the ff data:

--
         colA    colB    colC    colD
row1     value0  value1          value3
--

When extracted using XSSFBEventBasedExcelExtractor via getText(), output is:

--
         colA    colB    colC    colD
row1     value0  value1  value3
--
Comment 1 grimmreaperph 2017-12-26 04:33:46 UTC 
Now the colD data is missing because the XSSFBEventBasedExcelExtractor -> getText() didn't leave the colC empty.
Comment 2 Dominik Stadler 2018-02-08 19:54:28 UTC 
Can you provide sample files and code that shows the problem to make it possible for others to reproduce the described behavior?
Comment 3 Tim Allison 2018-02-08 21:19:17 UTC 
Does this behavior differ from XSSFEventBasedExcelExtractor?
Comment 4 Dominik Stadler 2018-04-05 19:38:08 UTC 
We cannot analyze or reproduce this without more information, please reopen this bug if it is still a problem for you and you can provide some sample files and sample-code/unit-tests which reproduce this problem.