When you deleted the data from row 21 onwards did you just highlight the cells/data and press delete, or select all the row numbers from 21 to the end, right click and select delete? There is a difference, the former just clears the data from the cells but otherwise Excel considers the cells to have content (retains styles etc). If you do the latter it actually deletes the rows entirely from its internal representation.
Have you opened up the xlsx file as a zip and had a look at the XML file for the sheet? Since you're still seeing SAX processing those rows it's my guess that when you saved the file Excel thought they were still valid content cells and wrote out empty cells for all of them. Try deleting the rows using the method I described, and then seeing if SAX still processes them. >________________________________ > From: Enrique <[email protected]> >To: [email protected] >Sent: Monday, March 10, 2014 10:48 AM >Subject: XSSF - detecting end of file when reading XLSX files > > >Hello, > >I'm working on making extraction of some excel files (very large files), >using XSSF + SAX. > >I've used some tests files, specifically one that contained thousands of rows >of data. I only wanted to keep few of them, so I deleted all the content from >the 20th row. When I process this excel file, I see that since the 21th row, >every row I processed, with empty results obviously. > >I would rather expect to have this process finished. Is there anyway to say >to the XSSF processor not to enter this empty rows? > >I suppose there is a relation with the fact that the file contained more data >in this rows before, but this is a real case that our end users could do. > >Thanks for your help. > >Kind regards, >Enrique > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [email protected] >For additional commands, e-mail: [email protected] > > > >
