Charlie Briggs

Results 40 comments of Charlie Briggs

This only seems to occur when using a custom label, e.g `_` rather than the default `@`. We've now switched to the default so are less interested in the resolution...

https://github.com/metabase/metabase/issues/21600 is similar - I need the "all" option, but I'd like the `all` option to be the default, so if a linked filter is updated, the filter shrinks/grows its...

I'd be satisified with the performance penalty weighed against useability of the dashboard. If there was over some hardcoded threshold of options - I assume one exists where it goes...

It'd be great to see this in merged if possible - this is holding us up on upgrading airflow (we could point to this PR but would prefer not to)

I just tested this with dbt 1.2.1RC1 and I'm seeing the same error: ``` [2022-08-11, 15:35:24 BST] {{subprocess.py:92}} INFO - 14:35:24 Running with dbt=1.2.1-rc1 ... ... ... [2022-08-11, 15:46:01 BST]...

Yep, there are 4 models like this within the project: - `int_organisations_content_licenses_with_time_ranges` - `int_organisations_content_set_access_with_time_ranges` - `int_organisations_content_set_access_with_time_ranges_api` - `int_organisations_content_licenses_with_time_ranges_api`

We haven't seen any errors since deploying rc2 the day it was released

This now seems to have turned into errors when running Deltastreamer: ``` 22/08/11 10:16:25 INFO HoodieTableMetaClient: Loading HoodieTableMetaClient from s3://prod-signal-articles-store/articles_hudi_copy_on_write/.hoodie/metadata 22/08/11 10:16:25 INFO HoodieTableConfig: Loading table properties from s3://prod-signal-articles-store/articles_hudi_copy_on_write/.hoodie/metadata/.hoodie/hoodie.properties 22/08/11...

I tried to delete the Hoodie `metadata` folder (`.hoodie/metadata`) and allow the next run to recreate it, however Deltastreamer failed with this error: ``` java.lang.IllegalStateException: Metadata table is not fully...

> Can you disable metadata explicitly in your write configs (hoodie.metadata.enable=false), and try restarting your pipeline This already worked for us, I haven't tried re-enabling metadata yet. Erasing the table...