You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2024/01/02 19:01:00 UTC

[jira] [Commented] (NIFI-12558) Upgrade Jagged to 0.3.0

    [ https://issues.apache.org/jira/browse/NIFI-12558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801900#comment-17801900 ] 

ASF subversion and git services commented on NIFI-12558:
--------------------------------------------------------

Commit 1a0a9b5bc09dada7ca79758ac268b21b3c06c342 in nifi's branch refs/heads/support/nifi-1.x from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1a0a9b5bc0 ]

NIFI-12558 Upgraded Jagged from 0.2.0 to 0.3.0

Signed-off-by: Matt Burgess <ma...@apache.org>


> Upgrade Jagged to 0.3.0
> -----------------------
>
>                 Key: NIFI-12558
>                 URL: https://issues.apache.org/jira/browse/NIFI-12558
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Minor
>              Labels: backport-needed
>             Fix For: 1.25.0, 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> The Jagged library should be upgraded to version [0.3.0|https://github.com/exceptionfactory/jagged/releases/tag/0.3.0] on both main and support branches to resolve an issue with concurrent access to KeyAgreement instances that presents itself when configuring the DecryptContentAge Processor with more than one Concurrent Task.



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