Hi Szehon,
Yes, you are reading the PR correctly, and interpreting the meaning of
properties correctly. I think the reply you pasted from Ryan refers to the
same concept as well.
For the initial Google doc and the issue (by the way it is an issue, not a
PR), yes both are proposing new metadata fi
Hi Walaa
As there may be confusion in the word 'properties', I want to double check
if we are talking about the same thing here.
I am reading your PR as adding lineage metadata as new key/value pair under
the storage Table's 'properties' field:
https://github.com/apache/iceberg/blob/main/format/s
Hi Szehon,
I think choosing separate view + table objects precludes us from adding new
metadata to table and view metadata. Here is one relevant comment [1] from
Ryan on the modeling doc, where his point is that we want to avoid
introducing new APIs since it requires updating every catalog, and
(q
Hi Walaa,
I agree, I definitely do not want yet another pr/doc where discussion
happens. as its already quite spread out :) But did not want to clarify
some points before we get started on the discussion on your PR.
With reusing the table and view objects, we are not changing the existing
> meta
Thanks Szehon.
The reason for the difference is that the proposal in the Google doc is
based on a new MV model, hence, new metadata fields and a new metadata
model were being introduced (with types, optionality, etc). With reusing
the table and view objects, we are not changing the existing metada
Thanks Walaa for driving it forward, looking forward to thinking about
implementation of Materialized Views.
I see Jan's point, the PR spec change is similar but does not seem to be
completely aligned with the Draft Spec in the design doc:
https://docs.google.com/document/d/1UnhldHhe3Grz8JBngwXPA6
Hi everyone,
I'm pleased to announce the release of Apache Iceberg 1.5.2!
Apache Iceberg is an open table format for huge analytic datasets. Iceberg
delivers high query performance for tables with tens of petabytes of data,
along with atomic commits, concurrent writes, and SQL-compatible table
ev
