I’ve been using Redash for a little while and have never had a problem with the search functionality for queries. Having upgrade to v5 it’s absolutely and totally useless.
Previously it seems there was a simple implementation so that searches just used a “LIKE” on the name & description fields of the ‘queries’ table. Great.
Now it seems things have migrated to PostgreSQL full text search - which is being populated with the name, the id, the description and the query body. This makes search worse then useless for me; and I can’t believe I’m the only one in this situation; I have a whole load of queries that are named and titled based upon what they’re for which usually means listing what information they take as parameters to perform analysis - however these are fields in plenty of other queries, often multiple times.
Worse still, I have a bunch of queries that are used for populating query-based drop-down boxes - since they’re for selecting a constant they’re called:
Select: A Country
Select: A Product
Select: A Supplier
In older redash versions I’d have chosen a parameter to be a “Query Based Dropdown List” typed “Select” into the query name box and be given a list of the above queries… however in Redash v5 I type “Select” and can choose between ~25 recent unpublished queries none of which are what I’m looking for. Even if I type in the full name of the query I want “Select: A supplier” I get 25 unrelated queries and no way to pick what I want.
Has something gone wrong with my upgrade or is this now the intended behaviour?
At this rate I’m going to locally alter the schema of the redash Postgres DB so that the query body isn’t included in the full-text index.