Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/148#issuecomment-174110900
@olegz - I am still working through the locking on paper. I gave up on
getting stack traces. We have a week or so before 0.5.0, if I don't make
progress I think we go with
Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/148#issuecomment-174110924
That 'deadlock' above should be readlock
---
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 doe
I agree, Matt. Not advocating strongly for prioritizing mobile now, but I could
see value in using tablets to do read-only checks on nodes in physically
distributed scenarios.
Andy LoPresto
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
> On Jan 2
Safari is certainly supported and I neglected to include it in my original
post. Sorry about that. We currently state in the user guide that we
support Safari 8. I'll do a little research but I'll likely use a relative
version like we're doing with Firefox and Chrome to keep things consistent
with
Thanks Matt. I didn’t see any mention of Safari (OS X) [1] or MobileSafari
(iOS). Same with Chrome for Mobile [2]. Are mobile clients supported at all?
[1] http://www.apple.com/safari/
[2] https://www.google.com/chrome/browser/mobile/
Andy LoPresto
alopresto.apa...@gmail.com
PGP Fingerprint: 70E
All,
I wanted to take a moment to revisit this topic. As previously stated, the
version of FireFox and Chrome that will be officially supported is
'Current' and 'Current - 1' simply based on some of the dependencies that
we utilize as outlined earlier.
Due to Microsoft officially dropping technic
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/179
---
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 mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-174050331
Awesome @bbende great work! I'll go ahead and merge this in now. Thanks
everyone!
---
If your project is set up for it, you can reply to this email and have your
reply a
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-174049864
Just a quick update on the scenario where some messages get resent...
I turned on rsyslog debug and I noticed that rsyslog seemed to be queueing
up responses until
Thanks for the quick response.
I solved the problem by following the advice @
http://deploymentzone.com/2014/01/06/aws-instances-and-java-net-unknownhostexception/
I modified my /etc/hosts file
#!/bin/bash
HOSTNAME=`hostname`
ETC_HOSTS=${1:-/etc/hosts}
if ! grep $HOSTNAME $ETC_HOSTS > /dev
Validation errors do not indicate success or failure of the request. The
component will be created and the validation errors are to inform the user
what else needs to be addressed before the component can be
enabled/started/etc. It is safe to rely on the success response code.
Matt
On Fri, Jan 22
Got it. I see it is hidden behind some other processors. So what about the
validation errors?
Is it safe to rely only the HTTP status code of 201.
On 1/22/16, 11:25 AM, "Matt Gilman" wrote:
>Paresh,
>
>So the Response in your original email was from the curl command?
>
>If so, can you trying se
Paresh,
So the Response in your original email was from the curl command?
If so, can you trying searching in the UI for the value "TestCurlPort" or
look in the birdseye/overview on the right to see if maybe the component is
just not in the current viewport?
Matt
On Fri, Jan 22, 2016 at 2:20 PM,
Again.
curl -X POST -H "Content-Type: application/x-www-form-urlencoded;
charset=UTF-8" http://lcess-groups/root/input-ports --data
"version=58&clientId=2c4a82b5-1bec-4db6-af0c-d50f5facefcb&name=TestCurlPort
&x=30&y=30"
On 1/22/16, 11:16 AM, "Paresh Shah" wrote:
>Typo. The command is
>
>curl
Typo. The command is
curl -X POST -H "Content-Type: application/x-www-form-urlencoded;
charset=UTF-8"
http://localhost:9080/nifi-api/controller/process-groups/root/input-ports
--data
"version=58&clientId=2c4a82b5-1bec-4db6-af0c-d50f5facefcb&name=TestCurlPort
"
UI shows the yellow icon with the m
Paresh,
The URI in your curl command appears corrupt. I'm guessing that was an
issue with copying and pasting into the email.
Just to clarify...
1) The Response in your email is the response from the curl command?
2) What error message do you see in the UI?
Matt
On Fri, Jan 22, 2016 at 2:03 P
Github user markap14 commented on the pull request:
https://github.com/apache/nifi/pull/158#issuecomment-174013946
@jdye64 - this is awesome! A few NiFi-isms to work out, which i commented
on inline but otherwise looks good to go. Thanks for all of the work that
you've put in here!
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50576416
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
I have not been able to create a InputPort at the root level using the
following.
curl -X POST -H "Content-Type: application/x-www-form-urlencoded;
charset=UTF-8" http://lcess-groups/root/input-ports --data
"version=58&clientId=2c4a82b5-1bec-4db6-af0c-d50f5facefcb&name=TestCurlPort&x=30&y=30”
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50576123
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575812
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575707
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575577
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575282
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575133
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575093
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50575110
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50574984
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/158#discussion_r50574955
--- Diff:
nifi-nar-bundles/nifi-kite-bundle/nifi-kite-processors/src/main/java/org/apache/nifi/processors/kite/InferAvroSchema.java
---
@@ -0,0 +1,454 @@
EC2 instances have a public facing Hostname and IP and a private facing
Hostname and IP. My thought is that you are using the public facing
hostname or IP. The problem there is that public facing hostname or IP
will not match up with the only hostname and IP Java sees associated with
that instanc
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/179#issuecomment-173968940
@trkurc thanks for the review, i liked your idea about the
AsyncChannelDispatcher extending ChannelDispatcher so I went ahead and did
that, and addressed the other stuff as
Howdy,
I'm trying to run NiFi on an ec2 instance. In nifi.properties if I leave
blank
nifi.web.http.host=
and
nifi.remote.input.socket.host=
I get in the log nifi-bootstrap.log:
2016-01-22 14:57:06,592 WARN [main] org.apache.nifi.bootstrap.RunNiFi Failed
to obtain hostname for notification du
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/148#issuecomment-173941919
@trkurc @joewitt @markap14 Ok, I was not able to reproduce the deadlock
with _readLock_, that said I am voting for removal of any lock from stop
routine to avoid further co
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/167#issuecomment-173939440
@trkurc I understand and thank you for merging it. That said, there are
improvements efforts under way which hopefully would address all of our
concerns.
---
If your proj
Mans,
See here for a developer guide which includes processor development
https://nifi.apache.org/docs/nifi-docs/html/developer-guide.html
You are correct in what the primary node indicator for a processor
does - no lifecycle differences other than it won't get scheduled on
the other nodes.
Th
Hi:
Is there any documentation on how to develop a processor and what's the
lifecycle of a processor that is required to be executed on only one node in a
cluster ? I believe this can be done if the processor is executed on the
primary node but am not sure of the lifecycle/contract/etc for suc
36 matches
Mail list logo
