You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Mike Thomsen <mi...@gmail.com> on 2022/06/10 20:06:03 UTC
Upgrading Cassandra driver and bringing in breaking changes with it
https://issues.apache.org/jira/browse/NIFI-9770
Based on David's description saying it will require some deep changes
to how various properties are configured, I think this ticket would be
a good time to simplify the Cassandra bundle in general to just use a
controller service to configure the connection. (Current approach is
controller service or manual configuration on a per-processor basis).
Thoughts?
Re: Upgrading Cassandra driver and bringing in breaking changes with it
Posted by Steven Matison <st...@gmail.com>.
Sure, as long as you can help guide me in the right direction. I'll send
you a slack msg...
On Tue, Jun 14, 2022 at 7:40 AM Mike Thomsen <mi...@gmail.com> wrote:
> Steve,
>
> Do you want to break up the ticket into a controller service ticket
> and an update ticket for the processors? You could do the former while
> I do the latter if you want to get your hands dirty making a
> contribution here.
>
> Thanks,
>
> Mike
>
> On Fri, Jun 10, 2022 at 4:32 PM Steven Matison <st...@gmail.com>
> wrote:
> >
> > I'd like to get in on this one if you guys need anything.
> >
> >
> >
> > On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
> > exceptionfactory@apache.org> wrote:
> >
> > > Mike,
> > >
> > > Thanks for digging into this issue! I agree that simplifying the
> > > implementation makes going forward. The newer driver version involves
> > > changes in the Controller Service method signatures either way, so
> > > streamlining the connection handling approach would be helpful.
> > >
> > > Based on feedback, perhaps summarizing the planned implementation in
> the
> > > Jira issue would be helpful.
> > >
> > > Regards,
> > > David Handermann
> > >
> > > On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen <mi...@gmail.com>
> > > wrote:
> > >
> > > > https://issues.apache.org/jira/browse/NIFI-9770
> > > >
> > > > Based on David's description saying it will require some deep changes
> > > > to how various properties are configured, I think this ticket would
> be
> > > > a good time to simplify the Cassandra bundle in general to just use a
> > > > controller service to configure the connection. (Current approach is
> > > > controller service or manual configuration on a per-processor basis).
> > > >
> > > > Thoughts?
> > > >
> > >
>
Re: Upgrading Cassandra driver and bringing in breaking changes with it
Posted by Mike Thomsen <mi...@gmail.com>.
Steve,
Do you want to break up the ticket into a controller service ticket
and an update ticket for the processors? You could do the former while
I do the latter if you want to get your hands dirty making a
contribution here.
Thanks,
Mike
On Fri, Jun 10, 2022 at 4:32 PM Steven Matison <st...@gmail.com> wrote:
>
> I'd like to get in on this one if you guys need anything.
>
>
>
> On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
> exceptionfactory@apache.org> wrote:
>
> > Mike,
> >
> > Thanks for digging into this issue! I agree that simplifying the
> > implementation makes going forward. The newer driver version involves
> > changes in the Controller Service method signatures either way, so
> > streamlining the connection handling approach would be helpful.
> >
> > Based on feedback, perhaps summarizing the planned implementation in the
> > Jira issue would be helpful.
> >
> > Regards,
> > David Handermann
> >
> > On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen <mi...@gmail.com>
> > wrote:
> >
> > > https://issues.apache.org/jira/browse/NIFI-9770
> > >
> > > Based on David's description saying it will require some deep changes
> > > to how various properties are configured, I think this ticket would be
> > > a good time to simplify the Cassandra bundle in general to just use a
> > > controller service to configure the connection. (Current approach is
> > > controller service or manual configuration on a per-processor basis).
> > >
> > > Thoughts?
> > >
> >
Re: Upgrading Cassandra driver and bringing in breaking changes with it
Posted by Steven Matison <st...@gmail.com>.
I'd like to get in on this one if you guys need anything.
On Fri, Jun 10, 2022 at 4:12 PM David Handermann <
exceptionfactory@apache.org> wrote:
> Mike,
>
> Thanks for digging into this issue! I agree that simplifying the
> implementation makes going forward. The newer driver version involves
> changes in the Controller Service method signatures either way, so
> streamlining the connection handling approach would be helpful.
>
> Based on feedback, perhaps summarizing the planned implementation in the
> Jira issue would be helpful.
>
> Regards,
> David Handermann
>
> On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen <mi...@gmail.com>
> wrote:
>
> > https://issues.apache.org/jira/browse/NIFI-9770
> >
> > Based on David's description saying it will require some deep changes
> > to how various properties are configured, I think this ticket would be
> > a good time to simplify the Cassandra bundle in general to just use a
> > controller service to configure the connection. (Current approach is
> > controller service or manual configuration on a per-processor basis).
> >
> > Thoughts?
> >
>
Re: Upgrading Cassandra driver and bringing in breaking changes with it
Posted by David Handermann <ex...@apache.org>.
Mike,
Thanks for digging into this issue! I agree that simplifying the
implementation makes going forward. The newer driver version involves
changes in the Controller Service method signatures either way, so
streamlining the connection handling approach would be helpful.
Based on feedback, perhaps summarizing the planned implementation in the
Jira issue would be helpful.
Regards,
David Handermann
On Fri, Jun 10, 2022 at 3:06 PM Mike Thomsen <mi...@gmail.com> wrote:
> https://issues.apache.org/jira/browse/NIFI-9770
>
> Based on David's description saying it will require some deep changes
> to how various properties are configured, I think this ticket would be
> a good time to simplify the Cassandra bundle in general to just use a
> controller service to configure the connection. (Current approach is
> controller service or manual configuration on a per-processor basis).
>
> Thoughts?
>