Evidence MySQL source and compatibility checks

Start with the shared setup and dataset. The versioned observations below use the MatrixOne build identified in the overview.

Configure a source

Create an Evidence project following the upstream datasource documentation. Enable the MySQL source plugin; the tested package was @evidence-dev/mysql 1.1.6.

Create sources/matrixone/connection.yaml:

name: matrixone
type: mysql
options:
  host: MO_HOST
  port: 6001
  database: bi_tutorial
  user: MO_USER
  password: REPLACE_WITH_PASSWORD
  ssl: "false"

The SSL setting above reproduces only a local non-TLS test. Configure TLS according to the connector’s supported settings for remote use. Keep credentials in private local configuration or the deployment’s secret mechanism rather than a published project.

If the native connection succeeds on your versions, place the shared category SQL in sources/matrixone/category_net.sql. Refresh sources with the project’s source command, typically npm run sources, and inspect the extracted rows before building a page. A page can then query matrixone.category_net for its two rows, subject to the installed Evidence project’s query syntax. Extraction and page-local queries are separate from execution on MatrixOne.

Known limitation and numeric transport

The unmodified source connector failed its native queries with Can't add new command when connection is in closed state on the tested MatrixOne build. A diagnostic replacement of mysql2.createConnection options with a general collation enabled the query control, but this changed application runtime behavior and is not a supported setup instruction.

Package 1.1.6 forwards user/host/database/password/port/socket and SSL settings, but does not forward an arbitrary charset option from the source configuration. Adding charset to the YAML is not an established fix. The independent collation controls and #29206 provide background; they do not prove that Grafana and Evidence have identical failure causes.

The connector also enables decimalNumbers: true, which converts Decimal to JavaScript numbers. The diagnostic query path lost material precision on some large/high-precision values. Verify the large-Decimal check after extraction. Native Evidence report builds and browser pages were not verified on the blocked combination; do not treat the diagnostic query result as a working end-to-end tutorial.