[
https://issues.apache.org/jira/browse/IGNITE-4198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15653036#comment-15653036
]
ASF GitHub Bot commented on IGNITE-4198:
----------------------------------------
GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1225
IGNITE-4198: Kafka Connect sink option to transform Kafka values.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite ignite-4198
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1225.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 #1225
----
commit 0fffdf71dfbaa3d7e551fd2e5b70c1d3f0f71839
Author: shtykh_roman <[email protected]>
Date: 2016-11-10T04:52:07Z
IGNITE-4198: Kafka Connect sink option to transform Kafka values.
----
> Ignite Kafka sink connector should have an option to transform Kafka values
> ---------------------------------------------------------------------------
>
> Key: IGNITE-4198
> URL: https://issues.apache.org/jira/browse/IGNITE-4198
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Shtykh
> Assignee: Roman Shtykh
>
> Currently the connector takes a Kafka key and uses it as an Ignite key.
> However, Kafka keys can be null, and users may want to specify an Ignite key
> from the value object.
> Instead of creating a new transformer interface, I think we can use
> {{StreamMultipleTupleExtractor}} whenever its implementation is specified by
> the user in connector config file.
> http://apache-ignite-users.70518.x6.nabble.com/Kafka-Failed-to-stream-a-record-with-null-key-td8731.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
