Hello here
We updated our Metabase instance to the last version to get the log4j patch.
However, this new version comes with a new way to autocomplete in the search in filter. The search is now infix, where it use to be prefix.
Source for this evolution
PR https://github.com/metabase/metabase/pull/15032
issue https://github.com/metabase/metabase/issues/8219
We had the proper index (postgresql, covering B-tree on (lower(column), column)) to autocomplete instantly on a 20 millions lines table.
With the new mecanism, we cannot find an index efficient enough. Hence our website is completely broken.
Do someone have ideas on what we should do ?
Maybe Metabase will give the option to choose how to autocomplete in the future ?
Or would it be easy to fork a version without this evolution (but with log4j patch) ?
To give some context, we are an NGO working on transparency in health.
Our websites eurosfordocs.fr (the broken one) and eurosfordocs.eu.
Our gitlab account : https://gitlab.com/eurosfordocs/
Any help welcome ! 