findinpath opened a new pull request, #18135:
URL: https://github.com/apache/iceberg/pull/18135

   ## What
   
   Minimal, self-contained port of the materialized-view "storage table" 
mechanism and its
   RefreshState/SourceTableState/SourceViewState freshness/refresh bookkeeping 
model onto the
   stable apache-iceberg-1.11.0 release tag, instead of tracking main.
   
   This branch carries just the storage-table/refresh-state-related files from 
@wmoustafa's
   materialized-views branch (which tracks main) — ViewVersion#storageTable(),
   ViewBuilder#withStorageTableIdentifier(...), the corresponding wire-format 
support in
   ViewVersionParser/RESTSessionCatalog/CatalogHandlers, and the new 
RefreshState /
   RefreshStateParser / SourceState / SourceTableState / SourceViewState 
classes — applied on top
   of apache-iceberg-1.11.0, dropping everything else that branch picked up 
incidentally from
   tracking main (unrelated API churn, test adjustments, etc.).
   
   ## Why
   
   Trino's Iceberg REST catalog materialized-view support (trinodb/trino#31027) 
needs this native
   mechanism to exist in a buildable Iceberg artifact. This branch exists so 
that PR can build and
   run its test suite against something closer to a real release than a full 
main snapshot, while
   the underlying spec/reference-implementation work is still unmerged upstream.
   
   ## Relationship to other PRs
   
   - #9830 — the original reference implementation this is ported from 
(materialized views backed
     by a native storage table, with Spark integration).
   - #11041 — the formal materialized-view spec proposal this mechanism is 
based on.
   
   This PR is not a proposal to merge materialized views into Iceberg — it's a 
downstream
   showcase/reference build for trinodb/trino#31027. Please treat #9830/#11041 
as the actual venues
   for that discussion.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to