Honah (Jonas) J.

@geruh, thanks for highlighting this issue. The confusion largely stems from the naming convention used when the `profile_name`, `region_name`, `aws_access_key_id`, etc., were introduced in [#7781](https://github.com/apache/iceberg/pull/7781). Initially, these configurations were intended...

Thanks for raising the PR! I am also +1 on removing this. This seems unnecessary and will inevitably lead to the issue as @sungwy mentioned in the third point: >...

Hmm, it's my first time to see this error. I've merged a PR that bumps `duckdb` to 1.0.0: #793. Hope that can fix the issue here. BTW, thanks for working...

> Is this a duck db problem? Or do I need to open a new PR (from main branch + my changes) to resolve it? I tried this PR locally...

Hi @MehulBatra. Thanks for taking this! It looks like a great start. > I believe we need to make a change in this write_file method to support ORC writes, as...

I am interested in digging more into this feature and working on it if no one has started.

@kevinjqliu Thanks for doing the experiments! > But I think there's still a lot to gain by separating out the package namespace of an intentional publication (release candidates, and successful...

> TableMetadata is initialized with the default Pydantic object for schema, partition_spec, and sort_order, which does not play well with table updates. Hi @kevinjqliu. Could you please elaborate more on...

I think this is related to the `CreateTableTransaction` use-case and the current limitation of `update_table_metadata`, which is used in all non-rest catalog's `_commit_table`. As @kevinjqliu mentioned in the issue description...

Hi @kevinjqliu I ran a few experiments and found that removing `initial_change `would be challenging unless we can temporarily disable Pydantic’s validators during `update_table_metadata`. Fortunately, I found that Pydantic’s `model_construct`...