You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Andrei Sereda (Jira)" <ji...@apache.org> on 2019/09/11 23:11:00 UTC
[jira] [Resolved] (CALCITE-3335) Connecting on ElasticSearch server
on HTTPS
[ https://issues.apache.org/jira/browse/CALCITE-3335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrei Sereda resolved CALCITE-3335.
------------------------------------
Resolution: Fixed
Fixed in [f6aa7a927f|https://github.com/apache/calcite/commit/f6aa7a927feaa88bd4076f9098203346b89ae80d]
> Connecting on ElasticSearch server on HTTPS
> -------------------------------------------
>
> Key: CALCITE-3335
> URL: https://issues.apache.org/jira/browse/CALCITE-3335
> Project: Calcite
> Issue Type: Improvement
> Components: elasticsearch-adapter
> Affects Versions: 1.21.0
> Reporter: Shikha Somani
> Assignee: Andrei Sereda
> Priority: Major
> Labels: aws, elasticsearch, pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently Calcite assumes that elasticsearch server will be exposed on HTTP only. So, it initializes HTTP host with default scheme i.e. HTTP. [Code|https://github.com/apache/calcite/blob/master/elasticsearch/src/main/java/org/apache/calcite/adapter/elasticsearch/ElasticsearchSchemaFactory.java#L86]
> If a ElasticSearch server is on HTTPS, connection to it fails with below exception:
> Caused by: java.net.UnknownHostException
>
> This is evident when trying to connect on AWS ElasticSearchService which is exposed only on HTTPS.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)