Hi team, Issue: In one of our use case to query pinot we were using pinot-java-client-0.6.0 where protocol scheme '*http*' is hardcoded, this setup used to work with our inhouse pinot queried via svc(k8) endpoint. Now, After migration of brokers to a different VPC, it was exposed via this url https://broker.xyz.cloud (using https), which the existing cient

pinot-java-client-0.6.0

couldnt connect. What didnt work: Updating pinot-java-client dependency to 0.7.1 or later in our usecase didnt work for us, as it was breaking other parts of the implementation Fix: To find a workable fix we updated the url to "https://" in JsonAsyncHttpPinotClientTransport of pinot java client 0.6.0 and repacked it as a new artifact

pinot-java-client-0.6.0-tls.jar

, As of today we are using this jar in build gradle as file(..) import, which still is a dirtyway to use a dependency, Would like to know from the team if we can have this change pushed somwehere in mvnreposiroty or any other Repository Manager, or any cleaner approach because all we needed was https instead of http The above fix works perfectly!

Hi @shivam , thanks for the fix! This looks good! Since the project is moving forward about 20 months from this release, we may not consider a public fix or release for this. In terms of hosting the artifact, one place I can suggest is to use https://jitpack.io/ . You can publish the artifactory there and let other people use it by adding the jitpack repository.