igorbelianski-cyber commented on PR #11041:
URL: https://github.com/apache/iceberg/pull/11041#issuecomment-3658242606
Benny,
Are you proposing to simplify states from
tri-state (fresh, stale ,invalid ). down to 2 states (fresh, stale) ?
with various suggested above flavors implementing freshness
determination ?
Personally I would prefer the simplification (I am not certain i
interpreted your comment correctly)
PS
If we were to pursue this option we would need to make some definitive
statements about not initialized MVs.
On Fri, Dec 12, 2025 at 8:46 PM Benny Chow ***@***.***> wrote:
> ***@***.**** commented on this pull request.
> ------------------------------
>
> In format/view-spec.md
> <https://github.com/apache/iceberg/pull/11041#discussion_r2616065681>:
>
> > +When `ref` is `null` or not set, it defaults to "main".
> +
> +#### Source view
> +
> +A source view record captures the state of a source view at the time of
the last refresh operation.
> +
> +| Requirement | Field name | Description |
> +|-------------|----------------|-------------|
> +| _required_ | `uuid` | The uuid of the source view |
> +| _required_ | `version-id` | Version-id of when the last refresh
operation was performed |
> +
> +#### Status Interpretation
> +
> +During read time, a materialized view (storage table) can be interpreted
as "fresh", "stale" or "invalid", depending on the following situations:
> +
> +* **invalid** -- The current `version_id` of the materialized view does
not match the `view-version-id` recorded in its refresh state. A read operation
cannot proceed using the materialized view's data.
>
> I personally find trying to use invalid, fresh and stale statuses as too
> generic. We could instead describe the 3 high level ways a consumer would
> validate the freshness:
>
> 1. Use refresh-start-timestamp-ms
> 2. Use source-table-states and source source-view-states. Optionally
> validating nested MV refresh-state..
> 3. Advanced validation through view SQL expansion and refresh-state
> comparison.
>
> For 3, the consumer may determine that affected partitions in the table
> are still up to date after pushing down filters.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/apache/iceberg/pull/11041#discussion_r2616065681>, or
> unsubscribe
>
<https://github.com/notifications/unsubscribe-auth/B3NEUQTQP2XE7PBFVSAGYE34BOKY7AVCNFSM6AAAAABNKKAL3KVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZTKNZUGE3TOMBQGA>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
--
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]
