Jayce Slesar
Jayce Slesar
I think there is a better way to figure this out....ideally would like to stratify by channel as well as not all channels in a test finish at the same...
So I have found 0 reliable ways to determine if a channel within test has completed....still looking but if you have any ideas shoot
I think the best strategy so far is to probe your database every hour or so, if the latest data in a channel is greater or equal than 3 days...
see https://github.com/duckdb/duckdb-iceberg/issues/2 -- looks like this is a super fresh implantation of reading from iceberg
would be awesome to get some momentum here, I took a look at the java impl of this (I am not fluent in java) and have a very rough idea...
I did a little digging and just to be safe also tested `table.scan(row_filter=In("x", [0.0, 1.0, 2.0]))` which results in the same issue. I do however believe that this is happening...
We could also cover testing against all catalogs via the `test_catalog.py` in the integration tests!
Im certainly in no rush so happy to let you see this through! Would be epic to have this in the next minor release (0.11.0) !
EmrServerlessStartJobOperator does not cancel EMR Serverless job when waiter_max_attempts is reached
Do you ever see https://github.com/apache/airflow/blob/main/airflow/providers/amazon/aws/operators/emr.py#L1272 ("Unable to request query cancel on EMR Serverless. Exiting") in the logs?
Any update on this?