[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[jvwing]

Github user jvwing commented on the pull request:

https://github.com/apache/nifi/pull/267#issuecomment-216431685
  
What would you recommend for this pull request?  No utility?  A simpler 
hashing utility?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi pull request: MINIFI-23 Removing indexing from provena...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi/pull/18


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[jvwing]

Github user jvwing commented on a diff in the pull request:

https://github.com/apache/nifi/pull/267#discussion_r61836807
  
--- Diff: 
nifi-nar-bundles/nifi-iaa-providers-bundle/nifi-file-identity-provider/src/main/java/org/apache/nifi/authentication/file/CredentialsStore.java
 ---
@@ -0,0 +1,229 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.authentication.file;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.io.InvalidObjectException;
+import java.util.List;
+import javax.xml.XMLConstants;
+import javax.xml.bind.JAXBContext;
+import javax.xml.bind.JAXBElement;
+import javax.xml.bind.JAXBException;
+import javax.xml.bind.Marshaller;
+import javax.xml.bind.Unmarshaller;
+import javax.xml.bind.ValidationEvent;
+import javax.xml.bind.ValidationEventHandler;
+import javax.xml.transform.stream.StreamSource;
+import javax.xml.validation.Schema;
+import javax.xml.validation.SchemaFactory;
+
+import org.apache.nifi.authentication.file.generated.ObjectFactory;
--- End diff --

They are used to serialize and deserialize the XML credentials file.  What 
kind of issues are you experiencing?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-981: Added ExecuteHiveQL and PutHiveQL pro...

[bbende]

Github user bbende commented on a diff in the pull request:

https://github.com/apache/nifi/pull/384#discussion_r61832445
  
--- Diff: 
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/SelectHiveQL.java
 ---
@@ -52,15 +54,27 @@
 @EventDriven
 @InputRequirement(Requirement.INPUT_ALLOWED)
 @Tags({"hive", "sql", "select", "jdbc", "query", "database"})
-@CapabilityDescription("Execute provided HiveQL SELECT query against a 
Hive database connection. Query result will be converted to Avro format."
+@CapabilityDescription("Execute provided HiveQL SELECT query against a 
Hive database connection. Query result will be converted to Avro or CSV format."
 + " Streaming is used so arbitrarily large result sets are 
supported. This processor can be scheduled to run on "
 + "a timer, or cron expression, using the standard scheduling 
methods, or it can be triggered by an incoming FlowFile. "
 + "If it is triggered by an incoming FlowFile, then attributes of 
that FlowFile will be available when evaluating the "
 + "select query. FlowFile attribute 'executehiveql.row.count' 
indicates how many rows were selected.")
-public class ExecuteHiveQL extends AbstractHiveQLProcessor {
+@WritesAttributes({
+@WritesAttribute(attribute = "mime.type", description = "Sets the 
MIME type for the outgoing flowfile to application/avro-binary for Avro or 
text/csv for CSV."),
+@WritesAttribute(attribute = "filename", description = "Adds .avro 
or .csv to the filename attribute depending on which output format is 
selected."),
+@WritesAttribute(attribute = "executehiveql.row.count", 
description = "Indicates how many rows were selected/returned by the query.")
--- End diff --

Nit-picking here, but given the rename of the processor, do we want this to 
be selecthiveql.row.count?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-981: Added ExecuteHiveQL and PutHiveQL pro...

[bbende]

Github user bbende commented on a diff in the pull request:

https://github.com/apache/nifi/pull/384#discussion_r61832456
  
--- Diff: 
nifi-nar-bundles/nifi-hive-bundle/nifi-hive-processors/src/main/java/org/apache/nifi/processors/hive/SelectHiveQL.java
 ---
@@ -52,15 +54,27 @@
 @EventDriven
 @InputRequirement(Requirement.INPUT_ALLOWED)
 @Tags({"hive", "sql", "select", "jdbc", "query", "database"})
-@CapabilityDescription("Execute provided HiveQL SELECT query against a 
Hive database connection. Query result will be converted to Avro format."
+@CapabilityDescription("Execute provided HiveQL SELECT query against a 
Hive database connection. Query result will be converted to Avro or CSV format."
 + " Streaming is used so arbitrarily large result sets are 
supported. This processor can be scheduled to run on "
 + "a timer, or cron expression, using the standard scheduling 
methods, or it can be triggered by an incoming FlowFile. "
 + "If it is triggered by an incoming FlowFile, then attributes of 
that FlowFile will be available when evaluating the "
 + "select query. FlowFile attribute 'executehiveql.row.count' 
indicates how many rows were selected.")
-public class ExecuteHiveQL extends AbstractHiveQLProcessor {
+@WritesAttributes({
+@WritesAttribute(attribute = "mime.type", description = "Sets the 
MIME type for the outgoing flowfile to application/avro-binary for Avro or 
text/csv for CSV."),
+@WritesAttribute(attribute = "filename", description = "Adds .avro 
or .csv to the filename attribute depending on which output format is 
selected."),
+@WritesAttribute(attribute = "executehiveql.row.count", 
description = "Indicates how many rows were selected/returned by the query.")
+})
+public class SelectHiveQL extends AbstractHiveQLProcessor {
 
 public static final String RESULT_ROW_COUNT = 
"executehiveql.row.count";
--- End diff --

same as above


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[alopresto]

Github user alopresto commented on the pull request:

https://github.com/apache/nifi/pull/267#issuecomment-216417900
  
I think my earlier comments may have been unclear or ambiguous. I do not 
believe we need a full command-line interface for modifying the configuration 
file, as hand-editing the files is the existing norm. I simply meant that the 
process of protecting a raw password with bcrypt is not an "in-head" operation 
for most instance admins, so we should provide a utility to perform that 
operation. 

While I very much respect the effort that went into the supporting 
infrastructure, I think it is overkill and not consistent with the global 
approach. 


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[alopresto]

Github user alopresto commented on a diff in the pull request:

https://github.com/apache/nifi/pull/267#discussion_r61832014
  
--- Diff: 
nifi-nar-bundles/nifi-iaa-providers-bundle/nifi-file-identity-provider/src/main/java/org/apache/nifi/authentication/file/CredentialsStore.java
 ---
@@ -0,0 +1,229 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.authentication.file;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.io.InvalidObjectException;
+import java.util.List;
+import javax.xml.XMLConstants;
+import javax.xml.bind.JAXBContext;
+import javax.xml.bind.JAXBElement;
+import javax.xml.bind.JAXBException;
+import javax.xml.bind.Marshaller;
+import javax.xml.bind.Unmarshaller;
+import javax.xml.bind.ValidationEvent;
+import javax.xml.bind.ValidationEventHandler;
+import javax.xml.transform.stream.StreamSource;
+import javax.xml.validation.Schema;
+import javax.xml.validation.SchemaFactory;
+
+import org.apache.nifi.authentication.file.generated.ObjectFactory;
--- End diff --

I'm getting a number of issues building the project with these generated 
classes. Why do they need to be generated?


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: Fix for NIFI-1838 & NIFI-1152 & Code modificati...

[PuspenduBanerjee]

Github user PuspenduBanerjee commented on the pull request:

https://github.com/apache/nifi/pull/400#issuecomment-216414833
  
Updated to address Fix for NIFI-1838 & NIFI-1152


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[jvwing]

Github user jvwing commented on a diff in the pull request:

https://github.com/apache/nifi/pull/267#discussion_r61821120
  
--- Diff: 
nifi-nar-bundles/nifi-iaa-providers-bundle/nifi-file-identity-provider/src/main/java/org/apache/nifi/authentication/file/CredentialsCLI.java
 ---
@@ -0,0 +1,207 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.authentication.file;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.util.ArrayList;
+
+import org.apache.nifi.authentication.file.generated.UserCredentials;
+import org.apache.nifi.authentication.file.generated.UserCredentialsList;
+
+
+/**
+ * Command-line interface for working with a {@link CredentialsStore}
+ * persisted as an XML file.
+ *
+ * Usage:
+ * 
+ *   list credentials.xml
+ *   add credentials.xml admin password
--- End diff --

Thanks, I'll try that method.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[alopresto]

Github user alopresto commented on a diff in the pull request:

https://github.com/apache/nifi/pull/267#discussion_r61817392
  
--- Diff: 
nifi-nar-bundles/nifi-iaa-providers-bundle/nifi-file-identity-provider/src/main/java/org/apache/nifi/authentication/file/CredentialsCLI.java
 ---
@@ -0,0 +1,207 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.authentication.file;
+
+import java.io.File;
+import java.io.FileNotFoundException;
+import java.util.ArrayList;
+
+import org.apache.nifi.authentication.file.generated.UserCredentials;
+import org.apache.nifi.authentication.file.generated.UserCredentialsList;
+
+
+/**
+ * Command-line interface for working with a {@link CredentialsStore}
+ * persisted as an XML file.
+ *
+ * Usage:
+ * 
+ *   list credentials.xml
+ *   add credentials.xml admin password
--- End diff --

Accepting the raw password on the command line will mean that it is 
persisted in the terminal history and available to any other processes running. 
It is more secure to use 
[Console#readPassword()](https://docs.oracle.com/javase/7/docs/api/java/io/Console.html#readPassword%28%29)


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-361- Create Processors to mutate JSON data

[YolandaMDavis]

GitHub user YolandaMDavis opened a pull request:

https://github.com/apache/nifi/pull/405

NIFI-361- Create Processors to mutate JSON data

Implementation of the TransformJSON processor using the Jolt library. 
TransformJSON supports Jolt specifications for the following transformations: 
Chain, Shift, Remove, Sort, Cardinality and Default. Users will be able to add 
the TransformJSON processor, select the transformation they wish to apply and 
enter the specification for the given transformation.

Details for creating Jolt specifications can be found 
[here](https://github.com/bazaarvoice/jolt)

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/YolandaMDavis/nifi NIFI-361-0.x

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/405.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #405


commit 873c534a057b051f3b28cac3cc496d59f0c352ef
Author: Yolanda M. Davis 
Date:   2016-04-14T12:19:41Z

NIFI-361 Adding TransformJSON from master. Also changed streams in test 
since 1.7 only supported.
(cherry picked from commit ffc9d19)




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1614 File Identity Provider implementation

[jvwing]

Github user jvwing commented on the pull request:

https://github.com/apache/nifi/pull/267#issuecomment-216353947
  
I rebased the commits on the master branch to resolve conflicts and use the 
updated LoginIdentityProvider interface and Administrator's Guide content.  I 
apologize if it complicates reviewing.  Changes include:

- Improved performance by only reloading the credentials data if the file 
has been modified
- Provided a command-line utility reference implementation
- Added documentation to the Administrator's Guide
- Included a sample login-credentials.xml file to the conf directory


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1213 Added the possibility to register Flo...

[pvillard31]

GitHub user pvillard31 opened a pull request:

https://github.com/apache/nifi/pull/404

NIFI-1213 Added the possibility to register FlowFile assertions in mock 
framework



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pvillard31/nifi NIFI-1213

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/404.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #404


commit 9c006043188a4175295120bfd96580c0c21e74a7
Author: Pierre Villard 
Date:   2016-05-02T17:54:53Z

NIFI-1213 Added the possibility to register FlowFile assertions in mock 
framework




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: Code modification for typeSafety

[apiri]

Github user apiri commented on the pull request:

https://github.com/apache/nifi/pull/400#issuecomment-216305090
  
@PuspenduBanerjee Certainly will.  Currently pending review before I am 
able to incorporate.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi-minifi-cpp pull request: MINIFI-6: Initial Checkin for basic ...

[apiri]

Github user apiri commented on a diff in the pull request:

https://github.com/apache/nifi-minifi-cpp/pull/1#discussion_r61772403
  
--- Diff: Makefile ---
@@ -0,0 +1,40 @@
+CC=g++
+AR=ar
+TARGET_DIR= ./build
+TARGET_LIB=libminifi.a
+TARGET_EXE=minifi
+CFLAGS=-O0 -fexceptions -fpermissive -Wno-write-strings -std=c++11 -fPIC 
-Wall -g -Wno-unused-private-field
+INCLUDES=-I./inc -I./src -I./test -I/usr/include/libxml2 
-I/usr/local/opt/leveldb/include/
+LDDIRECTORY=-L/usr/local/opt/leveldb/out-static/ -L./build
--- End diff --

@benqiu2016 This out-static directory seems to be problematic on OS X.  Is 
additional setup needed beyond brew install leveldb.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: Code modification for typeSafety

[PuspenduBanerjee]

Github user PuspenduBanerjee commented on the pull request:

https://github.com/apache/nifi/pull/400#issuecomment-216302926
  
@apiri Please incorporate PR #370 as soon as you can. It will be a great 
help.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1811 Removed ProcessorLog and updated depe...

[pvillard31]

GitHub user pvillard31 opened a pull request:

https://github.com/apache/nifi/pull/403

NIFI-1811 Removed ProcessorLog and updated dependent interfaces



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pvillard31/nifi NIFI-1811

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/403.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #403


commit 8c6e20382fdff0a2fb3592b2627a67a5656d2e3a
Author: Pierre Villard 
Date:   2016-05-02T15:47:44Z

NIFI-1811 Removed ProcessorLog and updated dependent interfaces




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: Code modification for typeSafety

[apiri]

Github user apiri commented on the pull request:

https://github.com/apache/nifi/pull/400#issuecomment-216268893
  
@PuspenduBanerjee unfortunately the appveyor results are a bit of noise at 
the moment as the associated PR #370 has yet to be incorporated.  As a result, 
out of the box, it is trying to build its default which is not a Maven based 
project.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-981: Added ExecuteHiveQL and PutHiveQL pro...

[bbende]

Github user bbende commented on the pull request:

https://github.com/apache/nifi/pull/384#issuecomment-216246029
  
Latest commits look good, I am a +1 and going to merge to 0.x and master


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: apache nifi focused hackathon/meetup

[Bryan Bende]

All,

Just some thoughts for the NiFi Hackathon Meetup, it might be good to
identify a handful of JIRA's that could be worked on by people fairly new
to the codebase, and provide as much background info as possible on those
issues for someone to hit the ground running.
The goal would be to have a couple of PRs/patches submitted by the end of
the night and merged by a committer.

Of course if those already familiar with the codebase want to come and work
on more advanced issues, or flesh out designs, that is fine too.

Thanks,

Bryan


On Mon, May 2, 2016 at 9:32 AM, Joe Witt  wrote:

> Team,
>
> For those in the MD/DC/VA area or who would be interested in
> participating remotely we are planning to host hackathon as part of
> our normal NiFi meetup here in the area.
>
>   http://www.meetup.com/ApacheNiFi/events/230804255/
>
> On-site we can host about 30 or so folks pretty easily and I am happy
> to setup a video conference for others interested in participating
> directly as well.  The idea will be to use this gathering to focus on
> existing PRs and JIRAs and help work them down and get them addressed.
> The number of open and interesting JIRAs is growing and the same is
> true of PRs.
>
> Discussions during the meetup will be captured and documented via the
> PRs/JIRAs as is normal but also any other discussion/ideas that come
> out will be captured and made available as well.  The meetup must not
> become a way to have disconnected decision making.
>
> If you do signup to join can you please indicate if you plan to be
> on-site or remote and if remote please let me know if you'd like to be
> on a web conference and if we get one or more requests I'll set that
> up.
>
> Also of note those of us organizing this are hackathon rookies so if
> you have ideas/comments/etc.. please share.
>
> Thanks
> Joe
>

Re: Plan to add community links about nifi to website - lazy consensus

[Joe Witt]

Bende's hadoop summit talk is now on the site.

Joey's cool github resource perhap we can just link from our wiki for
now but i'll defer to others to curate that unless i get to it sooner.

thanks

On Tue, Apr 26, 2016 at 8:38 PM, Tony Kurc  wrote:
> The wiki has a bit lower bar for curating, but the experience of leaving
> the website and going to confluence which looks and feels different is less
> than ideal.
>
> I don't know if I have a strong opinion one way or the other, just didn't
> understand what you were suggesting.
> On Apr 26, 2016 11:47 AM, "Joe Witt"  wrote:
>
>> It was so clear in my head - so wrong once written.
>>
>> I was thinking just a straight link to Joey's site but perhaps the
>> wiki page with references to sites like Joey's makes sense.  What do
>> you think?
>>
>> Thanks
>> Joe
>>
>> On Tue, Apr 26, 2016 at 11:45 AM, Tony Kurc  wrote:
>> > I little confused about your proposal for "Externally Maintained
>> > References" in the menu - will it be a link to a page on the wiki? Or
>> would
>> > it be another page CM'ed along with rest of the website?
>> >
>> >
>> >
>> >
>> > On Tue, Apr 26, 2016 at 11:39 AM, Joe Witt  wrote:
>> >
>> >> Team,
>> >>
>> >> Bryan Bende gave a great talk on Apache NiFi at the Hadoop Summit in
>> >> Ireland recently that I'd like to add to the apache nifi website
>> >> videos section.
>> >>   https://www.youtube.com/watch?v=V77M-8ABrdE
>> >>
>> >> Joey Frazee is helping maintain a great github site for general
>> >> ideas/approaches to using and extending NiFi.  Seems a bit like a cool
>> >> incubator concept for NiFi ideas.
>> >>   https://github.com/jfrazee/awesome-nifi
>> >>
>> >> I'd like to add a pointer on our apache nifi website under the
>> >> documentation dropdown to point at 'Externally Maintained References'
>> >> and it would like to Joey's to the 'awesome-nifi' page.
>> >>
>> >> I'll wait a few days (72 hours) and unless there is objection will
>> >> assume lazy consensus.
>> >>
>> >> Thanks
>> >> Joe
>> >>
>>

Re: Reg: Nifi Clustering

[Joe Witt]

Sourav,

The installation procedure does not differ.  However, you do need to
be careful to ensure you're not trying to use the same ports for both
the master and the node.

If you're having trouble go ahead and send some of the configuration
details over and someone can try to assist.

Thanks
Joe

On Mon, May 2, 2016 at 9:05 AM, Sourav Gulati
 wrote:
> Hello Joe,
>
> Could you please provide steps of creating cluster on single node in current 
> version?
>
> Regards,
> Sourav Gulati
>
> -Original Message-
> From: Joe Witt [mailto:joe.w...@gmail.com]
> Sent: Monday, May 02, 2016 6:28 PM
> To: dev@nifi.apache.org
> Subject: Re: Reg: Nifi Clustering
>
> Sourav,
>
> Yes.  And in the upcoming 1.0 release work is being done to eliminate this 
> notion of master/slave altogether and move to instead that at any time any 
> node can carry the responsibility of being a coordinator for the cluster.
>
> Thanks
> Joe
>
> On Mon, May 2, 2016 at 8:49 AM, Sourav Gulati  
> wrote:
>> Hi Team,
>>
>> While creating Nifi Cluster, Can I run master and slave on same node?
>>
>> Regards,
>> Sourav Gulati
>>
>>
>> 
>>
>>
>>
>>
>>
>>
>> NOTE: This message may contain information that is confidential, 
>> proprietary, privileged or otherwise protected by law. The message is 
>> intended solely for the named addressee. If received in error, please 
>> destroy and notify the sender. Any use of this email is prohibited when 
>> received in error. Impetus does not represent, warrant and/or guarantee, 
>> that the integrity of this communication has been maintained nor that the 
>> communication is free of errors, virus, interception or interference.
>
> 
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential, proprietary, 
> privileged or otherwise protected by law. The message is intended solely for 
> the named addressee. If received in error, please destroy and notify the 
> sender. Any use of this email is prohibited when received in error. Impetus 
> does not represent, warrant and/or guarantee, that the integrity of this 
> communication has been maintained nor that the communication is free of 
> errors, virus, interception or interference.

RE: Reg: Nifi Clustering

[Sourav Gulati]

Hello Joe,

Could you please provide steps of creating cluster on single node in current 
version?

Regards,
Sourav Gulati

-Original Message-
From: Joe Witt [mailto:joe.w...@gmail.com]
Sent: Monday, May 02, 2016 6:28 PM
To: dev@nifi.apache.org
Subject: Re: Reg: Nifi Clustering

Sourav,

Yes.  And in the upcoming 1.0 release work is being done to eliminate this 
notion of master/slave altogether and move to instead that at any time any node 
can carry the responsibility of being a coordinator for the cluster.

Thanks
Joe

On Mon, May 2, 2016 at 8:49 AM, Sourav Gulati  
wrote:
> Hi Team,
>
> While creating Nifi Cluster, Can I run master and slave on same node?
>
> Regards,
> Sourav Gulati
>
>
> 
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential, proprietary, 
> privileged or otherwise protected by law. The message is intended solely for 
> the named addressee. If received in error, please destroy and notify the 
> sender. Any use of this email is prohibited when received in error. Impetus 
> does not represent, warrant and/or guarantee, that the integrity of this 
> communication has been maintained nor that the communication is free of 
> errors, virus, interception or interference.








NOTE: This message may contain information that is confidential, proprietary, 
privileged or otherwise protected by law. The message is intended solely for 
the named addressee. If received in error, please destroy and notify the 
sender. Any use of this email is prohibited when received in error. Impetus 
does not represent, warrant and/or guarantee, that the integrity of this 
communication has been maintained nor that the communication is free of errors, 
virus, interception or interference.

Re: Reg: Nifi Clustering

[Joe Witt]

Sourav,

Yes.  And in the upcoming 1.0 release work is being done to eliminate
this notion of master/slave altogether and move to instead that at any
time any node can carry the responsibility of being a coordinator for
the cluster.

Thanks
Joe

On Mon, May 2, 2016 at 8:49 AM, Sourav Gulati
 wrote:
> Hi Team,
>
> While creating Nifi Cluster, Can I run master and slave on same node?
>
> Regards,
> Sourav Gulati
>
>
> 
>
>
>
>
>
>
> NOTE: This message may contain information that is confidential, proprietary, 
> privileged or otherwise protected by law. The message is intended solely for 
> the named addressee. If received in error, please destroy and notify the 
> sender. Any use of this email is prohibited when received in error. Impetus 
> does not represent, warrant and/or guarantee, that the integrity of this 
> communication has been maintained nor that the communication is free of 
> errors, virus, interception or interference.

[GitHub] nifi pull request: NIFI-1830: Fixed problems in the merging logic ...

[mcgilman]

Github user mcgilman commented on the pull request:

https://github.com/apache/nifi/pull/394#issuecomment-216226348
  
Looks good. +1


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1830: Fixed problems in the merging logic ...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/nifi/pull/394


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1560 - Fixing a copy and paste error

[devin-fisher]

GitHub user devin-fisher opened a pull request:

https://github.com/apache/nifi/pull/402

NIFI-1560 - Fixing a copy and paste error

Looks like when the original coder copied code from AuthenticationStrategy 
for the ReferralStrategy and did not change this reference for the error case.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/devin-fisher/nifi NIFI-1560

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/402.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #402


commit 931c7c32b56268d46b4ae4e0caf0e8920d28e83e
Author: Devin Fisher 
Date:   2016-05-02T10:26:13Z

Fixing a copy and paste error

Looks like when the original coder copied code from AuthenticationStrategy 
for the ReferralStrategy and did not change this reference for the error case.




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] nifi pull request: NIFI-1832 Allowing expression language in prope...

[pvillard31]

GitHub user pvillard31 opened a pull request:

https://github.com/apache/nifi/pull/401

NIFI-1832 Allowing expression language in properties with a set of 
allowable values

At the moment, if a property is defined with a set of allowable values AND 
is supporting expression language, then validation will always fail when the 
expression language value is not matching an allowable value. There are two 
options:

- In the processor, add in the allowable values the expression language 
value that is authorized and let the user knows that the expected value MUST BE 
in this specific attribute.

Example: .allowableValues("A", "B", "C", "${myProcessor.type}")
Then the incoming flow files must have this attribute (using 
UpdateAttribute before).

- Authorize any input value when expression language is supported for this 
kind of properties.

This PR is a proposition for the second option.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pvillard31/nifi NIFI-1832

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/nifi/pull/401.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #401


commit de320a6e9e1370964783016538fe07aa1ae6cb17
Author: Pierre Villard 
Date:   2016-05-02T09:57:28Z

NIFI-1832 Allowing expression language in properties with a set of 
allowable values




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---