[
https://issues.apache.org/jira/browse/FLINK-3933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15291024#comment-15291024
]
ASF GitHub Bot commented on FLINK-3933:
---------------------------------------
Github user aljoscha commented on a diff in the pull request:
https://github.com/apache/flink/pull/2010#discussion_r63869803
--- Diff: docs/apis/streaming/connectors/kafka.md ---
@@ -142,18 +142,24 @@ for querying the list of topics and partitions.
For this to work, the consumer needs to be able to access the consumers
from the machine submitting the job to the Flink cluster.
If you experience any issues with the Kafka consumer on the client side,
the client log might contain information about failed requests, etc.
-##### The `DeserializationSchema`
+##### **The `DeserializationSchema`**
--- End diff --
`kafka.md` uses very low level headings. The batch and streaming guides use
level 2 headings for top-level headings while `kafka.md` uses level 4. I think
the solution is to reduce heading level by 2 on all levels in this document,
which would yield
```
### The `DeserializationSchema`
```
> Add an auto-type-extracting DeserializationSchema
> -------------------------------------------------
>
> Key: FLINK-3933
> URL: https://issues.apache.org/jira/browse/FLINK-3933
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 1.0.0
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 1.1.0
>
>
> When creating a {{DeserializationSchema}}, people need to manually worry
> about how to provide the produced type's {{TypeInformation}}.
> We should add a base utility {{AbstractDeserializationSchema}} that provides
> that automatically via the type extractor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
