[
https://issues.apache.org/jira/browse/KAFKA-3846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15435842#comment-15435842
]
Michael Andre Pearce (IG) commented on KAFKA-3846:
--------------------------------------------------
This looks great, is any documents updated to show how we configure bits like
TimebasedPartitioner mentioned here
http://docs.confluent.io/3.0.0/connect/connect-hdfs/docs/configuration_options.html
to use this?
Also is it possible to store this timestamp ( and other meta) in the hdfs/hive
record it seems we can only store the payload. From the config options in
connect.
> Connect record types should include timestamps
> ----------------------------------------------
>
> Key: KAFKA-3846
> URL: https://issues.apache.org/jira/browse/KAFKA-3846
> Project: Kafka
> Issue Type: Improvement
> Components: KafkaConnect
> Affects Versions: 0.10.0.0
> Reporter: Ewen Cheslack-Postava
> Assignee: Shikhar Bhushan
> Labels: needs-kip
> Fix For: 0.10.1.0
>
>
> Timestamps were added to records in the previous release, however this does
> not get propagated automatically to Connect because it uses custom wrappers
> to add fields and rename some for clarity.
> The addition of timestamps should be trivial, but can be really useful (e.g.
> in sink connectors that would like to include timestamp info if available but
> when it is not stored in the value).
> This is public API so it will need a KIP despite being very uncontentious.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
