Closed malhotrashivam closed 3 weeks ago
One more thing, the nesting of IcebergReadInstructions
inside IcebergReadTable
makes me wonder if we really need two levels at all? Can we specialize IcebergReadInstructions
to include schema, snapshot, etc. and only have one builder? Not sure that makes sense in writing though
The Python changes LGTM. Do we need to tag it as 'breaking' even if it is experimental? Just for release notes purpose?
I tagged it breaking also from Java point of view because we are changing all the iceberg read APIs.
Labels indicate documentation is required. Issues for documentation have been opened:
Community: https://github.com/deephaven/deephaven-docs-community/issues/335
BREAKING CHANGES / Documentation Update:
As a follow up to #5707, following are the main changes:
IcebergTableAdaper::definition
,IcebergTableAdaper::definitionTable
, andIcebergTableAdaper::table
to inside IcebergReadInstructions to reduce the overloads.For example,
Before
After