Unable to use regexextract function to create custom columns

Get Help
21

It should be 8.0.35.

I believe it is not related to the version of MySQL, as I can still execute previously saved questions with regexextract expressions.
However, I am currently unable to modify existing questions with regexextract expressions or create new ones.

22

Would you mind sharing with me a screenshot of the GUI that you are able to execture the regex statement

23

This is the GUI for this question.

image
image1980×1500 189 KB

This is the SQL generated automatically for this question.

image
image2230×1620 275 KB

This is the execution results for this question.

image
image2148×402 44.9 KB

24

I have noticed a peculiar phenomenon. In the same Metabase, when I query from another database (Redshift database), the "regexextract" function works. Why is that?

25

Hmmm can you confirm the MYSQL version? I know you mentioned "It should be 8.0.35." but can you confirm so i can deploy a similar Version and check

26

Hey there,

I have the exact same issue, on 0.49.3 with MySQL 8.0.35 too.

I had to switch to a question written in SQL in order to be able to use REGEXP_SUBSTR (that works perfectly fine). So there's no reason we have this "Unsupported function regex-match-first" in the notebook editor when we try to use regexextract.

27

8.0.31

28

Any news ?

29

Bump...

30

I'm running into this as well.

image
image781×871 30.6 KB

image
image749×270 11.4 KB

Running 0.49.12 and mysql 8.0.36. Not sure if this matters, but the table is from an uploaded csv file.

31

not sure how but now i managed to replicate opened a bug, for reference:

32

Hello,

I have the same problem with my sql database.
image

{
  "browser-info": {
    "language": "fr-FR",
    "platform": "MacIntel",
    "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36",
    "vendor": "Google Inc."
  },
  "system-info": {
    "file.encoding": "UTF-8",
    "java.runtime.name": "OpenJDK Runtime Environment",
    "java.runtime.version": "11.0.22+7-post-Ubuntu-0ubuntu222.04.1",
    "java.vendor": "Ubuntu",
    "java.vendor.url": "https://ubuntu.com/",
    "java.version": "11.0.22",
    "java.vm.name": "OpenJDK 64-Bit Server VM",
    "java.vm.version": "11.0.22+7-post-Ubuntu-0ubuntu222.04.1",
    "os.name": "Linux",
    "os.version": "5.15.0-107-generic",
    "user.language": "en",
    "user.timezone": "Europe/Paris"
  },
  "metabase-info": {
    "databases": [
      "mysql",
      "h2"
    ],
    "hosting-env": "unknown",
    "application-database": "postgres",
    "application-database-details": {
      "database": {
        "name": "PostgreSQL",
        "version": "16.3 (Ubuntu 16.3-1.pgdg22.04+1)"
      },
      "jdbc-driver": {
        "name": "PostgreSQL JDBC Driver",
        "version": "42.7.2"
      }
    },
    "run-mode": "prod",
    "version": {
      "date": "2024-05-13",
      "tag": "v0.49.10",
      "hash": "9e8fc83"
    },
    "settings": {
      "report-timezone": "Europe/Paris"
    }
  }
}
33

Hello, I have exactly the same problem here on metabase v0.49.11 against an Athena database