You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tests were updated to reflect the change in that PR, but I am unsure that this is intended behavior as no other file read functions (e.g. read_csv) were updated.
Steps/Code to reproduce bug
The code below shows how the behavior of read_json differs from that of read_csv.
Thank you for opening the issue.
This is intended behavior, see #6411.
The plan is to stop using column_names in tests and Cython bindings, and to remove column_names from table_metadata once this is complete.
You can use the schema_info member to get column names when reading JSON files. It quickly replaced column_names because it supports nested columns (like the experimental JSON parser does).
Keeping the issue open in case there are follow-up questions we can help with :)
Describe the bug
With the release of libcudf 22.10.00,
read_json
no longer sets thecolumn_names
field of it's return value. Instead, it sets the names in theschema_info
field. This seems to have been introduced in #11364: https://github.com/rapidsai/cudf/pull/11364/files?diff=unified&w=0#diff-6e1002a16556df11f73b654cffbe18812bed655f377f52a6888c53ba6e1f04a6L566-R566.Tests were updated to reflect the change in that PR, but I am unsure that this is intended behavior as no other file read functions (e.g.
read_csv
) were updated.Steps/Code to reproduce bug
The code below shows how the behavior of
read_json
differs from that ofread_csv
.Output:
Environment overview (please complete the following information)
The text was updated successfully, but these errors were encountered: