Bryan, Is there a new GUI part of the registry for the extension registry work in master? I compiled 0.4.0-SNAPSHOT and didn't see anything immediately. You mentioned docs and sys admin stuff... Could you point me in the quick-start path if I wanted to try to kick-the-tires a little on this?
Thanks, Ryan On Tue, Mar 26, 2019 at 9:57 AM Bryan Bende <[email protected]> wrote: > Mike, > > All record-oriented components are extensions and thus can make use of > versioned components (i.e. nothing related to records is baked into > the core framework of NiFi). > > The record API is essentially the module named > nifi-record-serialization-services-api which at runtime is included in > nifi-standard-services-api-nar. Any record oriented processors you > build are dependent on a specific version of > nifi-standard-services-api-nar since that is where the Java interface > will be that your processor was compiled against. > > Right now, even without extension registry, you could deploy multiple > versions of nifi-standard-services-api-nar to a NiFi instance, and > then deploy multiple versions of your record processing NAR that > correspond to the versions of your API NAR. > > Going forward with extension registry, we probably want to consider > breaking up nifi-standard-services-api-nar into smaller API NARs, as > well as nifi-standard-bundle into smaller processor bundles. For > example, there could be a record API NAR and a record processors NAR, > that would both be split out of from the standard NARs. > > -Bryan > > > On Tue, Mar 26, 2019 at 7:55 AM Mike Thomsen <[email protected]> > wrote: > > > > Great news about the extension registry! As we get closer to that being > > ready, I'd like to add in some discussion about versioning the record API > > separately. A lot of the custom processors we build now are Record > > API-based, and it would be great to be able to decouple them from one > > specific release of NiFi. > > > > On Mon, Mar 25, 2019 at 2:14 PM Bryan Bende <[email protected]> wrote: > > > > > Hi Pierre, > > > > > > I think we are definitely close to an 0.4.0 release. A major chunk of > > > extension registry work has already landed in master, and I still have > one > > > other jira that I almost have ready and wanted to include, NIFIREG-233 > for > > > generating extensions docs. Plus we probably need to make a few > > > additions/updates to the admin guide. > > > > > > -Bryan > > > > > > On Mon, Mar 25, 2019 at 1:33 PM Pierre Villard < > > > [email protected]> > > > wrote: > > > > > > > All, > > > > > > > > Some really nice features have been included since the NiFi Registry > > > 0.3.0 > > > > release and I'm wondering if it'd be a good time to consider a 0.4.0 > > > > release. > > > > > > > > There is a JIRA tagged for 0.4.0 and there are 2 opened pull > requests, > > > plus > > > > interesting discussions / JIRAS on the mailing lists. > > > > > > > > Are there any reasons to hold off on a 0.4.0 release? Are there > > > particular > > > > JIRAs that the community considers necessary to have as part of the > > > > release? > > > > > > > > If not, happy to give it a try at performing RM duties! > > > > > > > > Thanks, > > > > Pierre > > > > > > > -- > > > Sent from Gmail Mobile > > > >
