Correct fastparquet call
See original GitHub issuePlease, could you remove the setting of sep
parameter when calling ParquetFile.__init__()
from fastparquet lib?
This parameter is not used any longer.
def __init__(self, fn, verify=False, open_with=default_open,
root=False, sep=None, fs=None, pandas_nulls=True):
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Usage Notes — fastparquet 0.7.1 documentation
Fastparquet will automatically use metadata information to load such columns as categorical if the data was written by fastparquet/pyarrow. To efficiently load ...
Read more >dask/fastparquet: python implementation of the ... - GitHub
fastparquet is a python implementation of the parquet format, aiming integrate into python-based big data work-flows. It is used implicitly by the projects...
Read more >fastparquet Documentation - Read the Docs
1. fix critical buffer overflow crash for large number of columns and long ... Dask and Pandas fully support calling fastparquet directly, ...
Read more >How to use the fastparquet.write function in fastparquet - Snyk
Secure your code as it's written. Use Snyk Code to scan source code in minutes - no build needed - and fix issues...
Read more >Problem with opening parquet files with fastparquet after ...
before updating to dask 2.2.0 and latest fastparquet it worked correctly. Now I get this messages. On executing read command:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for opening this issue. I will open a PR to try removing
sep
.Thanks a lot for your reactivity! Much appreciated!