onestep-mysql

Deprecation notice (issue #133): onestep-mysql is now a thin forwarding shim that delegates to the canonical onestep-sql package. New deployments should install onestep-sql[mysql] (or onestep[mysql]) and import from onestep_sql.mysql. This package remains available so existing pip install onestep-mysql and from onestep_mysql import ... keep working unchanged; it no longer declares its own resource entry point. All 14 YAML resource type names are unchanged. See the migration guide for details.

MySQL connector plugin for onestep.

pip install onestep-mysql
# or the canonical package
# pip install 'onestep-sql[mysql]'

The package registers these YAML resource types through the onestep.resources entry point:

• mysql
• mysql_state_store
• mysql_cursor_store
• mysql_table_queue
• mysql_incremental
• mysql_binlog
• mysql_table_sink

Python usage:

from onestep_mysql import MySQLConnector

SQLAlchemy database operations use AsyncEngine and async drivers. Existing mysql:// and mysql+pymysql:// DSNs are accepted and are automatically adapted to the asyncmy dialect. SQLite is supported in tests and local development through aiosqlite. The binlog reader remains isolated behind a thread boundary because mysql-replication is a synchronous library.

Production mysql_incremental sources should bind a durable mysql_cursor_store with an explicit stable state_key. Retries redeliver the same logical row with incremented attempts and pause later SQL reads across the gap. Concurrent acknowledgements advance only a contiguous prefix and are coalesced into cursor-store commit waves.