Andy,
You're right. I was a caching issue with Chrome. I don't know why I
didn't think to try that--forest for the trees, I guess. Thank you.
Russ
On 7/17/20 5:58 PM, Andy LoPresto wrote:
Russell,
Have you verified this is not a browser caching issue? They are pernicious and
it sounds like this could be an example. If you’re sure it’s not, verify the
API calls using your browser’s Developer Tools to see what properties are
actually being returned by the server when inspecting a component to see if the
correct values are present. If so, it’s likely a UI bug, and if not, the new
code is not being properly loaded/used by NiFi’s server application.
Andy LoPresto
alopre...@apache.org
alopresto.apa...@gmail.com
He/Him
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
On Jul 17, 2020, at 3:48 PM, Russell Bateman <r...@windofkeltia.com> wrote:
If I have changed a custom processor's PropertyDescriptor.nameand/or
.displayName,including changes I have made to my /additionalDetails.html, /and
I have:
- removed that processor from my test flow or removed /flow.xml.gz/ altogether
- removed my NAR from /${NIFI_ROOT}///custom-lib/ and bounced NiFi with the new
custom NAR copied
yet nothing changes (in usage or in additional details), what am I overlooking?
Let's set aside the vaguely confusing semantic distinction between nameand
displayName, I just want NiFi to forget my new custom processor completely and
then accept my new version as if brand new including all the changes I have
made.
Thanks for any suggestions.
