-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to parse really long CSV cell (breaks Parsers.jl) #935
Comments
Just a clarification that the ~100K characters is per cell, not per row. I think we can support double the current length without too much trouble; we just need to add the bigger definition in Parsers.jl, then need to provide a way in CSV.jl, probably just via a keyword arg, to specify that you need/want the larger PosLen. |
Sorry yes, per Cell is correct, a limitation of the current PosLen primitive used for strings. In the data It's just the one column Double the length would be amazing, i think the 150k is the largest cell we have right now. I'm also looking at compressing/truncating the data from my end to solve my immediate problem, but if this could be a future feature it would help a lot! |
Some thoughts/initial work at increasing capacity in Parsers.jl: JuliaData/Parsers.jl#98 |
Bumping this issue, since I'm running into a similar problem, and it appears there's no alternative parsing option in this case. |
Hi Team,
Have an unusual situation where i'm trying to read in CSV files with really long (Geospatial data), about ~150k characters per row (Sample attached).
Using the default
CSV.File
method with quote chars (see my sample file attached) - i get this error. Following the stacktrace it seems the problem is with how Parsers.jl implements reading long strings from a file using their custom byte index, which only supports a maximum length of ~100k charssegment_mini.csv
Error stacktrace:
Wondering what's the stance on supporting this type of use case by CSV.jl? Will there ever be support for super long lines or should I raise with over at the Parsers.jl github instead?
The text was updated successfully, but these errors were encountered: