Thanks for the links, good read.

I implemented the C++ version of MiNiFi and got it all working, but found
out that the ExecuteStreamCommand processor doesn't exist.  Do I have to
write my own version into the C++ MiNiFi or is there another way to run OS
commands?  MiNiFi is running on a Windows machine btw.

Jeremy

On Wed, Jul 22, 2020 at 8:45 PM Pierre Villard <[email protected]>
wrote:

> I don't recall the specific details but when I used MQTT processors [1]
> with latest version of MiNiFi Java, I *think* I could not use the latest
> version of NiFi NARs, I had to use code from a previous NiFi version and
> cherry-pick some code (open pull request) I needed for my use case [2].
> Having said that, I'm not 100% sure - I might be mixing things up with an
> even older version of MiNiFi. If there is an issue, it should not be too
> hard to solve though, and happy to give pointers here.
>
> [1]
> https://medium.com/google-cloud/running-visual-quality-inspection-at-the-edge-with-google-cloud-and-apache-nifi-minifi-45282ce7af2d
> [2] https://github.com/apache/nifi/pull/3392
>
> Le mar. 21 juil. 2020 à 19:35, Joe Witt <[email protected]> a écrit :
>
>> ...right nars should generally port well.
>>
>> On Tue, Jul 21, 2020 at 10:25 AM Jeremy Pemberton-Pigott <
>> [email protected]> wrote:
>>
>>> Thanks Joe, that's really helpful, I have an immediate use for the Java
>>> version.  If I wanted to use the ConsumeMQTT processor from say 1.11.4, so
>>> that I can get the UUID Client ID feature, is that easy to do by just
>>> moving the jar over or something else has to be done or I'm limited to a
>>> specific NiFi version?
>>>
>>> Jeremy
>>>
>>> On Wed, Jul 22, 2020 at 12:52 AM Joe Witt <[email protected]> wrote:
>>>
>>>> Jeremy
>>>>
>>>> MiNiFi Java is basically a headless version of NiFi with some added
>>>> configuration ease of use items appropriate to that model.  It has proven
>>>> too hard to slice time for that versus NiFi so I think what will end up
>>>> happening is that minifi java as a standalone source repository will just
>>>> fade out and instead we'll make 'MiNiFi Java' an assembly/convenience
>>>> binary that builds from the same source repository as NiFi itself.  Matt
>>>> Burgess is doing a lot of work here in this regard.
>>>>
>>>> So in short - yeah this is still very actively developed.  Just that
>>>> 'where it is done' is shifting back into the mothership of NiFi itself so
>>>> to speak.
>>>>
>>>> MiNiFi CPP is another one to look at depending on your needs/scenario.
>>>> Also under very active development.
>>>>
>>>> Thanks
>>>>
>>>> On Tue, Jul 21, 2020 at 9:39 AM Jeremy Pemberton-Pigott <
>>>> [email protected]> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> Can someone help out with the version of NiFi that MiNiFi tracks?  The
>>>>> Java version seems to be at 0.5 for a long time while the C++ version is
>>>>> 0.7.  I'm also wondering if MiNiFi is actively developed or is it risky to
>>>>> include it in new projects?
>>>>>
>>>>> Jeremy
>>>>>
>>>>

Reply via email to