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.

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

[Java API] Break up Table API #706

Closed
nbauernfeind opened this issue Jun 3, 2021 · 2 comments
Closed

[Java API] Break up Table API #706

nbauernfeind opened this issue Jun 3, 2021 · 2 comments
Assignees
Labels
Milestone

Comments

@nbauernfeind
Copy link
Member

nbauernfeind commented Jun 3, 2021

The Table.java API needs to split into two, TableData and TableOperations (to be named?). The TableOperations will drive things that can be done without having a table on-hand (aka QST), while TableData drives data that exists client-side.

EPIC: Java API #257

@nbauernfeind nbauernfeind added the core Core development tasks label Jun 3, 2021
@nbauernfeind nbauernfeind added this to the June 2021 milestone Jun 3, 2021
@nbauernfeind nbauernfeind self-assigned this Jun 4, 2021
@nbauernfeind nbauernfeind changed the title Break up table API Java API: Break up Table API Jun 4, 2021
@nbauernfeind nbauernfeind changed the title Java API: Break up Table API [Java API] Break up Table API Jun 4, 2021
@nbauernfeind
Copy link
Member Author

TableOperations is take care of via #762.

The TableData API remains.

@nbauernfeind nbauernfeind modified the milestones: June 2021, Aug 2021 Jul 26, 2021
@rcaudy rcaudy assigned devinrsmith and unassigned nbauernfeind Aug 29, 2021
@rcaudy
Copy link
Member

rcaudy commented Aug 29, 2021

Devin delivered on TableOperations. As of now, I don't think we need a separate TableData.

@rcaudy rcaudy closed this as completed Aug 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants