julien-duponchelle / julien-duponchelle/python-mysql-replication
Assertion Error
- Dominant language
- Python
- Stars
- 2.4k
- Forks
- 690
- PR merge metrics
- No merged PRs in 30d
Description
### Version
Please specify the versions you are using. Exact version numbers are preferred.
- Pymyrepl (e.g., 1.0.2):
- OS (e.g., Ubuntu 18.04):
- Database and version (Remove unnecessary options):
- MySQL: 10.23
- MariaDB: 5.3
- `binlog_row_metadata`: None
### Symptoms
I have a prod db, where somw insert queries are running on top of it, I am trying to replicate in snowflake. But while reading the insert event, while getting binlog_event.event.rows throwing
Assertion Error
Expected = 111. Actual = 46. Position=130. Data=176
And I am getting the assertion error for column type varchar,
### Steps to Reproduce
I cannot help you in reproducing as I am testing in prod environment
I tried with many version degrading and upgrading with all the modules such as pymysql, mysql-replication, s3, etc..
Contributor guide
Research direction
The report points to binlog_event.event.rows and a varchar assertion with expected 111 versus actual 46 at position 130, but names no source file or test. Start by locating the row-event parsing entry point and inspect how the column metadata is interpreted; done means reproducing the assertion with a representative binlog event and identifying a verified fix or a precise missing reproduction detail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mysql, python
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100