Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[FEA] Support nested types in JSON reader #8827

Closed
4 tasks done
Tracked by #9
vuule opened this issue Jul 22, 2021 · 5 comments
Closed
4 tasks done
Tracked by #9

[FEA] Support nested types in JSON reader #8827

vuule opened this issue Jul 22, 2021 · 5 comments
Assignees
@elstehle
Labels
cuIO cuIO issue feature request New feature or request libcudf Affects libcudf (C++/CUDA) code. Python Affects Python cuDF API.
Projects
v22.12 Release
Milestone
Nested JSON reader

Comments

@vuule
Copy link
Contributor

vuule commented Jul 22, 2021 •
edited by GregoryKimball
Loading

Support arbitrarily nested types in JSON reader.

  • JSON format
  • JSON lines format
  • schema inference
  • user-provided schema

(edited by @GregoryKimball, 2022-06-30)
@vuule vuule added feature request New feature or request libcudf Affects libcudf (C++/CUDA) code. Python Affects Python cuDF API. cuIO cuIO issue labels Jul 22, 2021
@vuule vuule added this to Issue-Needs prioritizing in v21.10 Release via automation Jul 22, 2021
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v21.10 Release Jul 22, 2021
@beckernick beckernick added this to the IO Data Type Expansion milestone Jul 27, 2021
@vuule vuule removed this from Issue-P0 in v21.10 Release Sep 20, 2021
@vuule vuule added this to Issue-Needs prioritizing in v21.12 Release via automation Sep 20, 2021
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v21.12 Release Sep 20, 2021
@vuule vuule mentioned this issue Oct 8, 2021
Closed
@revans2
Copy link
Contributor

revans2 commented Nov 2, 2021

Just a little curious. In the check list here it says that reading list types is done. But #8335 is closed pointing at this as a duplicate. So can I assume that it is not done yet?

@vuule
Copy link
Contributor Author

vuule commented Nov 2, 2021

I think that maybe the item was automatically marked as done when #8335 was closed. Unchecked it now.

@revans2 revans2 mentioned this issue Nov 3, 2021
Open
58 tasks
@vuule vuule removed this from Issue-P0 in v21.12 Release Nov 4, 2021
@vuule vuule added this to Issue-Needs prioritizing in v22.02 Release via automation Nov 4, 2021
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.02 Release Nov 4, 2021
@GaryShen2008 GaryShen2008 mentioned this issue Jan 24, 2022
Open
@vuule vuule removed this from Issue-P0 in v22.02 Release Jan 26, 2022
@vuule vuule added this to Issue-Needs prioritizing in v22.04 Release via automation Jan 26, 2022
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.04 Release Jan 26, 2022
@github-actions
Copy link

This issue has been labeled inactive-90d due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.

@revans2
Copy link
Contributor

revans2 commented Feb 2, 2022

This is still wanted

@GregoryKimball GregoryKimball mentioned this issue Mar 26, 2022
Closed
@vuule vuule removed this from Issue-P0 in v22.04 Release Mar 28, 2022
@vuule vuule added this to Issue-Needs prioritizing in v22.06 Release via automation Mar 28, 2022
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.06 Release Mar 28, 2022
@bdice bdice mentioned this issue May 19, 2022
Closed
@vuule vuule removed this from Issue-P0 in v22.06 Release May 20, 2022
@vuule vuule added this to Issue-Needs prioritizing in v22.08 Release via automation May 20, 2022
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.08 Release May 20, 2022
This was referenced Jul 1, 2022
Closed
Closed
@GregoryKimball GregoryKimball mentioned this issue Jul 1, 2022
Closed
@vuule vuule removed this from Issue-P0 in v22.08 Release Aug 2, 2022
@vuule vuule added this to Issue-Needs prioritizing in v22.10 Release via automation Aug 2, 2022
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.10 Release Aug 2, 2022
@vuule vuule mentioned this issue Aug 2, 2022
Merged
3 tasks
rapids-bot bot pushed a commit that referenced this issue Aug 3, 2022
@vuule
Python API for the future experimental JSON reader (#11426)
b281fdf 
Add Python API to expose the future experimental JSON reader implementation.
Add tests for C++ and Python experimental APIs.

Issue #8827

Authors:
  - Vukasin Milovanovic (https://github.com/vuule)

Approvers:
  - Nghia Truong (https://github.com/ttnghia)
  - Karthikeyan (https://github.com/karthikeyann)
  - GALI PREM SAGAR (https://github.com/galipremsagar)

URL: #11426
@vuule vuule removed this from Issue-P0 in v22.10 Release Sep 23, 2022
@vuule vuule added this to Issue-Needs prioritizing in v22.12 Release via automation Sep 23, 2022
@vuule vuule moved this from Issue-Needs prioritizing to Issue-P0 in v22.12 Release Sep 23, 2022
@GregoryKimball
Copy link
Contributor

The core feature was released in 22.10, please consult the milestone for follow-up items!

v22.12 Release automation moved this from Issue-P0 to Done Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elstehle elstehle

Labels
cuIO cuIO issue feature request New feature or request libcudf Affects libcudf (C++/CUDA) code. Python Affects Python cuDF API.
Projects
cuDF/Dask/Numba/UCX
Archived in project
v22.12 Release
  
Done
Milestone
Nested JSON reader
Development

No branches or pull requests
5 participants
@revans2 @elstehle @beckernick @GregoryKimball @vuule