You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Dariusz Seweryn (Jira)" <ji...@apache.org> on 2026/03/04 10:14:00 UTC

[jira] [Resolved] (NIFI-14292) ConsumeKinesisStream revisit SessionFactory living time in onTrigger

     [ https://issues.apache.org/jira/browse/NIFI-14292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dariusz Seweryn resolved NIFI-14292.
------------------------------------
    Fix Version/s: 2.7.0
       Resolution: Abandoned

Advised migration to ConsumeKinesis processor

> ConsumeKinesisStream revisit SessionFactory living time in onTrigger
> --------------------------------------------------------------------
>
>                 Key: NIFI-14292
>                 URL: https://issues.apache.org/jira/browse/NIFI-14292
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Dariusz Seweryn
>            Priority: Major
>             Fix For: 2.7.0
>
>
> A Scheduler is created in `onTrigger()` method. This Scheduler has a Record Processor implementation passed at the creation time. 
> Record Processor implementations for ConsumeKinesisStream have a strong reference on the `SessionFactory` passed in `onTrigger()` method — which is not ideal.
> Possible ways forward:
>  * Exchange SessionFactory on each call of `onTrigger()`.
>  * Remove dependency on SessionFactory in the processors but make them buffer of records. Processing would happen in `onTrigger()`. Tracking checkpoints may be non-trivial.
>  
> See this [PR comment|https://github.com/apache/nifi/pull/9737#issuecomment-2675170481]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)