Regarding OpenLDAP Public License
This does not appear to be listed under the approved apache licenses
to use for source or binary dependencies. However, it looks like it
is probably considered a variant of the BSD 3-Clause license which
would be ok as category a. It would be helpful to validate
Daniel,
I think one reason that MiNiFi Java has been successful, both as a prototype
and tool deployed in real environments today, is that it was able to leverage
much of the existing NiFi Java codebase. This greatly reduced the
"time-to-market” and allowed the development team to get working c
For me personally, I don't see a value add of MiNiFi Java. The needs that
NiFi can't address MiNiFi Java can't either, so my focus is MiNiFi C++ as
that is the hole that needs fixing, again in my opinion, so that is where my
MiNiFi focus is going to be.
As I go through things I am sure I will hav
Hi Daniel,
Thanks for mailing and getting involved with MiNiFi!
There is no inherent coupling of versions rather, as has been the custom
within the NiFi community, we use, roughly, semantic versioning. As a
result, our initial release of MiNiFi C++ started as 0.0.1 and since there
have been some
Having been out of touch since MiNiFi C++ got added and just getting into it,
is there a reason the C++ version is trying to follow closely the MiNiFi
Java version rather than just insuring connectivity with NiFi? I have not
been able to find alot of details regarding the roadmap for MiNiFi C++.
Hey folks,
There have been some nice improvements increasing stability and another
step toward framework parity with its Java counterparts. There was also
work done to update build tooling to provide a better foundation to tackle
specific environments and flexibility in generating differing buil
Awesome. Your prompt and detailed feedback is very much appreciated!
On Tue, Nov 22, 2016 at 12:47 PM, Joe Witt wrote:
> mike - also to clarify based on what you brought up I updated the JIRA
> description as follows
>
> The following also would be true:
> 1) Apache NiFi 1.0.0 repositories sho
mike - also to clarify based on what you brought up I updated the JIRA
description as follows
The following also would be true:
1) Apache NiFi 1.0.0 repositories should work just fine when applied
to an Apache NiFi 1.1.0 installation.
2) Repositories made/updated in Apache NiFi 1.1.0 onward would
Mike - yeah good catch and good question. It does support the old
format. We've always been pretty good about being diligent to allow
folks to upgrade and it honor existing state and in many cases
configurations and it would automatically port them over. What has
always been far more problematic
After seeing "Repositories now support rollback" in the release notes and
reading NIFI-2854 [1], I have a question.
Are repositories created using NiFi 1.0.0 compatible with NiFi 1.1.0
software? This is the goal that the ticket seems to indicate with 1.1.0
onward, but it's not clear whether 1.0.0
Thanks James. Will add the AWS stuff now. The generate flow file
I'll leave off since it is mostly a developer/debug tool unless you
disagree.
Thanks
Joe
On Tue, Nov 22, 2016 at 12:08 PM, James Wing wrote:
> Going through the tickets, it seems like quite a release. A few more
> things for you
Going through the tickets, it seems like quite a release. A few more
things for your list:
GenerateFlowFile updated to support literal/expression content and
attributes
AWS-related:
* New processors PutCloudWatchMetric, PutKinesisStream
* Updated processors PutS3Object (content type, signer opti
I've reviewed NIFI-3064 and it's good to go, would like to add that one as well.
Thanks,
Matt
On Tue, Nov 22, 2016 at 10:51 AM, Joe Witt wrote:
> thanks Joe and Andy. Have those on the list now.
>
> On Tue, Nov 22, 2016 at 5:09 AM, Joe Gresock wrote:
>> I'm biased, but I think the new Query /
thanks Joe and Andy. Have those on the list now.
On Tue, Nov 22, 2016 at 5:09 AM, Joe Gresock wrote:
> I'm biased, but I think the new Query / Scroll Elasticsearch processors are
> pretty big ;)
>
> On Tue, Nov 22, 2016 at 9:02 AM, Andy LoPresto wrote:
>
>> Important to call out in the security
Hi Joe,
we are running a modified code, basically we removed the ORC table support from
NIFI. Do you think this problem is due to our patches?
Actually we don't use anything which is related to ORC.
From: Joe Witt
Sent: Tuesday, November 22, 2016 2:25:47 PM
To: d
Thanks Andrew,
Will check with influxdb mail list.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/PostHttp-processor-read-timeout-error-socketTimeoutException-tp13879p13946.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
Thanks for your detailed reply Joseph Percivalllinkedin.
Yes Im using multiple http processors. As you suggested , I will try to
explore Getfile and extracttext processors.
Sorry for the late reply.
Thanks Again.
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.n
Hello Alessio
The concerning bit from the log is the ClassCastException.
Have you altered the lib folder in some way?
Thanks
Joe
On Tue, Nov 22, 2016 at 8:22 AM, Alessio Palma
wrote:
> Hello all,
> I'm working on 3 nodes cluster, sometimes nodes get disconnected and there
> is no way to connec
Hello all,
I'm working on 3 nodes cluster, sometimes nodes get disconnected and there is
no way to connect them again using the Cluster menu.
I checked the logs and this is what is reported, can you explain what is going
on ?
AP
2016-11-22 11:17:41,943 INFO [NIOServerCxn.Factory:0.0.0.0/0.0.0.
I'm biased, but I think the new Query / Scroll Elasticsearch processors are
pretty big ;)
On Tue, Nov 22, 2016 at 9:02 AM, Andy LoPresto wrote:
> Important to call out in the security section that
> login-identity-providers.xml is now covered by encrypted config, and
> flow.xml.gz processor prop
Important to call out in the security section that login-identity-providers.xml
is now covered by encrypted config, and flow.xml.gz processor property
encryption/nifi.sensitive.props.key value can now be migrated by the
command-line tool (second part pending completion of NIFI-3024).
Andy LoPre
21 matches
Mail list logo