[
https://issues.apache.org/jira/browse/FLINK-9188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16451809#comment-16451809
]
ASF GitHub Bot commented on FLINK-9188:
---------------------------------------
Github user tzulitai commented on a diff in the pull request:
https://github.com/apache/flink/pull/5889#discussion_r183965718
--- Diff:
flink-connectors/flink-connector-kinesis/src/test/java/org/apache/flink/streaming/connectors/kinesis/proxy/KinesisProxyTest.java
---
@@ -86,4 +86,19 @@ protected AmazonKinesis createKinesisClient(Properties
configProps) {
assertEquals(10000, clientConfiguration.getSocketTimeout());
}
+ @Test
+ public void testClientConfigOverride() {
+
+ Properties configProps = new Properties();
+ configProps.setProperty(AWSConfigConstants.AWS_REGION,
"us-east-1");
+ configProps.setProperty(AWSUtil.AWS_CLIENT_CONFIG_PREFIX +
"socketTimeout", "9999");
--- End diff --
Would this usage also subsume other commonly seen settings, such as setting
the AWS crredentials?
Currently we have these explicitly defined keys in `AWSConfigConstants`,
for which we might be able to get rid of (because we have to maintain the set
of config keys ourselves, which is not nice and hard to meet with all the
functionalities that KCL provides).
If so, we might also want tests + update our documents for those.
> Provide a mechanism to configure AmazonKinesisClient in FlinkKinesisConsumer
> ----------------------------------------------------------------------------
>
> Key: FLINK-9188
> URL: https://issues.apache.org/jira/browse/FLINK-9188
> Project: Flink
> Issue Type: Task
> Components: Kinesis Connector
> Reporter: Thomas Weise
> Priority: Major
>
> It should be possible to control the ClientConfiguration to set socket
> timeout and other properties.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
