MySQL Bugs: #117126: Hang when fetching data from specific MySQL views after upgrading to v9.1.0

Bug #117126	Hang when fetching data from specific MySQL views after upgrading to v9.1.0
Submitted:	8 Jan 4:07	Modified:	13 Jan 9:08
Reporter:	KOTE WATARU	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / Python	Severity:	S3 (Non-critical)
Version:	9.1.0	OS:	Debian (docker image : apache/beam_python3.11_sdk:2.60.0)
Assigned to:	Philip Olson	CPU Architecture:	x86

Description:
I am using this package to fetch data from MySQL on Google Cloud Dataflow. After upgrading the package version from 8.3.0 to 9.1.0, I encountered an issue where the process hangs specifically when fetching data from certain views.

Environment

- Previous version: `8.3.0`
- Current version: `9.1.0`
- Platform: Google Cloud Dataflow
- Database: MySQL (no changes on DB side)

Expected Behavior

Data should be fetched from MySQL views without hanging.

Current Behavior

The process hangs indefinitely when attempting to fetch data from specific views.

Additional Information

- No changes were made to the database configuration or schema
- I can provide information about related package versions if needed

How to repeat:
To reproduce this issue:

1. Set up a Google Cloud Dataflow environment with the package version 9.1.0
2. Create a simple pipeline that reads from a MySQL view
3. Execute the pipeline

Note: The issue appears to be environment-specific and may depend on:
- The complexity of the view query
- The volume of data being processed
- Network configuration between Dataflow and MySQL

For debugging purposes, I can provide:
- Simplified view definition structure (without sensitive data)
- Basic pipeline configuration
- Relevant log snippets

Please let me know if you need any specific information to investigate this issue further.

Hi Mr. WATARU,

Thank you for your bug report.

However, let us inform you that this is a forum for the reports with fully repeatable test cases. Each test case should consist of the set of SQL statements and and example of the program that you wrote with our C/Python  Connector.

Simply, we can not proceed without fully repeatable test case and you have not provided us with one !!!!!

Thanks in advance.

Dear Support Team,

I apologize for submitting a bug report without a fully reproducible test case. I understand this makes it difficult to investigate the issue properly.

Since we have found a workaround for our current situation, I will hold off on this report for now. Should we encounter this issue again, I will make sure to provide a complete test case with the necessary SQL statements and connector program code.

Thank you for your prompt and clear response. I appreciate your guidance on the bug reporting requirements.

Hi Mr. Watabu,

There is no need for you to apologise for anything .......

We will wait as much as it is necessary for you to prepare a repeatable test case.

With kind regards ......