nifi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (NIFI-1296) Add capabilities to Kafka NAR to use new Kafka API (0.9)
Date Thu, 19 May 2016 11:36:13 GMT


ASF subversion and git services commented on NIFI-1296:

Commit 2d03489ec5dbc56bcb0dbd7b694cdf030d2532a5 in nifi's branch refs/heads/master from [~ozhurakousky]
[;h=2d03489 ]

NIFI-1296, NIFI-1680, NIFI-1764, NIFI-1837, NIFI-1827, NIFI-1699  implemented new  Kafka processors
that leverage Kafka 0.9 API
- Improved StreamScanner for better performance
- Renamed StreamScanner to StreamDemarcator as suggested by Joe
- Added failure handling logic to ensure both processors can be reset to their initial state
(as if they were just started)
- Provided comprehensive test suite to validate various aspects of both Publish and Consume
from Kafka
- Added relevant javadocs
- Added initial additionalDetails docs
- Addressed NPE reported by NIFI-1764
- Life-cycle refactoring for the existing PutKafka to ensure producer restart after errors
- Incorporated code changes contributed by Ralph Perko (see NIFI-1837)
- Addressed partition issue in RoundRobinPartitioner discussed in NIFI-1827
- Updated PropertyDescriptor descriptions to reflect their purpose

NIFI-1296 added @Ignore on some Kafka tests to improve test time

NIFI-1296 reworked tests to avoid dependency on embedded Kafka

NIFI-1296 fixed spelling error

NIFI-1296 fixed trailing whitespaces in non-java files

This closes #366

> Add capabilities to Kafka NAR to use new Kafka API (0.9)
> --------------------------------------------------------
>                 Key: NIFI-1296
>                 URL:
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 0.4.0
>            Reporter: Oleg Zhurakousky
>            Assignee: Oleg Zhurakousky
>             Fix For: 0.7.0
> Not sure when can we address this, but the interesting comment in
The usage of new API may introduce issues with running against older Kafka brokers (e.g.,
0.8). Need to investigate.

This message was sent by Atlassian JIRA

View raw message