[ 
https://issues.apache.org/jira/browse/FLINK-3923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15296391#comment-15296391
 ] 

ASF GitHub Bot commented on FLINK-3923:
---------------------------------------

Github user rmetzger commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2016#discussion_r64227104
  
    --- Diff: 
flink-streaming-connectors/flink-connector-kinesis/src/main/java/org/apache/flink/streaming/connectors/kinesis/FlinkKinesisProducer.java
 ---
    @@ -30,14 +28,20 @@
     import org.apache.flink.api.java.ClosureCleaner;
     import org.apache.flink.configuration.Configuration;
     import org.apache.flink.streaming.api.functions.sink.RichSinkFunction;
    +import 
org.apache.flink.streaming.connectors.kinesis.config.KinesisConfigConstants;
     import 
org.apache.flink.streaming.connectors.kinesis.serialization.KinesisSerializationSchema;
    +import org.apache.flink.streaming.connectors.kinesis.util.AWSUtil;
    +import 
org.apache.flink.streaming.connectors.kinesis.util.KinesisConfigUtil;
     import org.apache.flink.streaming.util.serialization.SerializationSchema;
     import org.slf4j.Logger;
     import org.slf4j.LoggerFactory;
     
     import java.nio.ByteBuffer;
     import java.util.List;
     import java.util.Objects;
    +import java.util.Properties;
    +
    +import static com.google.common.base.Preconditions.checkNotNull;
    --- End diff --
    
    Can you use `Objects.requireNonNull()` instead?
    
    We are trying to get rid of Guava in the long term


> Unify configuration conventions of the Kinesis producer to the same as the 
> consumer
> -----------------------------------------------------------------------------------
>
>                 Key: FLINK-3923
>                 URL: https://issues.apache.org/jira/browse/FLINK-3923
>             Project: Flink
>          Issue Type: Sub-task
>          Components: Kinesis Connector, Streaming Connectors
>    Affects Versions: 1.1.0
>            Reporter: Robert Metzger
>            Assignee: Abdullah Ozturk
>
> Currently, the Kinesis consumer and producer are configured differently.
> The producer expects a list of arguments for the access key, secret, region, 
> stream. The consumer is accepting properties (similar to the Kafka connector).
> The objective of this issue is to change the producer so that it is also 
> using a properties-based configuration (including an input validation step)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to