[
https://issues.apache.org/jira/browse/NIFI-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14723461#comment-14723461
]
Sean Busbey commented on NIFI-780:
----------------------------------
I haven't looked at what's included in 0.3.0, but generally yes. At least for
things that are regressions I'd rather have a lower risk upgrade path. This
issue itself is a great example of the risk in updating to a newer minor
version. If I was a user of the Solr NAR on version 0.1.0, ostensibly I had the
same assurances while upgrading to 0.2.0. How do I know that when upgrading to
0.3.0 I won't lose some other processor set I rely on?
Trust in version numbers is earned over time. If "you can't use class of
processors X" isn't a blocker, I'm guessing production users of NiFi are
quickly going to end up in a situation where they pull nars from particular
releases and hack together their own deployments rather than upgrading
everything. It's great that our architecture will make that not-super-painful
in most situations, but it's less than ideal.
> Solr NAR has incompatible version of httpclient
> -----------------------------------------------
>
> Key: NIFI-780
> URL: https://issues.apache.org/jira/browse/NIFI-780
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 0.2.0
> Reporter: Bryan Bende
> Assignee: Bryan Bende
> Fix For: 0.3.0
>
> Attachments: NIFI-780.patch
>
>
> Due to bumping the version of several dependencies in the top level
> dependency management section, the Solr NAR is now bringing in httpclient
> 4.4.1, but still using 4.3.x version of other http libraries. There are some
> incompatibilities resulting in NoClassDefFound errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
