Mike,

Yes that's correct, here's the Jira issue for tracking the migration work:

https://issues.apache.org/jira/browse/NIFI-12219

Regards,
David Handermann

On Thu, Oct 12, 2023, 5:29 PM Mike Thomsen <mikerthom...@gmail.com> wrote:

> This Xodus?
>
> https://github.com/JetBrains/xodus
>
> On Thu, Oct 12, 2023 at 1:30 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Mike,
> >
> > Thanks for raising this question. I am working on an automated
> > migration for the support branch from H2 to Xodus. We previously
> > handled automated migration from H2 1.4 to 2.1, and 2.1 to 2.2, so the
> > basic mechanics are in place to extract content from H2. The general
> > upgrade path will be to migrate to the latest version 1 release, and
> > then upgrade to version 2.
> >
> > Regards,
> > David Handermann
> >
> > On Thu, Oct 12, 2023 at 12:24 PM Mike Thomsen <mikerthom...@gmail.com>
> > wrote:
> > >
> > > When H2 goes, what will the upgrade path look like?
> > >
> > > On Tue, Oct 10, 2023 at 7:57 PM David Handermann <
> > > exceptionfact...@apache.org> wrote:
> > >
> > > > Joe,
> > > >
> > > > Thanks for the reply, that sounds good.
> > > >
> > > > For reference, here is the Jira issue for tracking the initial
> > > > implementation:
> > > >
> > > > https://issues.apache.org/jira/browse/NIFI-12206
> > > >
> > > > Regards,
> > > > David Handermann
> > > >
> > > > On Tue, Oct 10, 2023 at 6:53 PM Joe Witt <joe.w...@gmail.com> wrote:
> > > > >
> > > > > David
> > > > >
> > > > > I think we can hold off for a few weeks - I'll respond to the Slack
> > > > message
> > > > > on that.
> > > > >
> > > > > Will be sad to see H2 go.  The original nifi flowfile repository
> ran
> > on
> > > > > H2.  Surprisingly fast and stable actually.  But happy to hear
> there
> > is
> > > > > such progress underway.
> > > > >
> > > > > Thanks
> > > > >
> > > > > On Tue, Oct 10, 2023 at 4:27 PM David Handermann <
> > > > > exceptionfact...@apache.org> wrote:
> > > > >
> > > > > > Joe,
> > > > > >
> > > > > > Thanks for initiating the discussion on a 1.24 release. There
> are a
> > > > > > handful of new features, plus additional deprecations and
> > dependency
> > > > > > upgrades that would be very useful to release sooner rather than
> > > > > > later.
> > > > > >
> > > > > > If we are considering a 1.24 release within the next week, then I
> > > > > > would expect needing a 1.25 release to incorporate some
> additional
> > > > > > deprecations around the same time we are ready for a 2.0
> milestone
> > > > > > release version.
> > > > > >
> > > > > > I am in the process of implementing a replacement for H2 to store
> > flow
> > > > > > configuration history, and I plan to have a pull request ready in
> > the
> > > > > > next few days. There will be some additional work to support
> > migration
> > > > > > on version 1 support branch.
> > > > > >
> > > > > > If we want to move forward with a 1.24 release within a week or
> so,
> > > > > > then these changes could be targeted for 1.25. If we want to
> wait a
> > > > > > few weeks, then I could see this being incorporated in 1.24.
> > > > > >
> > > > > > Regards,
> > > > > > David Handermann
> > > > > >
> > > > > > On Tue, Oct 10, 2023 at 6:14 PM Mark Payne <marka...@hotmail.com
> >
> > > > wrote:
> > > > > > >
> > > > > > > Thanks Joe. I wouldn’t argue against doing a 1.24 release.
> > > > > > >
> > > > > > > Thanks
> > > > > > > -Mark
> > > > > > >
> > > > > > > > On Oct 10, 2023, at 7:01 PM, Joe Witt <joe.w...@gmail.com>
> > wrote:
> > > > > > > >
> > > > > > > > Team,
> > > > > > > >
> > > > > > > > We have plenty of bits out there to kick a release.  I'm
> happy
> > to
> > > > RM
> > > > > > this
> > > > > > > > if nobody else wants to.
> > > > > > > >
> > > > > > > > Had a user on Slack ask for it.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > > Joe
> > > > > > >
> > > > > >
> > > >
> >
>

Reply via email to