Add Pandas profile.py
analyzer for JSON, CSV/TSV, and Parquet
#157
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JSON, CSV, TSV, and Parquet files now have a Pandas data profile analyzer for local filesystems, remote object stores (S3), and remote HTTP(S) locations. The profiler also runs against all SQLAlchemy compatible URLs, so
TablePath
andViewPath
locations are also analyzed with Pandas.I also took the opportunity to fix a bug in the Frictionless, GenSON, and DuckDB columns.py analyzers, which were using forward reference types for their
create_analyzer
methods. Since these analyzers both had the same class name, the bug caused the plugins to all resolve to the first analyzer class that it saw. Thus, DuckDB's analyzer was returned for the Frictionless and GenSON analyzers as well.Future work:
DataFrame.hist()
data to the profile.