[
https://issues.apache.org/jira/browse/CALCITE-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16476155#comment-16476155
]
ASF GitHub Bot commented on CALCITE-2284:
-----------------------------------------
Github user aaraujo commented on the issue:
https://github.com/apache/calcite-avatica/pull/46
> I'm not sure if Java can handle this with binary compatibility or not.
Java seems to provide backwards compat for the raw API by adding additional
methods to class files during compile time. This is consistent with my local
testing.
> If Java doesn't insulate us from this change, we'll have to make this
change in a new HttpServer+Builder pair
Happy to add a new pair, to be safe, if that eases your concern.
> Allow Jetty Server to be customized before startup
> --------------------------------------------------
>
> Key: CALCITE-2284
> URL: https://issues.apache.org/jira/browse/CALCITE-2284
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Affects Versions: 1.11.0
> Reporter: Alex Araujo
> Priority: Critical
> Attachments: CALCITE-2284.patch
>
>
> Avatica server options currently allow users to enable TLS with file based
> key stores. In order to support additional options (in memory keystores,
> dynamically loaded keys/certificates, etc.) Avatica should provide a callback
> to customize the embedded Jetty server before starting it up.
>
> This would be similar to how Spring Boot allows developers to customize the
> embedded server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
