[
https://issues.apache.org/jira/browse/FLINK-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708074#comment-14708074
]
ASF GitHub Bot commented on FLINK-2558:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/1040#discussion_r37697052
--- Diff: docs/apis/streaming_guide.md ---
@@ -1517,11 +1517,24 @@ Stream connectors
----------------
<!-- TODO: reintroduce flume -->
-Connectors provide an interface for accessing data from various third
party sources (message queues). Currently three connectors are natively
supported, namely [Apache Kafka](https://kafka.apache.org/),
[RabbitMQ](http://www.rabbitmq.com/) and the [Twitter Streaming
API](https://dev.twitter.com/docs/streaming-apis).
+Connectors provide code for interfacing with various third-party systems.
+Currently these systems are supported:
-Typically the connector packages consist of a source and sink class (with
the exception of Twitter where only a source is provided). To use these sources
the user needs to pass Serialization/Deserialization schemas for the connectors
for the desired types. (Or use some predefined ones)
+ * [Apache Kafka](https://kafka.apache.org/)
--- End diff --
Should we add source/sink, to show which types of connectors are
im`plemented for which systems?
We can also add Java/Scala collections and file systems (HDFS) to that list.
> Add Streaming Connector for Elasticsearch
> -----------------------------------------
>
> Key: FLINK-2558
> URL: https://issues.apache.org/jira/browse/FLINK-2558
> Project: Flink
> Issue Type: Improvement
> Components: Streaming
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Fix For: 0.10
>
>
> We should add a sink that can write to Elasticsearch. A source does not seem
> necessary because Elasticsearch would mostly be used for accessing results,
> for example using a dashboard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
