feat!(excelreader): only load dtypes for columns specified via use_columns
#329
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.
This changes our logic regarding the information we extract on sheet load. Rather than loading dtype information for all available columns, we only load it for selected columns. This introduces two breaking changes:
ExcelTable
andExcelSheet
,available_columns
is no longer a property. It is now a method, and information regarding available columns is computed on-demand (the information is cached after having been computed once).use_columns
is a callable, it no longer receives aColumnInfo
object, but aColumnInfoBuilder
instead (no dtype information).ColumnInfoBuilder
is now part of the Python API.@PrettyWood If you have a better naming suggestion for
ColumnInfoBuilder
, I'd love to hear it. MaybeColumnNameInfo
orColumnInfoNoDtype
?closes #327