javrasya commented on issue #10274:
URL: https://github.com/apache/iceberg/issues/10274#issuecomment-2095823012
An interesting finding, once there is any update on the main branch after
the schema is evolved, this no longer becomes a problem.
I ran the following to trigger a dummy update to test it and the problem
went away;
```sql
MERGE INTO spark_catalog.spark_catalog.my_db.my_table AS target
USING (SELECT * FROM spark_catalog.my_db.my_table LIMIT 1) AS source
ON target.id = source.id
WHEN MATCHED THEN
UPDATE SET *;
ALTER TABLE spark_catalog.my_db.my_table CREATE BRANCH `my_test_branch`;
SELECT *
FROM spark_catalog.my_db.my_table.branch_my_test_branch
WHERE myStructField.newlyAddedField='123' ;
```
--
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: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
