Description: Loading large .csv file at the end of loading displays message "The data could not be loaded completely because the maximum number of rows per sheet was exceeded." Is it possible to have interface like Excel does in this situation, to give user ability to filter this large .csv and to load filtered version? Actual Results: Summary: "The data could not be loaded completely because the maximum number of rows per sheet was exceeded." - message dialog in Calc. Expected Results: New UI that would allow loading filtered version. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
MAX row count is 1,048,576, or 2^20 rows Do you really have a CSV that large? Otherwise the CSV is misformatted. =-ref-= https://wiki.documentfoundation.org/Faq/Calc/022
250M just trying to load utility that logged for week traffic on server with single client connected.
Sure, some LO testing prior to import filter parsing (e.g. test with wc -l) might be feasible. But that really is rather an abusive data set to be pushing into a spread sheet. I would not want to try to work with a sheet that large ;-) Would think loading to Base on detection would be a smarter route. Filtering records would be trivial at that point. @Eike, Kohei?
I've seen this suggestion on different forums. But using Cals seems more intuitive for end users.
Filter how? What does Excel do there?
Created attachment 137534 [details] Excel Query Editor #1
Created attachment 137535 [details] Excel Query Editor #2
Excel uses Query Editor.
I would say, rather than a filter, the maximum number of row restriction should be dropped. I just tried to open a file, that wasn't even 70 MB and couldn't open it. We are in 2019. My computer has 20GB of ram. And I cannot open a 70 MB file because of some arbitrary row restriction?! Really!? (I have read the bug on the maximum column number restriction and understand that there might be some underlying technical debt issues that make this difficult to fix, but from a user perspective this really is ridiculous behaviour. I hope it will get fixed.)