Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/326#issuecomment-205645456
Tested on a variety of platforms:
- OS X 10.11 - JDK 8u77 - Maven 3.3.9
- Windows 7 - JDK 7u79 - Maven 3.3.9
- Windows 10 (VM) - JDK 8u51 - Maven 3.3.3
-
As was I, but I can't test tonight
On Apr 4, 2016 9:54 PM, "alopresto" wrote:
> Github user alopresto commented on the pull request:
>
> https://github.com/apache/nifi/pull/326#issuecomment-205592813
>
> I was one of the people having issues with `TestListFile` on
Github user alopresto commented on the pull request:
https://github.com/apache/nifi/pull/326#issuecomment-205592813
I was one of the people having issues with `TestListFile` on the 0.6.0
build, but I rebooted my machine during an OS patch between then and now. As of
right now, I can
GitHub user apiri opened a pull request:
https://github.com/apache/nifi/pull/326
NIFI-1689 ListFile test inconsistent on various environments
NIFI-1689 Correcting TimeUnit conversion to be milliseconds instead of the
incorrect microseconds and using historical modified times to
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/325#issuecomment-205566498
Okay, I have a clean build across Windows for the issues at hand with Kafka
tests and things work on a Windows 7 environment across a full build.
---
If your project is
Hi,
Thanks for the replies. Your recommendation is to use 0.4.1 Kafka nar, correct?
Do we need to upgrade NiFi from 0.4.0 to 0.4.1? Or just a nar upgrade should be
sufficient?
Does this also mean that 0.4.0 isn't a stable version to use as Kafka producer
on high data rate?
Thanks,
Oscar
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/325#issuecomment-205557307
Hold off on anything at this time. Running through the tests I have found
additional issues in the Windows environment. I suspect these are largely the
same things and
On Mon, Apr 4, 2016 at 4:40 PM, Adam Lamar wrote:
> On Mon, Apr 4, 2016 at 11:14 AM, Sean Busbey wrote:
>> You're correct, a github PR only targets a single branch and Travis-CI
>> only checks how the PR does at its own commit hash (that is, it
>> doesn't
On Mon, Apr 4, 2016 at 1:39 PM, Tony Kurc wrote:
> Sean, how about yetus? Is this something yetus can do with the patch
> testing in an automated way?
Right now Yetus only checks a single target branch.
For commits that can apply/merge cleanly we could add something to
check
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/325#issuecomment-205522127
@apiri probably best to just be explicit on all the tests about the charset.
---
If your project is set up for it, you can reply to this email and have your
reply appear
On Mon, Apr 4, 2016 at 11:14 AM, Sean Busbey wrote:
> You're correct, a github PR only targets a single branch and Travis-CI
> only checks how the PR does at its own commit hash (that is, it
> doesn't even check what the target branch would look like post-merge).
>
Hey Sean,
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/232#issuecomment-205493328
@olegz Following comments on JIRA, I reverted modifications on SSL Context
service and added a Client Auth property (as it has been done in Cassandra
processors). I
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/324
NIFI-1668 modified TestProcessorLifecycle to ensure FlowController isâ¦
⦠always shut down
You can merge this pull request into a Git repository by running:
$ git pull
Ok proceeding with the release steps in just a bit.
Will take a quick look at NIFI-1689 as this appears to cause some
release verification hurdles for people on certain platforms.
https://github.com/apache/nifi/tree/support/nifi-0.6.x
Thanks
Joe
On Thu, Mar 31, 2016 at 12:15 PM, Jennifer
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/323#issuecomment-205461796
This is a resubmission of #317 which was closed when we removed a temporary
1.x branch which it was referencing. Please see that PR for additional
commentary.
---
If
Sean, how about yetus? Is this something yetus can do with the patch
testing in an automated way?
On Apr 4, 2016 1:14 PM, "Sean Busbey" wrote:
> You're correct, a github PR only targets a single branch and Travis-CI
> only checks how the PR does at its own commit hash (that
You're correct, a github PR only targets a single branch and Travis-CI
only checks how the PR does at its own commit hash (that is, it
doesn't even check what the target branch would look like post-merge).
On Mon, Apr 4, 2016 at 12:05 PM, Matt Gilman wrote:
> To my
To my knowledge, when you open a PR in GitHub it only allows the
contributor to select a single branch. The reviewer would need to check the
compatibility if that contribution needs to be applied to both. Depending
on the contribution, a separate PR may be required as the codebases
diverge. In
Is travis ci / githib able to give immediate feedback if a PR doesn't merge
into both?
On Mon, Apr 4, 2016 at 12:33 PM, Matt Gilman
wrote:
> All,
>
> I have completed the branching discussed last week.
>
> - master contains the current 1.x baseline - Future 1.x releases
Mark,
Fair points!
Something an Apache Accumulo committer pointed out at meetup is the is that
the scale issues may come sooner than a couple hundred nodes due to the
size of writes and potential frequency of writes (Joe Percivall's
demonstration on the windowing seemed like it could write much
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/301
---
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
Essentially all of the information contained in a FlowFile's contents would
be translated to attributes. I would like to pass in a generic delimited
file with two rows:
- the first row contains header names,
- the second row contains values for each header corresponding to a single
entry.
The
I have created a custom Controller Service for connecting to the Salesforce
Streaming API to receive realtime Salesforce.com activity. Doing so
requires using the CometD Bayeux Protocol and Jetty. I seem to be running
into some class incompatibility issues when I attempt to enable the
service. I
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/285#issuecomment-205353808
They were logged at DEBUG only level and that was the issue since you would
not be able to see them, but now if there is an error the stack trace will be
printed
---
If
Github user ckmcd commented on the pull request:
https://github.com/apache/nifi/pull/303#issuecomment-205345851
Please ignore the request to kick the Travis build. I rebased and that did
it. :-)
---
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/311
---
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 olegz closed the pull request at:
https://github.com/apache/nifi/pull/314
---
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 olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/232#discussion_r58389967
--- Diff:
nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AbstractAMQPProcessor.java
---
@@ -191,6 +201,14
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/313#issuecomment-205314233
+1 Looks good. Pushed changes to master and the support/nifi-0.6.x
branches.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/305
---
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 asfgit closed the pull request at:
https://github.com/apache/nifi/pull/313
---
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/312#issuecomment-205303764
+1 Looks good. Merged to master and the support/0.6.x branch. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on
I have created a custom Controller Service for connecting to the Salesforce
Streaming API to receive realtime Salesforce.com activity. Doing so
requires using the CometD Bayeux Protocol and Jetty. I seem to be running
into some class incompatibility issues when I attempt to enable the
service. I
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/312
---
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/312#issuecomment-205294713
Revieiwng
---
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
I wouldn't advise upgrading to 0.6.0 to address PutKafka issues, as there
is an outstanding bug (NIFI-1701) that truncates messages.
NiFi 0.5.1 with the 0.4.1 Kafka nar is at least functional.
On Mon, Apr 4, 2016 at 6:48 AM, Oleg Zhurakousky <
ozhurakou...@hortonworks.com> wrote:
> Oscar
>
>
Oscar
Would you mind upgrading to NiFi 0.6.0? There were significant improvements to
Kafka module
Thanks
Oleg
On Apr 4, 2016, at 04:21, Oscar dela Pena
> wrote:
Hi NiFi team,
This is our current NiFi flow:
Our Kafka is version 0.8.2 and NiFi
37 matches
Mail list logo