github-actions[bot] closed issue #9737: branch schema affected by main table
schema
URL: https://github.com/apache/iceberg/issues/9737
--
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 co
github-actions[bot] commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2455962528
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apache Gi
github-actions[bot] commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2425313868
This issue has been automatically marked as stale because it has been open
for 180 days with no activity. It will be closed in next 14 days if no further
activity occurs.
nastra commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2027964878
> Looks like we are disabling the workaround from #10059.
The reason for #10059 is because we don't support time travel on branches
themselves, because there's no history track
namrathamyske commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2026055049
Looks like we are disabling the workaround from
https://github.com/apache/iceberg/pull/10059.
More future fix is where we track `schemaId` from snapshot in `SnapshotRef`
ob
danielcweeks commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2026009473
@namrathamyske it was pointed out to me that workaround may not be working
correctly for branches, which is something we might need to address.
--
This is an automated message
namrathamyske commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2026003001
Thanks @danielcweeks @nastra !
--
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
nastra commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2025665097
> @namrathamyske you can force reading with the snapshot id on a branch by
using the time travel statement.
>
> ```
> select * from default.t.branch_b1 for timestamp as of no
danielcweeks commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2025526690
@namrathamyske you can force reading with the snapshot id on a branch by
using the time travel statement.
```
select * from default.t.branch_b1 for timestamp as of now(
nastra commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-2024853497
@namrathamyske I've opened https://github.com/apache/iceberg/pull/10055 to
clarify which schema is being used when.
--
This is an automated message from the Apache Git Service.
To r
namrathamyske commented on issue #9737:
URL: https://github.com/apache/iceberg/issues/9737#issuecomment-1953177938
When fetching data the schema which was associated with branch should be
issued not table. But for operations like cherry pick from branch to main, it
should resolve conflicts
namrathamyske opened a new issue, #9737:
URL: https://github.com/apache/iceberg/issues/9737
### Apache Iceberg version
main (development)
### Query engine
None
### Please describe the bug 🐞
regarding this PR: https://github.com/apache/iceberg/pull/9131 - th
12 matches
Mail list logo
