tilgalas opened a new issue, #30610:
URL: https://github.com/apache/beam/issues/30610

   ### What needs to happen?
   
   Right now the confluent dependency version is set at 5.3.2, which is quite 
old (5 years or so) - one feature that we recently discovered is missing in 
this version is the support for configuring schema registry client's ssl 
configuration - according to the (current) docs 
(https://docs.confluent.io/platform/current/installation/configuration/consumer-configs.html)
 there's a whole bunch of configuration keys starting with a "ssl." prefix that 
dictate how a schema registry client might access the schema registry - the 
issue is that support for those config keys on the client side had only been 
added starting from version 5.4.0 IIUC 
(https://github.com/confluentinc/schema-registry/pull/957). Without it, the ssl 
has to be configured using standard JVM classes such as SSLContext or 
HttpsURLConnection, which on top of being slightly unintuitive is also 
undocumented.
   
   The goal of this task is to update the confluent libraries  to a version as 
high as possible, hopefully even as high as 7.6.0 (which is the most recent 
one, from what I gather), and successfully run tests and build the extension. 
   
   ### Issue Priority
   
   Priority: 3 (nice-to-have improvement)
   
   ### Issue Components
   
   - [ ] Component: Python SDK
   - [X] Component: Java SDK
   - [ ] Component: Go SDK
   - [ ] Component: Typescript SDK
   - [X] Component: IO connector
   - [ ] Component: Beam YAML
   - [ ] Component: Beam examples
   - [ ] Component: Beam playground
   - [ ] Component: Beam katas
   - [ ] Component: Website
   - [ ] Component: Spark Runner
   - [ ] Component: Flink Runner
   - [ ] Component: Samza Runner
   - [ ] Component: Twister2 Runner
   - [ ] Component: Hazelcast Jet Runner
   - [ ] Component: Google Cloud Dataflow Runner


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to