Github user trkurc commented on the pull request:
https://github.com/apache/nifi/pull/113#issuecomment-159446567
reviewing now.
---
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
Oleg,
Actually the jars were removed [1] and we already re-added them when we
discovered it in this thread [2]
[1] https://issues.apache.org/jira/browse/NIFI-1134
[2]
No qualms here. If they look good to go while the work and testing
surrounding NIFI-655 wraps up, they might as well be included. Would not
want to delay the release should any of these become protracted in terms of
iterations.
On Tue, Nov 24, 2015 at 4:05 PM, Tony Kurc wrote:
Agreed. I know there has already been a good deal of discussion about
design on all these.
On Tue, Nov 24, 2015 at 4:14 PM, Aldrin Piri wrote:
> No qualms here. If they look good to go while the work and testing
> surrounding NIFI-655 wraps up, they might as well be
Thanks Adam and Oleg.
My case is similar to Adam's.
NiFi is running on a node, that doesn’t have Hadoop client configured. It have
to invoke a script on other edge node that has Hadoop client setup.
I think you guys may have configured password less login for SSH (keys?)
In my case the
Joe - I reviewed NIFI-1107 when it was a processor on its own
(PutS3Multipart) and have an S3 testbed set up. I'm working through it now.
I believe Joe S. has been stress testing it as well. The good news is that
the code path for small files to S3 is largely unmolested, so it is not as
high risk
understood - thanks.
On Tue, Nov 24, 2015 at 10:28 PM, Tony Kurc wrote:
> Joe - I reviewed NIFI-1107 when it was a processor on its own
> (PutS3Multipart) and have an S3 testbed set up. I'm working through it now.
> I believe Joe S. has been stress testing it as well. The good
Sorry if this question may have been answered previously:
I am implementing two custom processors (bundled separately as NAR files), both
depends on Groovy Jar.
instead of bundling Groovy Jars in each NAR, is there a way to share jars that
don’t have any processors.
Should we consider NiFi
These tickets [1][2] address the incorrect validation errors we were seeing for
processors that include the Input Required annotation. These were bugs that
slipped through the NIFI-810 the review. Would be good to include if possible
but I understand we need to draw the line somewhere.
As for
Sumo
'is there a way to share jars...'
For this sort of classloader sharing mechanism you can see a
description here [1].
For adding optional language packs I know there is work underway on a
couple of tickets to make it easy to have various scripting languages
nicely invoked by processors or
For 1198 and 1203 those should be included. Those are the sorts of
things we're going to be finding/fixing in the testing phase anyway.
Also, since they're impacting an as of yet unreleased feature we
really need the multiple eyes on testing which is how these were
found.
For NIFI-655 why not
Tomorrow I will update the documentation for NIFI-655 and let the PR commence.
While that is ongoing I'll cycle back to testing this configuration.
Matt
Sent from my iPhone
> On Nov 24, 2015, at 10:44 PM, Joe Witt wrote:
>
> For 1198 and 1203 those should be included.
So, I beat on the the patch for NIFI-1107, and as I suspected, it is
awfully low risk for existing flows, but I think I'd need a second opinion
on how state is kept for resuming uploads. I believe it will work, and it
looks like a lot of the edge cases are covered if somehow state is lost or
Tags are a great place to mark experimental. We used to plan for this
concept outright and make it look at scary and such on the ui. But
folks just didn't care. They used it anyway. Happy to revisit it but
for now perhaps just adding a tag of experimental is enough.
If the existing code path
Sumo,
On Tue, Nov 24, 2015 at 10:27 PM, Sumanth Chinthagunta
wrote:
> I think you guys may have configured password less login for SSH (keys?)
>
Correct. I'm using SSH key exchange for authentication. It's usually
done password-less, true, but it doesn't necessarily have
GitHub user jskora opened a pull request:
https://github.com/apache/nifi/pull/132
NIFI-1107 - Integrate Multipart uploads into the PutS3Object processor.
* Add nifi-ssl-context-service-nar to nifi-aws-nar pom.
* Add nifi-ssl-context-service-api to nifi-aws-processors pom.
*
Did you configure the S2S port on all the Nodes in the cluster you are
trying to S2S to?
In addition to setting the port on those Nodes, you should also set the S2S
hostname. The hostname entered should be resolvable and reachable by the
systems trying to S2S to that cluster.
Thanks,
Matt
On
Yeah the S2S port is set on all node.
What should the host be set to on each machine? I first set it to the NCM
ip on each machine in the cluster. Then I set the host to be the ip of each
individual machine without luck.
The S2S port is open to the internet for the entire cluster for those
Are there any NiFi processors to execute remote commands via SSH?
I need to SSH to a remoter server and run a shell script on schedule basses.
thinking of using NiFi’s scheduling and argument passing capability.
I find this lib can be used, if no such processor exist.
Hello Sumo,
At present there are no such processors to do this. I know it has
been done in the past but that was not in an open source environment
so don't have anything to show for it.
It could be a great contrib.
Thanks
Joe
On Tue, Nov 24, 2015 at 11:32 AM, Sumanth Chinthagunta
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/131#issuecomment-159345927
@markap14 @trkurc The PR comments were addressed. I was hoping to get
Kafka embedded server with this commit as well (for testing), but so far it
doesn't appear to be very
Tony
I may have (accidentally) found what you were looking for. Somehow I can’t find
the original email thread, but it was about something along the lines of
who/where/how generated JAR for this: 'File exJar = new
File("src/test/resources/ExecuteCommand/TestSuccess.jar");’
Well, here it is
Dear, in nifi-0.3.0-source-release.zip , in the package
org.apache.nifi.attribute.expression.language;there seems antlr lost.Then how
to fix it.tks
23 matches
Mail list logo