qingdao81 commented on pull request #15808: URL: https://github.com/apache/flink/pull/15808#issuecomment-848950902
Good question - I just had a closer look into the confluent serializer code. Confluent has their own implementation of a `RestService` which takes care about http requests to the schema registry. The changes I did so far will only make sure that the ssl properties are forwarded to the `SslFactory` which is used by the `RestService`. I can add another change that auth properties are forwarded to the `RestService` as well. I can not really tell you if this then solves the issue from the stackoverflow thread which you mentioned, but in theory it should. But I also don't really know how that works in combination with the TableEnvironment. For the StreamingEnvironment it was not possible to provide any config properties (except the schema registry url) to the (de)serializer. But in your example you already provide a bunch of properties. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
