UI errors when filtering workflows with MariaDB

[matpen]

Pre-requisites

• I have double-checked my configuration
• I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
• I have searched existing issues and could not find a match for this bug
• I'd like to contribute the fix myself (see contributing guide)

What happened? What did you expect to happen?

I have just upgraded to v3.7.8 (from v3.6.4) and immediately started experiencing the following error in the UI:

Things I noticed, and could help pinpoint the problem:

1. As you can see in the screenshot, the UI code seems to crash and workflows are not loaded.
2. This seems to happen when a filter is applied in the left sidebar: right now I have entered a namespace and selected Phases as Error (it happens with other combinations, too). When the filter is cleared, and the page reloaded, everything works again.
3. The error message in the screenshot shows a MariaDB error, seemingly complaining about the --> operator in combination with a JSON query on labels and annotations.
4. This does not seem to affect running workflows, nor queries made via CLI: only UI.

Given the above, I would guess that this is a regression of #13202. However, I have no experience with the Argo codebase to trace the problem, so I might be wrong.

Version(s)

v3.7.8 (Helm chart 0.47.1)

Paste a minimal workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

n/a

Logs from the workflow controller

n/a

Logs from in your workflow's wait container

n/a

[MasonM]

Hi @matpen! Thanks for the report. It seems this is happening because MariaDB doesn't support the JSON path operator (column->>path). Here's a relevant ticket I found: https://jira.mariadb.org/browse/MDEV-13594

We don't support MariaDB, so this is more of a feature request than a bug. We could restore compatibility with MariaDB, but it's likely going to regress again, since we don't have any automated tests to verify compatibility.

[matpen]

It seems this is happening because MariaDB doesn't support the JSON path operator (column->>path). Here's a relevant ticket I found: https://jira.mariadb.org/browse/MDEV-13594

Indeed. This seems to be a discrepancy between MySQL and MariaDB, as confirmed by the reasoning outlined in #13202.

We don't support MariaDB, so this is more of a feature request than a bug. We could restore compatibility with MariaDB, but it's likely going to regress again, since we don't have any automated tests to verify compatibility.

I fully understand, and I just opened this ticket because in #13202 the team decided to go ahead with what they considered to be a "quick fix", which could help some users. In my case, I could rather painlessly switch to PostgreSQL, which I confirm working flawlessly so far.

Feel free to close if you deem it out of scope!