mina-asham opened a new pull request, #26008:
URL: https://github.com/apache/flink/pull/26008

   Note: Still waiting on JIRA account to open the issue
   
   ## What is the purpose of the change
   
   Replace deprecated avro-python3 with avro
   - avro-python3 was deprecated and replaced by avro, the first hasn't had a 
release since March 17, 2021 while the second has had multiple fixes and 
updated, latest is August 5, 2024
   - Both libraries are the exact same (i.e. `avro-python3` was just renamed to 
`avro` and had multiple updates since), but the problem is that they overlap in 
package name, so using PyFlink with any updated library that relies on `avro` 
fails starting the pipeline even if the pipeline doesn't actually do any avro 
encoding/decoding
   - This updates the library to the latest one, and fixes a few imports, other 
than that the library's functionality is exactly the same
   
   ## Brief change log
   
   - Replace `avro-python3` (deprecated since 2021) with `avro` in PyFlink
   
   ## Verifying this change
   
   This change is already covered by existing tests, such as all the existing 
avro tests
   
   ## Does this pull request potentially affect one of the following parts:
   
     - Dependencies (does it add or upgrade a dependency): yes
     - The public API, i.e., is any changed class annotated with 
`@Public(Evolving)`: no
     - The serializers: no
     - The runtime per-record code paths (performance sensitive): no
     - Anything that affects deployment or recovery: JobManager (and its 
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
     - The S3 file system connector: no
   
   ## Documentation
   
     - Does this pull request introduce a new feature? no
     - If yes, how is the feature documented? not applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to