Latest NiFi customs?

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Latest NiFi customs?

Russell Bateman-2
After a couple of years absence from NiFi (prior to Java 9), I find
myself just now back in a developer role in a company that uses NiFi.
(This is a pleasant thought, I might add, as I believe that NiFi rocks.)
I have inherited an existing implementation that's sorely aged and,
though I've googled mostly in vain on what I'm asking, would like to dot
the /i/s and cross the /t/s.

*What version of NiFi?*
How far forward (toward) NiFi 1.9 should I push my company? I see that
the Docker container is at 1.8 if that's any reference. I'm tempted
right now to move to 1.8 immediately.

*What about Java?*
What is the state of Java in NiFi? It appears that it's still back on
Java 8? I develop using IntelliJ IDEA. While I constrain the level of
language features to 1.8, it isn't realistic to contemplate developing
in IDEA without a pretty modern JDK version (I use Java 11 today because
LTS). I assume, nevertheless, that if I'm careful not to permit--by
setting in IDEA--the use of language constructs in my custom processors
to exceed 1.8, I should be okay, right? Or, am I missing something and
there are other considerations to watch out for?

Thanks for any and all comments, setting me straight, etc.
Reply | Threaded
Open this post in threaded view
|

Re: Latest NiFi customs?

Lars Francke
Hi,

I have just one data point on the version but I would suggest moving to 1.9
if you're just starting out and if you're using the Record based processors
with potentially dynamic/changing schemas.
The automatic schema inference described in this blog post[1] makes things
much easier (or possible). I see no reason to start with 1.8 today if you
have the option of upgrading.

Java: Java 8, while outdated, is still pretty much standard almost
everywhere I look.

Cheers,
Lars

[1] <
https://medium.com/@abdelkrim.hadjidj/democratizing-nifi-record-processors-with-automatic-schemas-inference-4f2b2794c427
>

On Wed, Apr 17, 2019 at 4:49 PM Russell Bateman <[hidden email]>
wrote:

> After a couple of years absence from NiFi (prior to Java 9), I find
> myself just now back in a developer role in a company that uses NiFi.
> (This is a pleasant thought, I might add, as I believe that NiFi rocks.)
> I have inherited an existing implementation that's sorely aged and,
> though I've googled mostly in vain on what I'm asking, would like to dot
> the /i/s and cross the /t/s.
>
> *What version of NiFi?*
> How far forward (toward) NiFi 1.9 should I push my company? I see that
> the Docker container is at 1.8 if that's any reference. I'm tempted
> right now to move to 1.8 immediately.
>
> *What about Java?*
> What is the state of Java in NiFi? It appears that it's still back on
> Java 8? I develop using IntelliJ IDEA. While I constrain the level of
> language features to 1.8, it isn't realistic to contemplate developing
> in IDEA without a pretty modern JDK version (I use Java 11 today because
> LTS). I assume, nevertheless, that if I'm careful not to permit--by
> setting in IDEA--the use of language constructs in my custom processors
> to exceed 1.8, I should be okay, right? Or, am I missing something and
> there are other considerations to watch out for?
>
> Thanks for any and all comments, setting me straight, etc.
>
Reply | Threaded
Open this post in threaded view
|

RE: [EXT] Re: Latest NiFi customs?

Peter Wicks (pwicks)
One other thing, that seems to catch me every time I upgrade an old instance: you will need to go in and allow users to read provenance data again. Somewhere along the way (1.6?) provenance reading moved into a separate policy, and it does not get assigned to anyone after upgrade.

-----Original Message-----
From: Lars Francke <[hidden email]>
Sent: Thursday, April 18, 2019 3:05 AM
To: [hidden email]
Subject: [EXT] Re: Latest NiFi customs?

Hi,

I have just one data point on the version but I would suggest moving to 1.9 if you're just starting out and if you're using the Record based processors with potentially dynamic/changing schemas.
The automatic schema inference described in this blog post[1] makes things much easier (or possible). I see no reason to start with 1.8 today if you have the option of upgrading.

Java: Java 8, while outdated, is still pretty much standard almost everywhere I look.

Cheers,
Lars

[1] <
https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40abdelkrim.hadjidj%2Fdemocratizing-nifi-record-processors-with-automatic-schemas-inference-4f2b2794c427&amp;data=02%7C01%7Cpwicks%40micron.com%7C756adfb0351748bcb14608d6c3dd1ae1%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C636911751740895088&amp;sdata=ek7jCdr8iy83RRJQ1cxhR%2BntfswCcLRImxviuDkWgBQ%3D&amp;reserved=0
>

On Wed, Apr 17, 2019 at 4:49 PM Russell Bateman <[hidden email]>
wrote:

> After a couple of years absence from NiFi (prior to Java 9), I find
> myself just now back in a developer role in a company that uses NiFi.
> (This is a pleasant thought, I might add, as I believe that NiFi
> rocks.) I have inherited an existing implementation that's sorely aged
> and, though I've googled mostly in vain on what I'm asking, would like
> to dot the /i/s and cross the /t/s.
>
> *What version of NiFi?*
> How far forward (toward) NiFi 1.9 should I push my company? I see that
> the Docker container is at 1.8 if that's any reference. I'm tempted
> right now to move to 1.8 immediately.
>
> *What about Java?*
> What is the state of Java in NiFi? It appears that it's still back on
> Java 8? I develop using IntelliJ IDEA. While I constrain the level of
> language features to 1.8, it isn't realistic to contemplate developing
> in IDEA without a pretty modern JDK version (I use Java 11 today
> because LTS). I assume, nevertheless, that if I'm careful not to
> permit--by setting in IDEA--the use of language constructs in my
> custom processors to exceed 1.8, I should be okay, right? Or, am I
> missing something and there are other considerations to watch out for?
>
> Thanks for any and all comments, setting me straight, etc.
>
Reply | Threaded
Open this post in threaded view
|

Re: [EXT] Latest NiFi customs?

Andy LoPresto-2
There is substantial work being lead by Jeff Storck to migrate NiFi to Java 11. You can see discussions about that on the mailing list [1] and in one of the PRs [2].

[1] https://lists.apache.org/thread.html/8af1752087480ac83bc01ea89d616316a125848b334624a3e2fce4d3@%3Cdev.nifi.apache.org%3E <https://lists.apache.org/thread.html/8af1752087480ac83bc01ea89d616316a125848b334624a3e2fce4d3@%3Cdev.nifi.apache.org%3E>
[2] https://github.com/apache/nifi/pull/3404 <https://github.com/apache/nifi/pull/3404>


Andy LoPresto
[hidden email]
[hidden email]
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Apr 18, 2019, at 6:40 AM, Peter Wicks (pwicks) <[hidden email]> wrote:
>
> One other thing, that seems to catch me every time I upgrade an old instance: you will need to go in and allow users to read provenance data again. Somewhere along the way (1.6?) provenance reading moved into a separate policy, and it does not get assigned to anyone after upgrade.
>
> -----Original Message-----
> From: Lars Francke <[hidden email]>
> Sent: Thursday, April 18, 2019 3:05 AM
> To: [hidden email]
> Subject: [EXT] Re: Latest NiFi customs?
>
> Hi,
>
> I have just one data point on the version but I would suggest moving to 1.9 if you're just starting out and if you're using the Record based processors with potentially dynamic/changing schemas.
> The automatic schema inference described in this blog post[1] makes things much easier (or possible). I see no reason to start with 1.8 today if you have the option of upgrading.
>
> Java: Java 8, while outdated, is still pretty much standard almost everywhere I look.
>
> Cheers,
> Lars
>
> [1] <
> https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmedium.com%2F%40abdelkrim.hadjidj%2Fdemocratizing-nifi-record-processors-with-automatic-schemas-inference-4f2b2794c427&amp;data=02%7C01%7Cpwicks%40micron.com%7C756adfb0351748bcb14608d6c3dd1ae1%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0%7C636911751740895088&amp;sdata=ek7jCdr8iy83RRJQ1cxhR%2BntfswCcLRImxviuDkWgBQ%3D&amp;reserved=0
>>
>
> On Wed, Apr 17, 2019 at 4:49 PM Russell Bateman <[hidden email]>
> wrote:
>
>> After a couple of years absence from NiFi (prior to Java 9), I find
>> myself just now back in a developer role in a company that uses NiFi.
>> (This is a pleasant thought, I might add, as I believe that NiFi
>> rocks.) I have inherited an existing implementation that's sorely aged
>> and, though I've googled mostly in vain on what I'm asking, would like
>> to dot the /i/s and cross the /t/s.
>>
>> *What version of NiFi?*
>> How far forward (toward) NiFi 1.9 should I push my company? I see that
>> the Docker container is at 1.8 if that's any reference. I'm tempted
>> right now to move to 1.8 immediately.
>>
>> *What about Java?*
>> What is the state of Java in NiFi? It appears that it's still back on
>> Java 8? I develop using IntelliJ IDEA. While I constrain the level of
>> language features to 1.8, it isn't realistic to contemplate developing
>> in IDEA without a pretty modern JDK version (I use Java 11 today
>> because LTS). I assume, nevertheless, that if I'm careful not to
>> permit--by setting in IDEA--the use of language constructs in my
>> custom processors to exceed 1.8, I should be okay, right? Or, am I
>> missing something and there are other considerations to watch out for?
>>
>> Thanks for any and all comments, setting me straight, etc.
>>