Closed sean-k1 closed 9 months ago
PTAL, @osheroff I desperately need this feature. Optional meta data in table map events holds invaluable data and users will benefit so much from correctly parsing it. I can't wait this PR to be merged!
hi, sorry for the delay,
can you please write an integration test that shows the issue clearly? Your patch looks ok -- although it'd be better if we could avoid another for-all-columns loop and the ArrayList
allocation -- but I'd like to be able to verify this against a running server.
thnx
@osheroff hello
If we add a function to the TableMapEventMetadataDeserializer class that takes ColumnType information as a parameter and that determines if it's numeric, we can eliminate the part where we allocate an ArrayList. But this codes.. It seems like this may not be the best structure for writing test code. If this approach is better, I'll modify code
and i added integration Test too
@osheroff Can you check my PR?
@osheroff PTAL
@osheroff It takes a month 🥲
@osheroff I know you're busy but I think it's high time you appoint additional maintainer. I think @sean-k1 is one of the most competent candidates. He has conducted a comprehensive walkthrough of the project and understands every aspect of it. And on top of everything, he is a maintainer and active contributor of python-mysql-replication. He is an expert in MySQL replication.
I was implementing optional_metadata field in table_map_event for python-mysql-replication.
Changes
Reason
optional metadata type SIGNEDNESS case The order of indices in the Inputstream corresponds to the order of numeric columns So we need to map the index to all columns index(include non numeric type columns)
Examples
SIGNEDNESS bit map now result is signedness={0, 2}, but we expect result should be signedness={0, 3}, Because test3 table column col1 and col4 are unsigned
AS-IS
TO-BE