[MXS-3365] Missing match setting in filter(s) results in no match at all Created: 2021-01-05  Updated: 2021-01-18  Resolved: 2021-01-08

Status: Closed
Project: MariaDB MaxScale
Component/s: Filter
Affects Version/s: 2.5.6
Fix Version/s: 2.5.7

Type: Bug Priority: Major
Reporter: Assen Totin (Inactive) Assignee: Esa Korhonen
Resolution: Fixed Votes: 0
Labels: None

Sprint: MXS-SPRINT-122

 Description   

Documentation at the below link clearly says that "If match is not defined, all queries are considered to match.". All filter modules link to this place from their own pages.

https://mariadb.com/kb/en/mariadb-maxscale-25-mariadb-maxscale-configuration-guide/#standard-regular-expression-settings-for-filters

This is completely wrong, at least for Tee and QLA filters, likely for many (all?) others too. If no match clause is given in the filter's config section, the filter will NEVER match. It order to match all queries, one must specify:

match=/.*/

Unsure if this is a regression or not and if the MaxScale or the docs have to be fixed, but they MUST be aligned. Otherwise we just seem lame and cause confusion and frustration with customers.



 Comments   
Comment by Esa Korhonen [ 2021-01-08 ]

Applies to Tee-filter, but did not see the reported behavior in QLA.

Generated at Thu Feb 08 04:20:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.