Congrats Joe!
> On May 16, 2016, at 11:00 PM, Joe Witt wrote:
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Joe Percivall has accepted the PMC's invitation to join the Apache
> NiFi PMC. We greatly appreciate all of Joe's hard work and generous
>
Welcome Joe!
> On May 16, 2016, at 11:00 PM, Joe Witt wrote:
>
> On behalf of the Apache NiFI PMC, I am very pleased to announce that
> Joe Percivall has accepted the PMC's invitation to join the Apache
> NiFi PMC. We greatly appreciate all of Joe's hard work and generous
>
In any event, I think creating JIRA ticket (regardless of how right/wrong it
may be) would be appropriate in such settings as well as producing a fix and a
PR/Patch essentially allowing it to be vetted by ASF process.
On the other hand I also hear Tony’s point about "short turnaround”. Certain
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/451#issuecomment-219717800
@pvillard31 all merged, but it seems like the auto-close hook didn't work.
Could you please close this PR?
---
If your project is set up for it, you can reply to this
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63526995
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63533161
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Thanks everyone! I am very excited to continue working on this awesome project
as part of the PMC.
Joe
- - - - - -
Joseph Percivall
linkedin.com/in/Percivall
e: joeperciv...@yahoo.com
On Tuesday, May 17, 2016 9:07 AM, Mark Payne wrote:
Welcome Joe!
> On May 16,
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/436#issuecomment-219738116
Since @markap14 has already reviewed this and merged it into 0.x branch, I
am going to merge this into master myself so we don't lose track of this.
---
If your project
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63534793
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63523209
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63524926
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63530121
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/448
---
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 joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63533145
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user joewitt commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63527657
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user pvillard31 closed the pull request at:
https://github.com/apache/nifi/pull/451
---
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/416#discussion_r63529484
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Github user bbende commented on the pull request:
https://github.com/apache/nifi/pull/448#issuecomment-219736438
+1 Full build passes with contrib-check, was able to create a flow with
controller services working as expected. Ran into an issue importing a template
with a controller
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/392#issuecomment-219721262
@olegz I pushed out new commits which address your comments. Also I added a
bit more functionality I noticed other MQTT projects expose. Lastly I
overhauled the unit
"After all, attendees of such event are the community and if there is
a consensus among all, that should be enough for an implied +1. Don’t
you agree?"
- Definitely share that view with a modifier that to be as inclusive
as we should we need to remember that not all the community will be
there.
Team,
Want to start zeroing in on the details of the next releases. We had
a good set of discussions around this back in January and have since
been executing along this general path [1].
On the 0.x line the next release would be 0.7.0. There does appear to
be a lot of useful
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63532252
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63533978
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63535091
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63536744
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
hi there, I am using StoreInKiteDataset , and when I give the dataset URI as
"dataset:hdfs:/user/xxx/dataset" path, it says "is invalid because dataset
URI is invalid:unknown dataset URI", not sure why its saying invalid.
I used Kite command
>./kite-dataset create
Andy, all,
thank you so much for your help. I have already started using ExecuteScript
quite heavily, in particular for data cleaning and wrangling between
processors. I was only concern that being experimental, it was not
particularly recommended to use in complex dataflow like the one I am
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63549263
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63551055
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/436
---
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 JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63539198
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63540545
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63537518
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63539712
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63545947
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63536461
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63536287
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63547530
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Hi,
I have a quite complex dataflow and half way through I am returned with a
Json file that looks like this:
{"field1": "D",
"field2": "12345",
"field3": "myText",
"field4": ,
"field5": "B2",
"field6": "B",
"field7": 74664",
"field8": 2,
"field9": [something."2334", something."9973"],
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63539083
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63558222
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user eorgad commented on the pull request:
https://github.com/apache/nifi/pull/416#issuecomment-219781233
Not yet, my "mvn clean install -Pcontrib-check" fails ...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Hi, I have had a look at the available processors and it seems I can do the
following:
GetFile (with my json already created) ->EvaluateJsonPath -> UpdateAttribute
->PutFile
So, lets get started with simply adding the missing '"", I am under the
impression that I can use something like this:
Glad to hear ExecuteScript is helping you. It is becoming very heavily used as
a “glue” processor to adapt edge cases, and (without speaking for Matt), I
would consider it no longer “experimental” when used with certain scripting
languages (Groovy, primarily). It still has some rough edges with
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/392#issuecomment-219808772
@JPercivall just a heads up; the branch now has merge conflicts
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63577875
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63578737
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63578922
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63579631
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63579787
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63580066
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63580288
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63579264
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63580606
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
+/*
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63581819
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63583614
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63583750
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63583956
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@ -0,0
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63584682
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63584936
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63585015
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user olegz commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63585043
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
+/*
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63585228
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/common/AbstractMQTTProcessor.java
---
@@
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63585339
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/PublishMQTT.java
---
@@ -0,0 +1,239 @@
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219830951
Reviewed and tested. LGTM. All tested flows were OK.
Few minor remarks:
- I'd update @CapabilityDescription to help users differentiate Publish/Put
and
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219832281
Thanks @pvillard31! Regarding @joewitt's comment, yes it is still an
outstanding issue since we need to modify ReflectionUtils to allow the
invocation of non-public
Github user andrewmlim commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219836475
@pvillard31 @olegz Just wanted to let you both know that during the demo of
these new Kafka processors, it was suggested that we also update the Put and
Get Kafka
I don't know if this use-case is too specific to be a feature for a future
release, but I would like to see the AttributesToJSON processor support
multi-valued fields.
In my use-case, I am storing JSON documents into Solr, and there are two
ways to store multi-valued fields: using an array and
Github user olegz commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219837303
@andrewmlim yep some of it has already been addressed, but I'd stay away
from munging yet another JIRA to this one. So good point and will be reviewed
and addressed once
I'm definitely in favor of releasing 0.7.0, but I don't think we need be
rigid about the schedule. If delaying 0.7.0 a few weeks (2-4?) helps pace
us towards a 1.0 in mid- to late-Summer, that seems reasonable to me. Do
we believe that is still a likely target?
Thanks,
James
On Tue, May 17,
Agreed! I would like to see 0.7 within 2-3 weeks as there are a lot of
improvements and new features/components in it already, and would like to give
it some miles before 1.0.
Oleg
> On May 17, 2016, at 4:02 PM, James Wing wrote:
>
> I'm definitely in favor of releasing
Ok - i'm good with an 0.7 release too and think it is a good idea. I
am happy to RM the release.
I'd like to select a date at which we're happy to call the 0.x line
then feature complete which means 0.7 would be the last feature
bearing 0.x release and from then on it would be bug fixes only
Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/366#issuecomment-219842672
i certainly agree. this thing has to be one of the most reviewed PRs of
all time. +1 please do merge.
---
If your project is set up for it, you can reply to this email
Supporting multi-valued fields on AttributesToJson would be a nice
feature...
One approach might be to provide a strategy property that lets the user
choose the handling.
For example, if there was an attribute called attribute1 with a value of
a,b,c...
One user may want the json to end up as:
{
Andy, thanks for sharing this with me, I was not aware of it. Unfortunately,
for a number of reasons, I will need to use 0.5.1 for the time being, so I
was looking at existing processors. I have had a go with the combination
EvaluateJsonPath + UpdateAttribute and although I am not a bit more
This schedule seems appropriate to me. Once 0.7.0 is released and we confirm
the release date for 1.0, feature development is completely targeted to 1.0,
correct? Security and data loss bug fixes would still be backported, but new
features would not.
Andy LoPresto
alopre...@apache.org
Github user pvillard31 commented on the pull request:
https://github.com/apache/nifi/pull/443#issuecomment-219855457
Maven build with contrib-check OK.
Reviewed and it LGTM, nice unit testing.
Tested with two different flows and it is working as expected.
I'm a +1
---
If
Ilaria,
Matt just wrote a JSON validator Groovy script for another answer on the
mailing list. I’ve included it below. You can modify this to perform validation
on the incoming JSON as defined by your custom schema, and then applying the
various fixes. I’m not familiar with the library Matt is
That usually means that the dataset URI is malformed in some way. Can you
confirm that there's no white spaces, or special characters that might be
messing up the path? I've not had this issue writing to HDFS paths.
On Tue, May 17, 2016 at 10:40 AM, pradeepbill
wrote:
>
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/392#discussion_r63608020
--- Diff:
nifi-nar-bundles/nifi-mqtt-bundle/nifi-mqtt-processors/src/main/java/org/apache/nifi/processors/mqtt/ConsumeMQTT.java
---
@@ -0,0 +1,341 @@
Github user JPercivall commented on the pull request:
https://github.com/apache/nifi/pull/392#issuecomment-219860709
@olegz just pushed out a new patch addressing the second round of comments
and rebased to master to fix the merge conflicts
---
If your project is set up for it, you
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/443
---
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
I believe that is right Andy. The support guide articulates that we
could do a feature release upon request if there was some specific
need a community member had but that otherwise the only releases on an
older line still supported would be focused on security/data loss type
items.
Thanks
Joe
GitHub user bbende opened a pull request:
https://github.com/apache/nifi/pull/452
NIFI-1884 Defining API for Users, Groups, and Policies
This pull request introduces the concept of a MutableAuthorizer which is an
interface that extends the recently introduced Authorizer. A
Github user YolandaMDavis commented on a diff in the pull request:
https://github.com/apache/nifi/pull/424#discussion_r63613822
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-transform-json-ui/src/main/webapp/app/components/processor/processor.service.js
---
@@ -0,0 +1,52
The way I read the release support document, I don't think the feature
cut-off for the 0.x branch happens when we confirm a release date for 1.0,
I think it occurs once we actually release 1.0. Maybe the cut-off can
happen once we declare the first 1.0 release candidate. I'm sure we will
spend
Github user YolandaMDavis commented on the pull request:
https://github.com/apache/nifi/pull/424#issuecomment-219871908
@mcgilman had same conversation with @scottyaslan last week concerning
referencing js in nifi-web-ui. My main concern was versioning e.g. changes
happening at that
Mike
I agree with the letter of the reading so this thread is to discuss
the spirit of it and how to best apply it to our situation and
community now. Whether it is 'just before' or 'just after' or 'same
time' I think it is within the intent. I just want us to be clear
what it is. It is extra
Github user mcgilman commented on the pull request:
https://github.com/apache/nifi/pull/424#issuecomment-219881237
@YolandaMDavis Yep. We're definitely on the same page here. However, we
currently have not formally established any APIs/components/widgets for UI
extensions to consume.
I think Mike’s read on the published guidelines is correct, but I agree with
Joe that if we release 0.7 two weeks before 1.0, feature development that is
merged after 0.7 does not need to be backported. Maybe this is something we
should clarify on the wiki once we reach a consensus.
Andy
Github user YolandaMDavis commented on a diff in the pull request:
https://github.com/apache/nifi/pull/424#discussion_r63624220
--- Diff:
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-api/src/main/java/org/apache/nifi/web/StandardNiFiServiceFacade.java
---
Github user YolandaMDavis commented on a diff in the pull request:
https://github.com/apache/nifi/pull/424#discussion_r63629669
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-transform-json-ui/src/main/java/org/apache/nifi/web/standard/api/processor/ProcessorResource.java
---
Github user alopresto commented on a diff in the pull request:
https://github.com/apache/nifi/pull/416#discussion_r63631088
--- Diff:
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/util/SCPTransfer.java
---
@@ -0,0
Hi Sumanth,
Sorry no one got back to you on this.
I don't know that much about how the framework gets access to the node id,
so maybe Mark, Joe, or others could chime in about whether the node id
could be made accessible from expression language.
I know that expression language currently has a
Github user YolandaMDavis commented on the pull request:
https://github.com/apache/nifi/pull/424#issuecomment-219902820
@mcgilman no problem. will refer to just codemirror in nifi-web-ui for 0.x
and both angular and codemiror in 1.0 (since angular is only available in that
module in
Hi Arturo,
Sorry for the delayed response, and thanks for pointing this out.
I don't have that much experience using sequence files, but assuming the
".sf" suffix has no meaning besides aesthetics, then it seems like there
could be two possible solutions...
One would be to not force the ".sf"
96 matches
Mail list logo