flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tzulitai <...@git.apache.org>
Subject [GitHub] flink pull request #2227: [FLINK-4197] Allow Kinesis endpoint to be overridd...
Date Tue, 12 Jul 2016 15:09:21 GMT
Github user tzulitai commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2227#discussion_r70457990
  
    --- Diff: docs/apis/streaming/connectors/kinesis.md ---
    @@ -299,3 +299,41 @@ Otherwise, the returned stream name is used.
     Other optional configuration keys can be found in `KinesisConfigConstants`.
     		
     		
    +### Using non-AWS Kinesis Endpoints
    +
    +It is sometimes desirable to have Flink operate as a consumer or producer against a non-AWS
Kinesis endpoint such as kinesalite; this is especially useful when performing functional
testing of a Flink application. The AWS endpoint that would normally be inferred by the AWS
region set in the Flink configuration must be overriden via a configuration property.
    --- End diff --
    
    We should be linking "kinesalite" to the project. Should we also capitalize "K"?
    
    However, I'm not sure if it's a good idea to refer to another public Github project in
the documentation, even though Kinesalite is a widely adopted solution for local Kinesis testing.
We'll need to have @rmetzger 's comment on this. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message