Jack Tuck created FLINK-13111:
---------------------------------
Summary: FlinkKinesisProducer fails with endpoint and region used together
Key: FLINK-13111
URL:
https://issues.apache.org/jira/browse/FLINK-13111 Project: Flink
Issue Type: Bug
Reporter: Jack Tuck
So far I have followed the instructions documented for Flink's kinesis connector to use a local Kinesis. (Using Flink 1.8 and Kinesis connector 1.8)
[
https://ci.apache.org/projects/flink/flink-docs-stable/dev/connectors/kinesis.html#using-non-aws-kinesis-endpoints-for-testing]
{code:java}
Properties producerConfig = new Properties();
producerConfig.put(AWSConfigConstants.AWS_REGION, "us-east-1");
producerConfig.put(AWSConfigConstants.AWS_ACCESS_KEY_ID, "aws_access_key_id");
producerConfig.put(AWSConfigConstants.AWS_SECRET_ACCESS_KEY, "aws_secret_access_key");
producerConfig.put(AWSConfigConstants.AWS_ENDPOINT, "
http://localhost:4567");{code}
With a Flink consumer, these instructions work and I can consume from local kinesis (I use Kinesalite).
However, with a Flink producer, I get an exception that `aws.region` and `aws.endpoint` are not *both* allowed.
Is this a bug in the connector? I found the PR which fixed this error for the consumer but not the producer
https://github.com/apache/flink/pull/6045 .
I found a [workaround on Flink's mailing list](
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Can-t-get-the-FlinkKinesisProducer-to-work-against-Kinesalite-for-tests-td23438.html) but it uses SSL and i can't use it in my case.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
