[
https://issues.apache.org/jira/browse/SAMZA-1793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shanthoosh Venkataraman updated SAMZA-1793:
-------------------------------------------
Description:
Kafka consumer:
1. Samza currently uses SimpleConsumer to consume messages from the
KafkaBroker. However, the SimpleConsumer API is deprecated and is slated to be
removed in future kafka-clients release. It's essential to migrate to
KafkaConsumer api sooner to continue kafka connector support in samza.
2. Internally within linkedIn, samza framework uses KafkaConsumer api. There's
a ongoing effort for building release tests within linkedin. By having
uniformity of API usage between OSS and internal linkedin branches, it will be
easy to port internal release tests to open source. It makes easy to port
internal stability fixes from internal LI release to OSS.
Kafka Producer:
Since 0.10.1, Kafka’s messages can carry timestamps, indicating the time the
event has occurred or the time when the message has been written to the Kafka
broker. This is essential to support rewinding of checkpoints based upon time.
was:
Kafka consumer:
1. Samza currently uses SimpleConsumer to consume messages from the
KafkaBroker. However, the SimpleConsumer API is deprecated and is slated to be
removed in future kafka-clients release. It's essential to migrate to
KafkaConsumer api sooner to continue kafka connector in samza.
2. Internally within linkedIn, samza framework uses KafkaConsumer api. There's
a ongoing effort for building release tests within linkedin. By having
uniformity of API usage between OSS and internal linkedin branches, it will be
easy to port internal release tests to open source. It makes easy to port
internal stability fixes from internal LI release to OSS.
Kafka Producer:
Since 0.10.1, Kafka’s messages can carry timestamps, indicating the time the
event has occurred or the time when the message has been written to the Kafka
broker. This is essential to support rewinding of checkpoints based upon time.
> Upgrade to recent API for kafka consumer / producer.
> ----------------------------------------------------
>
> Key: SAMZA-1793
> URL: https://issues.apache.org/jira/browse/SAMZA-1793
> Project: Samza
> Issue Type: New Feature
> Reporter: Shanthoosh Venkataraman
> Assignee: Shanthoosh Venkataraman
> Priority: Major
>
> Kafka consumer:
> 1. Samza currently uses SimpleConsumer to consume messages from the
> KafkaBroker. However, the SimpleConsumer API is deprecated and is slated to
> be removed in future kafka-clients release. It's essential to migrate to
> KafkaConsumer api sooner to continue kafka connector support in samza.
> 2. Internally within linkedIn, samza framework uses KafkaConsumer api.
> There's a ongoing effort for building release tests within linkedin. By
> having uniformity of API usage between OSS and internal linkedin branches, it
> will be easy to port internal release tests to open source. It makes easy to
> port internal stability fixes from internal LI release to OSS.
> Kafka Producer:
> Since 0.10.1, Kafka’s messages can carry timestamps, indicating the time the
> event has occurred or the time when the message has been written to the Kafka
> broker. This is essential to support rewinding of checkpoints based upon time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
