ENH: Support pd.json_normalize for normalizing only meta fields #60460
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.
doc/source/whatsnew/vX.X.X.rst
file if fixing a bug or adding a new feature.Currently,
meta
is used with whenrecord_path
is not None. The logic is to extract both therecord_path
and ethemeta
. For example:In the above example,
pd.json_normalize
not only retrievescounties
, but also retrievesstate
,shortname
andinfo.governor
.When
record_path
is not given,meta
is ignored, for example:This PR adds a feature when
record_path
is None or an empty list, only extracts themeta
.The behavior can be summarized as:
record_path
is None,meta
is None: normalize all records.record_path
is not None,meta
is None: normalize onlyrecord_path
.record_path
is not None,meta
is not None: normalizerecord_path
andmeta
.record_path
is None,meta
is not None: normalize onlymeta
. [This PR]