[
https://issues.apache.org/jira/browse/FLINK-3524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15208337#comment-15208337
]
ASF GitHub Bot commented on FLINK-3524:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/1834
[FLINK-3524] [kafka] Add JSONDeserializationSchema
This PR adds a JSON[KeyValue]DeserializationSchema to the kafka connector,
which can be used to more easily read JSON data from Kafka. Instead of having
to read them as strings and creating parsers themselves a user can now delegeta
this to the DeserializationSchema, saving the string allocation and possible
instantiation of multiple parser factories.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 3524_json_schema
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1834.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1834
----
commit 536b2888f1f8fa0a76753e0245378ceb0d242ef1
Author: zentol <[email protected]>
Date: 2016-03-23T10:24:50Z
[FLINK-3524] [kafka] Add JSONDeserializationSchema
----
> Provide a JSONDeserialisationSchema in the kafka connector package
> ------------------------------------------------------------------
>
> Key: FLINK-3524
> URL: https://issues.apache.org/jira/browse/FLINK-3524
> Project: Flink
> Issue Type: Improvement
> Components: Kafka Connector
> Reporter: Robert Metzger
> Assignee: Chesnay Schepler
> Labels: starter
>
> (I don't want to include this into 1.0.0)
> Currently, there is no standardized way of parsing JSON data from a Kafka
> stream. I see a lot of users using JSON in their topics. It would make things
> easier for our users to provide a serializer for them.
> I suggest to use the jackson library because we have that aready as a
> dependency in Flink and it allows to parse from a byte[].
> I would suggest to provide the following classes:
> - JSONDeserializationSchema()
> - JSONDeKeyValueSerializationSchema(bool includeMetadata)
> The second variant should produce a record like this:
> {code}
> {"key": "keydata",
> "value": "valuedata",
> "metadata": {"offset": 123, "topic": "<topic>", "partition": 2 }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
