badalprasadsingh opened a new issue, #1188:
URL: https://github.com/apache/iceberg-go/issues/1188
### Apache Iceberg version
None
### Please describe the bug š
#### Description
Iceberg-Go's SQL catalog assumes that iceberg table always has the `V1`
schema column `iceberg_type` (cf. `JdbcUtil.RECORD_TYPE`).
When the same postgres database has already been initialised by jdbc catalog
at its default schema-version (V0), the `iceberg_type` column does not exist.
Every read query bun emits via the `sqlIcebergTable` model fails immediately.
**Proposed Solution**
On catalog init, run `ALTER TABLE iceberg_tables ADD COLUMN iceberg_type
VARCHAR(5)` if the column is missing, and change every iceberg-go SQL query
that filters on iceberg_type to accept the legacy NULL form.
**Contribution**
Iād be happy to work on this issue. Please feel free to assign this issue to
me and I can prepare a PR implementing it.
--
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]
