You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Russell Bateman <ru...@windofkeltia.com> on 2017/04/03 20:05:20 UTC
org.apache.nifi.processor.util.FlowFileSessionWrapper deprecated
We're moving our code base ahead from NiFi 1.0.0 to 1.1.2 and have some
classes that are using FlowFileSessionWrapper. Appears to wrap up a
flowfile and its corresponding session; our use was in some special
batching code. I could roll my own, I guess, but there may be a very
good reason not to, i.e.: a better way to handle what it did for us,
stay out of trouble, etc.
So far, Googling encourages me to believe that this has been deprecated
and I shouldn't use it, but so far I haven't stumbled upon why or what
to do differently. Can anyone throw some light on this?
Thanks.
Re: org.apache.nifi.processor.util.FlowFileSessionWrapper deprecated
Posted by Joe Witt <jo...@gmail.com>.
Russell,
Sorry there was no reply but to help ensure it doesn't look like this
tree feel in an empty forest thanks for following up. You're right
that this refactoring occurred. There was some powerful session
merging capability made available that allowed us to simplify how
processors like MergeContent worked under the covers.
Thanks
Joe
On Thu, Apr 6, 2017 at 4:53 PM, Russell Bateman <ru...@windofkeltia.com> wrote:
> In answer to my own question, ... we discovered that the Binclass has been
> refactored to obviate the FlowFileSessionWrapper. Some light refactoring of
> our consuming code was required, that's all.
>
> Thanks.
>
>
> On 04/03/2017 02:22 PM, Russell Bateman wrote:
>>
>> I've tried building using NiFi JARs from 1.1.1 and 1.1.0, but only 1.0.0
>> works. It appears, unless I'm mistaken, that /MergeConte//n//t/ requires it
>> and the code appears to be in 1.1.2. (Maybe it's just Monday.) Here's the
>> error I'm getting back from Maven:
>>
>> [ERROR] Failed to execute goal
>> org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
>> (default-compile) on project standard-processors: Compilation failure:
>> Compilation failure:
>> [ERROR]
>> /home/russ/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/standard-processors/src/main/java/com/imatsolutions/nifi/processor/SearchServerBatch.java:[34,38]
>> cannot find symbol
>> [ERROR] symbol: class FlowFileSessionWrapper
>> [ERROR] location: package org.apache.nifi.processor.util
>>
>> Thanks.
>>
>> On 04/03/2017 02:05 PM, Russell Bateman wrote:
>>>
>>> We're moving our code base ahead from NiFi 1.0.0 to 1.1.2 and have some
>>> classes that are using FlowFileSessionWrapper. Appears to wrap up a flowfile
>>> and its corresponding session; our use was in some special batching code. I
>>> could roll my own, I guess, but there may be a very good reason not to,
>>> i.e.: a better way to handle what it did for us, stay out of trouble, etc.
>>>
>>> So far, Googling encourages me to believe that this has been deprecated
>>> and I shouldn't use it, but so far I haven't stumbled upon why or what to do
>>> differently. Can anyone throw some light on this?
>>>
>>> Thanks.
>>
>>
>
Re: org.apache.nifi.processor.util.FlowFileSessionWrapper deprecated
Posted by Russell Bateman <ru...@windofkeltia.com>.
In answer to my own question, ... we discovered that the Binclass has
been refactored to obviate the FlowFileSessionWrapper. Some light
refactoring of our consuming code was required, that's all.
Thanks.
On 04/03/2017 02:22 PM, Russell Bateman wrote:
> I've tried building using NiFi JARs from 1.1.1 and 1.1.0, but only
> 1.0.0 works. It appears, unless I'm mistaken, that /MergeConte//n//t/
> requires it and the code appears to be in 1.1.2. (Maybe it's just
> Monday.) Here's the error I'm getting back from Maven:
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
> (default-compile) on project standard-processors: Compilation failure:
> Compilation failure:
> [ERROR]
> /home/russ/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/standard-processors/src/main/java/com/imatsolutions/nifi/processor/SearchServerBatch.java:[34,38]
> cannot find symbol
> [ERROR] symbol: class FlowFileSessionWrapper
> [ERROR] location: package org.apache.nifi.processor.util
>
> Thanks.
>
> On 04/03/2017 02:05 PM, Russell Bateman wrote:
>> We're moving our code base ahead from NiFi 1.0.0 to 1.1.2 and have
>> some classes that are using FlowFileSessionWrapper. Appears to wrap
>> up a flowfile and its corresponding session; our use was in some
>> special batching code. I could roll my own, I guess, but there may be
>> a very good reason not to, i.e.: a better way to handle what it did
>> for us, stay out of trouble, etc.
>>
>> So far, Googling encourages me to believe that this has been
>> deprecated and I shouldn't use it, but so far I haven't stumbled upon
>> why or what to do differently. Can anyone throw some light on this?
>>
>> Thanks.
>
Re: org.apache.nifi.processor.util.FlowFileSessionWrapper deprecated
Posted by Russell Bateman <ru...@windofkeltia.com>.
I've tried building using NiFi JARs from 1.1.1 and 1.1.0, but only 1.0.0
works. It appears, unless I'm mistaken, that /MergeConte//n//t/ requires
it and the code appears to be in 1.1.2. (Maybe it's just Monday.) Here's
the error I'm getting back from Maven:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile
(default-compile) on project standard-processors: Compilation failure:
Compilation failure:
[ERROR]
/home/russ/sandboxes/nifi-pipeline.v73_release.dev/code/nifi-pipeline/standard-processors/src/main/java/com/imatsolutions/nifi/processor/SearchServerBatch.java:[34,38]
cannot find symbol
[ERROR] symbol: class FlowFileSessionWrapper
[ERROR] location: package org.apache.nifi.processor.util
Thanks.
On 04/03/2017 02:05 PM, Russell Bateman wrote:
> We're moving our code base ahead from NiFi 1.0.0 to 1.1.2 and have
> some classes that are using FlowFileSessionWrapper. Appears to wrap up
> a flowfile and its corresponding session; our use was in some special
> batching code. I could roll my own, I guess, but there may be a very
> good reason not to, i.e.: a better way to handle what it did for us,
> stay out of trouble, etc.
>
> So far, Googling encourages me to believe that this has been
> deprecated and I shouldn't use it, but so far I haven't stumbled upon
> why or what to do differently. Can anyone throw some light on this?
>
> Thanks.