Interesting. Appears the embedded Kafka instance is somehow not
running there or not accessible. Yet it is spun up in the tests.
Even more interesting is that Travis-CI runs on Ubuntu (older version)
as shown in the travis-ci build information linked to our github
Distributor ID: Ubuntu
Build worked on a Centos 7 system but is failing the Kafka tests on 2
different Ubuntu 15.10 systems.
Failed tests:
TestPutKafka.testComplexLeftPartialDelimitedMessages:225 Expected
all Transferred FlowFiles to go to success but 1 were routed to failure
Still working on the validation, but I was able to get past the point in
0.6.0 on my Windows 10 rig that kept failing in unit tests.
On Wed, Apr 6, 2016 at 5:51 PM, Joe Witt wrote:
> Hello Apache NiFi community,
>
> Please find the associated guidance to help those
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/335#issuecomment-207181902
Hello - thanks for contributing. Some feedback:
- The commit message and the PR will need to associate to some open JIRA.
If the JIRA were say NIFI-XYZ1 then the
GitHub user owieboy opened a pull request:
https://github.com/apache/nifi/pull/335
Adjust batch.size property description and validation.
According here : http://kafka.apache.org/082/configuration.html, batch.size
should be in bytes with default value 16348.
You can merge this
Github user adamonduty commented on the pull request:
https://github.com/apache/nifi/pull/246#issuecomment-207135460
Awesome, thanks @alopresto!!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user mans2singh commented on the pull request:
https://github.com/apache/nifi/pull/224#issuecomment-207081123
@apiri - Hi Aldrin - Do you have any recommendations for this pull request
? Thanks
---
If your project is set up for it, you can reply to this email and have your
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/330
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/330#issuecomment-207070409
Awesome thanks. FYI - I'm removing one line of dead code from the
FileAuthorizerTest prior to merging to master.
---
If your project is set up for it, you can reply to
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/330#issuecomment-207066913
Latest commit looks good. Performed code review and then verified
contrib-check and unit tests. +1
---
If your project is set up for it, you can reply to this email and
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/330#discussion_r58933064
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-file-authorizer/src/test/java/org/apache/nifi/authorization/FileAuthorizerTest.java
---
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/330#discussion_r58930317
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-file-authorizer/src/main/java/org/apache/nifi/authorization/FileAuthorizer.java
---
@@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/330#discussion_r58929464
--- Diff:
Aldrin input: Fixed date.
Tony input:
- Yes I think the increasing committer ranks suggests a strong PMC
pipeline. I can add that as a clarifying point.
- For the language change i'm good with it. New draft below.
+
Report from the Apache NiFi committee [Joe Witt]
## Description:
-
Tony,
Certainly some good points here. I definitely can agree that there is some
concern
about the resource contention between heart-beating and state management.
In testing the PR 323 for heart-beating to ZooKeeper, we did notice that if we
lose
the quorum, the nodes are no longer able to
Joe - hopefully constructive comments:
To me, based on the lack of new PMC members since November could be
considered unsubstantiated - are you basing this on number of new
committers?
- Pipeline for PMC progression is very strong.
As an aside I will take as an action to put together a DISCUSS
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/246
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi James,
It looks like there may be a typo in what I wrote... I had $[path} but it
should be ${path}
Sorry about that, can you let us know if that worked.
Thanks,
Bryan
On Thu, Apr 7, 2016 at 3:05 AM, jamesgreen
wrote:
> Hi Bryan
>
> I tried what you
+1 (binding)
Ran through release helper and everything checked out.
Ran example flows and functioned as expected.
On Wed, Apr 6, 2016 at 11:16 PM, Aldrin Piri wrote:
> +1, binding
>
> Build and tests worked on OS X and Windows 7. Branch looked good on our
> Travis build
Hello,
Another workaround that can be implemented for properties that implement
expression language can be to store these properties in a database table.
Retrieve them using ExecuteSQL, Then ConvertAvroToJSON and use EvaluateJSONPath
to convert JSON to attributes.
This will only work for
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/333
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user Hejki opened a pull request:
https://github.com/apache/nifi/pull/334
NIFI-1738 - Repair logger names for ControllerStatusReportingTask
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Hejki/nifi nifi-1738
GitHub user trixpan reopened a pull request:
https://github.com/apache/nifi/pull/290
NIFI-856 Implements experimental ListenLumberjack Processor
ListenLumberjack processor should allow NiFi to act as a drop in
replacement on pipelines
using logstash-forwarder and Logstash's
Github user trixpan closed the pull request at:
https://github.com/apache/nifi/pull/290
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/333
nifi-1736 Move kafka.StreamScanner to nifi-utils.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ijokarumawak/nifi nifi-1736
Alternatively
25 matches
Mail list logo