Github user mans2singh commented on the pull request:
https://github.com/apache/nifi/pull/213#issuecomment-196646278
@aldrin - I've added max buffer size limit check while getting flow files
from the session as you had recommended. I've also kept the batch size limit
in place. I've a
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/277
---
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 enable
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/277#issuecomment-196624448
Verified on OS X with and without JAVA_HOME set to permit the usage of env.
All worked as anticipated.
Performed the same on Cygwin with anticipated results.
GitHub user trkurc opened a pull request:
https://github.com/apache/nifi/pull/278
NIFI-1047 Added additional method to get processId, fixed tools.jar path
for cygwin
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trkurc/nifi NI
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/276#issuecomment-196619738
whoa, something went screwy when I merged this in.
---
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 p
Github user trkurc closed the pull request at:
https://github.com/apache/nifi/pull/276
---
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 enable
GitHub user trkurc opened a pull request:
https://github.com/apache/nifi/pull/277
NIFI-1481 fixed a couple bugs in bash script for cygwin and when JAVA_HOME
not set
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/trkurc/nifi NIF
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/277#issuecomment-196618302
reviewing
---
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
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56106623
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/bootstrap/SpringContextDelegate.java
---
@@ -0,0 +1,141
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56106557
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/SpringContextProcessor.java
---
@@ -0,0 +1,382 @@
+
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56106464
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/SpringContextFactory.java
---
@@ -0,0 +1,139 @@
+/*
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56105950
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/bootstrap/SpringContextDelegate.java
---
@@ -0,0 +1,14
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56105879
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/resources/docs/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
--
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56104556
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/SpringContextFactory.java
---
@@ -0,0 +1,139 @@
+/
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56104123
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/SpringContextFactory.java
---
@@ -0,0 +1,139 @@
+/
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56103524
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/java/org/apache/nifi/spring/SpringContextProcessor.java
---
@@ -0,0 +1,382 @@
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56103351
--- Diff:
nifi-nar-bundles/nifi-spring-bundle/nifi-spring-processors/src/main/resources/docs/org.apache.nifi.spring.SpringContextProcessor/additionalDetails.html
--
Github user trkurc commented on a diff in the pull request:
https://github.com/apache/nifi/pull/271#discussion_r56102458
--- Diff: nifi-nar-bundles/pom.xml ---
@@ -54,7 +54,8 @@
nifi-scripting-bundle
nifi-elasticsearch-bundle
nifi-amqp-bundle
Team,
Things are closing in well but we need to get pretty specific on these
to keep the release moving roughly along the lines of the schedule
we've discussed previously. Those of you who have tickets on here
that can be moved to 0.7.0 please do so. Otherwise, let's please keep
discussion/statu
GitHub user trkurc opened a pull request:
https://github.com/apache/nifi/pull/276
NIFI-1047 Added additional method to get processId, fixed tools.jar path
for cygwin
Uses ugly internal classes, but works on windows
You can merge this pull request into a Git repository by running:
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/218#issuecomment-196564618
So, after discussion with @apiri, we removed the env batch script because
it did not work due to limitations of bootstrap, and reworked nifi.sh to build
the classpath for B
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/218
---
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 enable
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-196535593
I'll look at it. I think I know what's going on.
---
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 proj
Github user mosermw commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-196532379
Yep, that's what I did. The TibjmsConnectionFactory must not see the
truststore I set in the SSL Context Service. I'm worried that different JMS
providers require differ
Excellent, thanks!
> On Mar 14, 2016, at 4:57 PM, Aldrin Piri wrote:
>
> Given the positive response, I have submitted requests for both a new JIRA
> and new Git repository which INFRA has kindly stood up for us. MiNiFi JIRA
> and Git are available at [1] and [2], respectively.
>
> [1] https:/
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-196527092
@mosermw shouldn't you just be able to create a typical SSL controller
service and set the "SSL Context Service" property to point to it? This should
automatically use
Given the positive response, I have submitted requests for both a new JIRA
and new Git repository which INFRA has kindly stood up for us. MiNiFi JIRA
and Git are available at [1] and [2], respectively.
[1] https://issues.apache.org/jira/browse/MINIFI/
[2] https://git-wip-us.apache.org/repos/asf/n
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/275#discussion_r56073702
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core-api/src/main/java/org/apache/nifi/controller/SchedulingAgentCallback.java
---
Github user mosermw commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-196508227
Tested using Tibco with SSL, didn't work.
ERROR o.a.n.jms.processors.PublishJMS
org.springframework.jms.JmsSecurityException: Can not initialize SSL client: no
tr
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/213#issuecomment-196476035
Hey @mans2singh,
Just wanted to see how the progress was going. We are coming up on release
time for 0.6.0 and need to start wrapping things up. If this is somethi
Sumo,
I do believe that you should be okay leaving that java.arg.15 in, in that case.
The ZooKeeper Client
will use the "Client" section of that file, if it is defined. In the example
that you provided, that Client section
does not exist, so it is okay. What would not work in this case would be
Thanks Mark.
I had java.arg.15 setting in bootstrap.conf from NiFi 0.4.x to make putHDFS
processor work with my MapR cluster. If I remove it, putHDFS will fail.
Now with NiFi 0.5.1,
if I set nifi.state.management.embedded.zookeeper.start=false ,
can I point to dedicated external ZooKeeper in
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/275#discussion_r56046482
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/scheduling/AbstractSchedulingAgent.jav
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/275#discussion_r56045229
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java
---
@@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/275#discussion_r56044999
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java
---
@@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/275#discussion_r56044931
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/StandardProcessorNode.java
---
@@
GitHub user olegz opened a pull request:
https://github.com/apache/nifi/pull/275
NIFI-1464 life-cycle refactoring part-2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/olegz/nifi NIFI-1464B
Alternatively you can review and appl
Thanks for the response. It gave my additional context such that I can
proceed with more confidence. I've been playing with creating additional
sessions and I believe that it will work for my use case. But I will keep
the duplicate flowfile potential issue in mind, though.
Thanks again.
Devin
On
Sumo,
If your intent is to use an external ZooKeeper, you should not be starting the
embedded ZooKeeper.
You will also not want to set the java.arg.15 parameter there to point to a
login config file, as that is
necessary only when enabling Kerberos - not for use when security disabled.
So you w
I am getting following error when NiFi Cluster started with embedded
ZooKeeper enabled.
I would like to configure external ZooKeeper for NiFi State Management without
interfering with java.security.auth.login.config setting for MapR HDFS. Can
somebody provide me instructions how to configur
Github user digitalplummer commented on the pull request:
https://github.com/apache/nifi/pull/222#issuecomment-196402216
Tested on IBM MQ 7.5 and greater
WebSphere
Tibco
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/218#issuecomment-196400346
@apiri - I tried last night to get the pid to get Windows to work. I could
not. I say we shelve the env batch script (remove it for now from the patch
set).
On cy
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/218#issuecomment-196384976
@trkurc What is the final verdict on handling of Windows and Cygwin? Are
we punting those for now? If so, would like to provide handling for env with
cygwin in nifi.sh and
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/218#issuecomment-196365140
@trkurc Patch unfortunately is not applying even on a fresh checkout of the
218 PR. Will checkout your branch and work from there.
Patch issue was:
> $ git
Github user apiri commented on the pull request:
https://github.com/apache/nifi/pull/218#issuecomment-196348408
@trkurc Okay, will apply over the top and review. Thanks!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-196309847
@joewitt yes I can have a look this afternoon. I'll try to propose
something before the end of the day.
---
If your project is set up for it, you can reply to this ema
Github user mattyb149 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/261#discussion_r55995978
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/QueryDatabaseTable.java
---
@@ -0,
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-196284703
Thank you @pvillard31 . That does make sense and in the case that there is
no request body being sent over I am supportive of the notion of not sending
the content type h
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/272#issuecomment-196200486
Definitely agree with you that this API should not act this way.
Anyway, just to clarify, this is only in the case there is no body/content
sent with the reques
Hi Adam,
Yes it makes sense. It was just an idea for an additional possibility, not
a fundamental change. Anyway, I used other processors as suggested.
Thanks Adam,
Pierre
On Mar 13, 2016 23:52, "Adam Taft" wrote:
> I think it makes total sense that POST/PUT requests read from the flowfile
> co
50 matches
Mail list logo
