All,
I have submitted a patch for NIFI-210 to offer scripting capabilities, my
GitHub feature branch is at:
https://github.com/mattyb149/nifi/tree/script-processors
I would truly appreciate any comments, questions, or suggestions about this
capability.
Regards,
Matt
On 12/16/15, 11:41
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/143#issuecomment-165207075
Addressed
---
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 mattyb149 opened a pull request:
https://github.com/apache/nifi/pull/144
NIFI-210 Add ExecuteScript and InvokeScriptProcessor
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mattyb149/nifi script-processors
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/143#discussion_r47814247
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/TestPutKafka.java
---
@@ -474,6 +475,18
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/143#discussion_r47814878
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/TestPutKafka.java
---
@@ -474,6 +475,18
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/143#discussion_r47814866
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/TestPutKafka.java
---
@@ -474,6 +475,18 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/143#discussion_r47814729
--- Diff:
nifi-nar-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/test/java/org/apache/nifi/processors/kafka/TestPutKafka.java
---
@@ -474,6 +475,18 @@
Thank you Sumanth
Just raised https://issues.apache.org/jira/browse/NIFI-1296 so you can track it
and contribute if you have more details/expertise. My biggest concern is
compatibility with older brokers. Currently even though we’ve upgraded to 0.9
it is still compatible with 0.8 brokers for
Hi Oleg,
For my case NiFi (consumer) has to talk to Kafka cluster behind firewall and it
was difficult got Kafka brokers and ZooKeeper ports opened.
I noticed that 0.9.0.0 support consumers directly communicate to Kafka brokers
with `bootstrap.servers` setting.
it might be good idea if you
May be we can create getKafka2 for 0.9.0.0, leaving original form backward
compatibility.
I will try new consumer API tomorrow and share here.
My concern with old consumer API is, it depends on zookeeper and worried, I
may have to open multiple ports on firewall as described here
The question is "Is NiFi supposed to be a full ETL tool"?
On Dec 16, 2015 11:27 AM, "Angry Duck Studio"
wrote:
> Shweta,
>
> I think your issue demonstrates one of my minor complaints with NiFi --
> that you always have to think in terms of several little, built-in
Github user olegz closed the pull request at:
https://github.com/apache/nifi/pull/143
---
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 the pull request:
https://github.com/apache/nifi/pull/143#issuecomment-165296041
Merged
---
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 opened a pull request:
https://github.com/apache/nifi/pull/142
NIFI-1289 added support for refreshing properties
- Added _getNewInstance()_ operation to NiFiProperties to ensure there is a
way to refresh/reload NiFi properties
- Fixed javadocs
You can merge
I added https://issues.apache.org/jira/browse/NIFI-1291 to keep this going.
On Sun, Dec 13, 2015 at 10:11 PM, Joe Witt wrote:
> This is a great point as that is a non-trivial pattern and one that
> can be reused. I could definitely see value in spinning out a
> nifi-commons
It is a fair criticism that sometimes the cohesion level of processors
can be simply too much. Early on I used to 'fight' to find the right
abstraction and argue that others do the same. But what I've found is
that it is better to let it happen naturally and to offer options.
Matt, I think your
16 matches
Mail list logo