Thanks for running this all down Joe/Aldrin/Oleg. I think Joe's
suggestion of having a test which checks for this sort of environment
condition and fails with a nice explanation would be really nice.
It looks like Oleg fixed the copyright concerns by removing the lines
which appear to have been u
+1
On Sat, Apr 9, 2016 at 12:13 AM, Joe Witt wrote:
> Team,
>
> Following a solid discussion [1] in early January regarding
> establishment of MiNiFi as a subproject of NiFi I'd like to call a
> formal vote to record this important community decision and
> established consensus.
>
> Through lazy
PROBLEM SOLVED. The problem was a mixture of DNS and routing.
For a couple of reasons, including possibly bad router config, each had a
mixture of a bad nameserver configuration or bad routing to the
nameserver. So, they couldn't resolve their own hostnames to an IP
address. That's not unique t
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/341
NIFI-1748 removed un-used test data
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1748
Alternatively you can review and apply the
The OSX system passed the tests switching to a different network. Putting
it back on the problem network and checking KafkaPublisherTest-output.txt I
see repeated occurrences of the following. (fat fingered, ignore any
obvious typos)
17:01:59,225 WARN kafka-producer-network-thread | produce
Well that's great to hear, Joe. Thanks for gathering a bit more info.
We should have tests that are a bit more resilient to varying network
conditions. I know we got nabbed by a few when the project first started
incubation To that end, if you know of anything specific between the two
routers s
Perfect
I was just replying too you again ;). Indeed ‘test’ was not used and I already
commented to that effect in JIRA and removed.
Yes, I was wondering why they fail as this is the first time someone reported
KafkaPublisherTest failures, so kind of curious, so please feed all the info
you can
Oleg,
I'm not familiar enough with Kafka to know what the tests need, but looking
at the test source now I don't think the "String test" on line 70 is used
anywhere, so I think you can just remove it.
The failures where pretty much the same on all 3 systems. But based on
Aldrin's question about
Aldrin,
Wow, great catch on it being a network issue, the OSX system has
successfully finished a "mvn -Pcontrib-check clean install" run!
I haven't had any other problems on this router, but something must be up.
Now the "fun" starts now to figure out what's wrong? ;-)
I'll let you know if it's
Joe
Thanks for pointing that out. I’ll remove the quote from CNN article, just used
it as sample text. Do you see any other issue with sample data?
Also, which systems did you observe failures described below?
Cheers
Oleg
> On Apr 9, 2016, at 2:47 PM, Joe Skora wrote:
>
> -1 (non-binding)
>
Github user jvwing commented on the pull request:
https://github.com/apache/nifi/pull/334#issuecomment-207841740
@Hejki, this looks like a solid fix to me. One thing I suggest you add is
some unit tests, which I missed when I "fixed" this a couple months ago. If
that sounds like ove
Aldrin,
Yes same network, nothing novel that I know of, they all have internet
access and I've disabled firewalls for comparison with no affect. This is
a new router, so I will move one to the old router and see if that makes a
difference.
The validate/valudate mismatch is a fat fingering error
The vote for nifi 0.6.1 is cancelled.
While test issues are one thing copyright issues are another. I looked at
the test Joe highlighted and believe we must remove both the quote and the
apparent news article. Will address and send another rc asap. If someone
could tackle the test failing tests
Joe,
Are these all running on the same network? If so, anything novel or
different about it?
Also, a I assume these are remnants of debugging, but noticed some
differences in terms of the source at the tagged RC and your stacktraces.
TestGetHTTP, for instance, only has 431 lines and the test lis
GitHub user jdye64 opened a pull request:
https://github.com/apache/nifi/pull/340
NIFI-1747 add maven-war-plugin to create jar as part of the existing â¦
â¦nifi-web-api build process
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
-1 (non-binding)
Builds and checkouts out ok, but 3 of 4 systems I tried fail in
KafkaPublisherTest unit tests with Java 7 and Java 8. Details and sample
results are included below.
The tests appear to handle ConsumerTimeoutException when it is expected,
but the very first call to ConsumerIterat
+1
> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
>
> Team,
>
> Following a solid discussion [1] in early January regarding
> establishment of MiNiFi as a subproject of NiFi I'd like to call a
> formal vote to record this important community decision and
> established consensus.
>
> Through la
+1
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com
On Saturday, April 9, 2016 10:40 AM, Suneel Marthi wrote:
+1
On Sat, Apr 9, 2016 at 9:36 AM, Toivo Adams wrote:
> +1
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7
+1
On Sat, Apr 9, 2016 at 9:36 AM, Toivo Adams wrote:
> +1
>
>
>
> --
> View this message in context:
> http://apache-nifi-developer-list.39713.n7.nabble.com/VOTE-Establish-Apache-MiNiFi-a-subproject-of-Apache-NIFi-tp8930p8947.html
> Sent from the Apache NiFi Developer List mailing list archive
+1
--
View this message in context:
http://apache-nifi-developer-list.39713.n7.nabble.com/VOTE-Establish-Apache-MiNiFi-a-subproject-of-Apache-NIFi-tp8930p8947.html
Sent from the Apache NiFi Developer List mailing list archive at Nabble.com.
+1
On Sat, Apr 9, 2016 at 8:17 AM Mark Payne wrote:
> +1
>
> Sent from my iPhone
>
> > On Apr 9, 2016, at 7:51 AM, Matt Gilman wrote:
> >
> > +1
> >
> > Sent from my iPhone
> >
> >> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
> >>
> >> Team,
> >>
> >> Following a solid discussion [1] in early J
+1
Sent from my iPhone
> On Apr 9, 2016, at 7:51 AM, Matt Gilman wrote:
>
> +1
>
> Sent from my iPhone
>
>> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
>>
>> Team,
>>
>> Following a solid discussion [1] in early January regarding
>> establishment of MiNiFi as a subproject of NiFi I'd like
+1
Sent from my iPhone
> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
>
> Team,
>
> Following a solid discussion [1] in early January regarding
> establishment of MiNiFi as a subproject of NiFi I'd like to call a
> formal vote to record this important community decision and
> established consen
+1
On Sat, Apr 9, 2016 at 7:08 AM, Matt Burgess wrote:
> +1
>
> > On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
> >
> > Team,
> >
> > Following a solid discussion [1] in early January regarding
> > establishment of MiNiFi as a subproject of NiFi I'd like to call a
> > formal vote to record this i
+1
> On Apr 9, 2016, at 1:13 AM, Joe Witt wrote:
>
> Team,
>
> Following a solid discussion [1] in early January regarding
> establishment of MiNiFi as a subproject of NiFi I'd like to call a
> formal vote to record this important community decision and
> established consensus.
>
> Through laz
+1
Rob
On Sat, Apr 9, 2016 at 3:48 AM, Jennifer Barnabee <
jennifer.barna...@gmail.com> wrote:
> +1
>
> On Sat, Apr 9, 2016 at 1:13 AM, Joe Witt wrote:
>
> > Team,
> >
> > Following a solid discussion [1] in early January regarding
> > establishment of MiNiFi as a subproject of NiFi I'd like to
+1
On Sat, Apr 9, 2016 at 1:13 AM, Joe Witt wrote:
> Team,
>
> Following a solid discussion [1] in early January regarding
> establishment of MiNiFi as a subproject of NiFi I'd like to call a
> formal vote to record this important community decision and
> established consensus.
>
> Through lazy
Great addition in the documentation. Very clear and useful.
Thanks,
Pierre
Le 8 avr. 2016 8:12 PM, "Joe Percivall" a
écrit :
Hello Dev,
I recently finished up an initial version of a new developer doc "Apache
NiFi In Depth". It goes in depth on the design decisions, the Repos, how a
FlowFile ge
28 matches
Mail list logo
