[
https://issues.apache.org/jira/browse/ASTERIXDB-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392347#comment-17392347
]
Ingo Müller commented on ASTERIXDB-2940:
----------------------------------------
Nope, I celebrated too early. I am able to _create_ my external table correctly
but I cannot query it. When I try, I get the following error:
{{ERROR: Code: 1 "ASX1108: External source error. Unable to execute HTTP
request: Connect to ingo-root-playground.s3.eu-west-1.amazonaws.com:443
[ingo-root-playground.s3.eu-west-1.amazonaws.com/52.218.30.168] failed: Connect
timed out"}}
I got this type of error during the creation of the table before finding out
about {{JAVA_OPTS}}, so I suppose that the {{JAVA_OPTS}} are not propagated to
all involved processes. Indeed, {{ps}} shows that {{asterixcc}} and
{{asterixncservice}} are started with my proxy flags but {{asterixnc}} is not.
Is there an established practice to pass flags to those processes?
> Make HTTP proxy of S3 client configurable
> -----------------------------------------
>
> Key: ASTERIXDB-2940
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2940
> Project: Apache AsterixDB
> Issue Type: Improvement
> Components: EXT - External data
> Affects Versions: 0.9.8
> Reporter: Ingo Müller
> Priority: Major
>
> It would be great if the S3 client used for external data set would work
> behind corporate proxies. The ClientConfiguration class of the AWS SDK has a
> number of attributes that should make that work easily (see
> [setProxyDomain|https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/ClientConfiguration.html#setProxyDomain-java.lang.String-]
> and similar), however, these must be set by the application (I suppose that
> this would happen in buildAwsS3Client).
> Any other method to enable AsterixDB to access S3 through a proxy should be
> fine too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
