You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Anna Nys (Jira)" <ji...@apache.org> on 2023/09/28 13:31:00 UTC

[jira] [Assigned] (NIFI-11812) Stateless hardcodes "nexus" as the only extension option - Requesting NiFi Registry and/or S3 as additional ExtensionClient options

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

Anna Nys reassigned NIFI-11812:
-------------------------------

    Assignee: Anna Nys

> Stateless hardcodes "nexus" as the only extension option - Requesting NiFi Registry and/or S3 as additional ExtensionClient options
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-11812
>                 URL: https://issues.apache.org/jira/browse/NIFI-11812
>             Project: Apache NiFi
>          Issue Type: New Feature
>            Reporter: Stephanie Ambrose
>            Assignee: Anna Nys
>            Priority: Major
>
> Right now stateless NiFi has a hard-coded check on extension type of "nexus" on line 302 of StandardStatelessDataflowFactory. It would be nice to configure stateless to pull nars from additional extensions such as NiFi Registry and/or S3. "stateful" NiFi allows you to set the nar provider to NiFi Registry, which can be configured to store to S3. It'd be nice to have this feature for stateless as well versus being tied to only nexus.



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