steven-luabase

Commenting to follow for updates, would love to see this feature work for `.yml` models too. Current workaround is a series of lengthy CTEs

> 1. First check cache for an existing result > 2. If no result is found or refreshKey is outdated, execute query against data source > 3. If data source...

Saw that this was a similar issue https://github.com/duckdb/ducklake/issues/147 The error was slightly different though, as that one was related to columns already existing and the one I ran into is...

My temporary workaround is to manually make the migration schema changes directly in the catalog (I'm using postgres) by running a slight variation of the migration sql found [here](https://github.com/duckdb/ducklake/blob/d066f91848225ed22efd1a56349038c06f04a79c/src/storage/ducklake_metadata_manager.cpp#L91-L101): ```...

Running into the same issue with [`tap-postgres`](https://github.com/MeltanoLabs/tap-postgres) Using `table-key-properties` does not seem to work ``` plugins: extractors: - name: tap-postgres variant: meltanolabs metadata: '*-events_*': table-key-properties: - _id ``` whereas using...

Also worth noting that for other taps, like [`tap-mssql`](https://github.com/wintersrd/pipelinewise-tap-mssql) `table-key-properties` does work whereas using just `key-properties` does not. Maybe because it's using a different version of the sdk?

Yep I saw that issue, I tried bumping the endpoint version to `2024-04` but ran into the same issue with media count still.

Observing the same in issue in duckdb 1.4