date:20180518

[jira] [Commented] (NIFI-5213) Allow AvroReader with explicit schema to read files with embedded schema

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481426#comment-16481426
 ] 

ASF GitHub Bot commented on NIFI-5213:
--

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

https://github.com/apache/nifi/pull/2718#discussion_r189422180
  
--- Diff: 
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/java/org/apache/nifi/avro/AvroReaderWithExplicitSchema.java
 ---
@@ -17,33 +17,61 @@
 
 package org.apache.nifi.avro;
 
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
 import java.io.EOFException;
 import java.io.IOException;
 import java.io.InputStream;
+import java.io.SequenceInputStream;
 
 import org.apache.avro.Schema;
+import org.apache.avro.file.DataFileStream;
 import org.apache.avro.generic.GenericDatumReader;
 import org.apache.avro.generic.GenericRecord;
 import org.apache.avro.io.BinaryDecoder;
 import org.apache.avro.io.DatumReader;
 import org.apache.avro.io.DecoderFactory;
-import org.apache.nifi.schema.access.SchemaNotFoundException;
+import org.apache.commons.io.input.TeeInputStream;
 import org.apache.nifi.serialization.MalformedRecordException;
 import org.apache.nifi.serialization.record.RecordSchema;
 
 public class AvroReaderWithExplicitSchema extends AvroRecordReader {
 private final InputStream in;
 private final RecordSchema recordSchema;
 private final DatumReader datumReader;
-private final BinaryDecoder decoder;
+private BinaryDecoder decoder;
 private GenericRecord genericRecord;
+private DataFileStream dataFileStream;
 
-public AvroReaderWithExplicitSchema(final InputStream in, final 
RecordSchema recordSchema, final Schema avroSchema) throws IOException, 
SchemaNotFoundException {
+public AvroReaderWithExplicitSchema(final InputStream in, final 
RecordSchema recordSchema, final Schema avroSchema) throws IOException {
 this.in = in;
 this.recordSchema = recordSchema;
 
-datumReader = new GenericDatumReader(avroSchema);
-decoder = DecoderFactory.get().binaryDecoder(in, null);
+datumReader = new GenericDatumReader<>(avroSchema);
+ByteArrayOutputStream baos = new ByteArrayOutputStream();
+TeeInputStream teeInputStream = new TeeInputStream(in, baos);
+// Try to parse as a DataFileStream, if it works, glue the streams 
back together and delegate calls to the DataFileStream
+try {
+dataFileStream = new DataFileStream<>(teeInputStream, new 
GenericDatumReader<>());
+} catch (IOException ioe) {
+// Carry on, hopefully a raw Avro file
+// Need to be able to re-read the bytes read so far, and the 
InputStream passed in doesn't support reset. Use the TeeInputStream in
+// conjunction with SequenceInputStream to glue the two 
streams back together for future reading
+ByteArrayInputStream bais = new 
ByteArrayInputStream(baos.toByteArray());
+SequenceInputStream sis = new SequenceInputStream(bais, in);
+decoder = DecoderFactory.get().binaryDecoder(sis, null);
+}
+if (dataFileStream != null) {
+// Verify the schemas are the same
+Schema embeddedSchema = dataFileStream.getSchema();
+if (!embeddedSchema.equals(avroSchema)) {
+throw new IOException("Explicit schema does not match 
embedded schema");
--- End diff --

Would it be better to throw SchemaValidationException - makes more sense 
than IOException?


> Allow AvroReader with explicit schema to read files with embedded schema
> 
>
> Key: NIFI-5213
> URL: https://issues.apache.org/jira/browse/NIFI-5213
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Minor
>
> AvroReader allows the choice of schema access strategy from such options as 
> Use Embedded Schema, Use Schema Name, Use Schema Text, etc. If the incoming 
> Avro files will have embedded schemas, then Use Embedded Schema is best 
> practice for the Avro Reader. However it is not intuitive that if the same 
> schema that is embedded in the file is specified by name (using a schema 
> registry) or explicitly via Schema Text, that errors can occur. This has been 
> noticed in QueryRecord for example, and the error is also not intuitive or 
> descriptive (it is often an ArrayIndexOutOfBoundsException).
>

[GitHub] nifi pull request #2718: NIFI-5213: Allow AvroReader to process files w embe...

2018-05-18 Thread bdesert

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

https://github.com/apache/nifi/pull/2718#discussion_r189422180
  
--- Diff: 
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/java/org/apache/nifi/avro/AvroReaderWithExplicitSchema.java
 ---
@@ -17,33 +17,61 @@
 
 package org.apache.nifi.avro;
 
+import java.io.ByteArrayInputStream;
+import java.io.ByteArrayOutputStream;
 import java.io.EOFException;
 import java.io.IOException;
 import java.io.InputStream;
+import java.io.SequenceInputStream;
 
 import org.apache.avro.Schema;
+import org.apache.avro.file.DataFileStream;
 import org.apache.avro.generic.GenericDatumReader;
 import org.apache.avro.generic.GenericRecord;
 import org.apache.avro.io.BinaryDecoder;
 import org.apache.avro.io.DatumReader;
 import org.apache.avro.io.DecoderFactory;
-import org.apache.nifi.schema.access.SchemaNotFoundException;
+import org.apache.commons.io.input.TeeInputStream;
 import org.apache.nifi.serialization.MalformedRecordException;
 import org.apache.nifi.serialization.record.RecordSchema;
 
 public class AvroReaderWithExplicitSchema extends AvroRecordReader {
 private final InputStream in;
 private final RecordSchema recordSchema;
 private final DatumReader datumReader;
-private final BinaryDecoder decoder;
+private BinaryDecoder decoder;
 private GenericRecord genericRecord;
+private DataFileStream dataFileStream;
 
-public AvroReaderWithExplicitSchema(final InputStream in, final 
RecordSchema recordSchema, final Schema avroSchema) throws IOException, 
SchemaNotFoundException {
+public AvroReaderWithExplicitSchema(final InputStream in, final 
RecordSchema recordSchema, final Schema avroSchema) throws IOException {
 this.in = in;
 this.recordSchema = recordSchema;
 
-datumReader = new GenericDatumReader(avroSchema);
-decoder = DecoderFactory.get().binaryDecoder(in, null);
+datumReader = new GenericDatumReader<>(avroSchema);
+ByteArrayOutputStream baos = new ByteArrayOutputStream();
+TeeInputStream teeInputStream = new TeeInputStream(in, baos);
+// Try to parse as a DataFileStream, if it works, glue the streams 
back together and delegate calls to the DataFileStream
+try {
+dataFileStream = new DataFileStream<>(teeInputStream, new 
GenericDatumReader<>());
+} catch (IOException ioe) {
+// Carry on, hopefully a raw Avro file
+// Need to be able to re-read the bytes read so far, and the 
InputStream passed in doesn't support reset. Use the TeeInputStream in
+// conjunction with SequenceInputStream to glue the two 
streams back together for future reading
+ByteArrayInputStream bais = new 
ByteArrayInputStream(baos.toByteArray());
+SequenceInputStream sis = new SequenceInputStream(bais, in);
+decoder = DecoderFactory.get().binaryDecoder(sis, null);
+}
+if (dataFileStream != null) {
+// Verify the schemas are the same
+Schema embeddedSchema = dataFileStream.getSchema();
+if (!embeddedSchema.equals(avroSchema)) {
+throw new IOException("Explicit schema does not match 
embedded schema");
--- End diff --

Would it be better to throw SchemaValidationException - makes more sense 
than IOException?


---

[jira] [Updated] (NIFI-5206) Provide additional information if user does not exist

2018-05-18 Thread Andy LoPresto (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andy LoPresto updated NIFI-5206:

Summary: Provide additional information if user does not exist  (was: 
Provide additional informatoin if user does not exist)

> Provide additional information if user does not exist
> -
>
> Key: NIFI-5206
> URL: https://issues.apache.org/jira/browse/NIFI-5206
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Affects Versions: 1.6.0
>Reporter: Mark Bean
>Priority: Major
>
> When a user attempts to access a NiFi which the user has not been added as a 
> user, an "Insufficient Permissions" error results. This error should only 
> occur if the user exists but is not in the 'view the user interface' policy. 
> For non-existent users, a customizable message should be displayed. For 
> example, the NiFi Admin could provide a custom message such as who to contact 
> to be added as a user.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4165) Update NiFi FlowFile Repository Toolkit to provide ability to remove FlowFiles whose content is missing

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481380#comment-16481380
 ] 

ASF GitHub Bot commented on NIFI-4165:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2502
  
@markap14 sorry I got distracted from this review. I have revisited it and 
I have some points I'd like to discuss:

* I rebased against `master`, as there have obviously been some changes 
there. These fall into a couple places:
** the version bump to `1.7.0-SNAPSHOT` in the `pom.xml` for both this 
artifact and a dependency
** there have been changes to `FlowFileQueue` which `DummyFlowFileQueue` 
must implement
* I added some logic to `RemoveFlowFilesWithMissingContent` which loads the 
*master key* from the expected `bootstrap.conf` file in order to handle a 
`nifi.properties` file with encrypted configuration values. 
* The other NiFi Toolkit components have a `*.bat`/`*.sh` script which 
allows them to be run. This provides a couple features:
** named command-line arguments as opposed to positional arguments
** Setting up `$JAVA_HOME` and the classpath rather than calling `java` 
directly on the command-line
* The `jar-with-dependencies` in `maven-assembly-plugin` only seems to run 
when you use `mvn clean compile assembly:single` rather than being tied to the 
`install` phase via a profile (see [Stack 
Overflow](https://stackoverflow.com/a/574650/70465)). Please let me know if I'm 
missing something here

I ran the scenario you suggested by generating some flowfiles into a queue 
and then removing the `content_repository` directory contents. When I did that, 
I got this message:

```

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo 
(pr2502) alopresto
 149s @ 17:17:25 $ cd target/

hw12203:...ers/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo/target
 (pr2502) alopresto
 0s @ 17:17:31 $ java -cp 
nifi-toolkit-flowfile-repo-1.7.0-SNAPSHOT-jar-with-dependencies.jar:../../nifi-toolkit-assembly/target/nifi-toolkit-1.7.0-SNAPSHOT-bin/nifi-toolkit-1.7.0-SNAPSHOT/lib/slf4j-api-1.7.25.jar
 org.apache.nifi.toolkit.repos.flowfile.RemoveFlowFilesWithMissingContent 
~/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/conf/nifi.properties
 
~/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/flowfile_repository/
17:17:35.865 [main] INFO org.apache.nifi.properties.NiFiPropertiesLoader - 
Loaded 148 properties from 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/conf/nifi.properties
17:17:35.872 [main] DEBUG 
org.apache.nifi.properties.ProtectedNiFiProperties - Loaded 148 properties 
(including 0 protection schemes) into ProtectedNiFiProperties
17:17:35.872 [main] DEBUG 
org.apache.nifi.properties.ProtectedNiFiProperties - No protected properties
Cannot find or cannot read ./content_repository or it is not a directory

hw12203:...ers/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo/target
 (pr2502) alopresto
 0s @ 17:17:36 $
```

The directory definitely exists:

```

hw12203:...space/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT
 (pr2502) alopresto
 0s @ 17:17:48 $ ll
total 416
drwxr-xr-x   17 alopresto  staff   578B May 10 16:40 ./
drwxr-xr-x3 alopresto  staff   102B May 10 10:20 ../
-rw-r--r--1 alopresto  staff   119K Mar 13 17:25 LICENSE
-rw-r--r--1 alopresto  staff80K May 10 09:23 NOTICE
-rw-r--r--1 alopresto  staff   4.4K Dec 13 15:56 README
drwxr-xr-x8 alopresto  staff   272B May 10 10:20 bin/
drwxr-xr-x   12 alopresto  staff   408B May 18 16:51 conf/
drwxr-xr-x2 alopresto  staff68B May 18 16:51 content_repository/
drwxr-xr-x6 alopresto  staff   204B May 18 16:50 database_repository/
drwxr-xr-x3 alopresto  staff   102B May 10 10:20 docs/
drwxr-xr-x5 alopresto  staff   170B May 18 16:52 flowfile_repository/
drwxr-xr-x  113 alopresto  staff   3.8K May 10 10:20 lib/
drwxr-xr-x   10 alopresto  staff   340B May 18 17:00 logs/
drwxr-xr-x9 alopresto  staff   306B May 18 16:51 provenance_repository/
drwxr-xr-x4 alopresto  staff   136B May 18 16:49 run/
drwxr-xr-x3 alopresto  staff   102B May 10 16:40 state/
drwxr-xr-x5 alopresto  staff   170B May 18 16:50 work/

hw12203:...space/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT
 (pr2502) alopresto
 0s @ 17:19:35 $ ll content_repository/
total 0
drwxr-xr-x   2 alopresto  staff68B May 18 16:51 ./
drwxr-xr-x  17 alopresto  staff   578B May 10 16:40 ../
```

I believe this is because in the default `nifi.properties` file, the 
content

[GitHub] nifi issue #2502: NIFI-4165: Added RemoveFlowFilesWithMissingContent.java an...

2018-05-18 Thread alopresto

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/2502
  
@markap14 sorry I got distracted from this review. I have revisited it and 
I have some points I'd like to discuss:

* I rebased against `master`, as there have obviously been some changes 
there. These fall into a couple places:
** the version bump to `1.7.0-SNAPSHOT` in the `pom.xml` for both this 
artifact and a dependency
** there have been changes to `FlowFileQueue` which `DummyFlowFileQueue` 
must implement
* I added some logic to `RemoveFlowFilesWithMissingContent` which loads the 
*master key* from the expected `bootstrap.conf` file in order to handle a 
`nifi.properties` file with encrypted configuration values. 
* The other NiFi Toolkit components have a `*.bat`/`*.sh` script which 
allows them to be run. This provides a couple features:
** named command-line arguments as opposed to positional arguments
** Setting up `$JAVA_HOME` and the classpath rather than calling `java` 
directly on the command-line
* The `jar-with-dependencies` in `maven-assembly-plugin` only seems to run 
when you use `mvn clean compile assembly:single` rather than being tied to the 
`install` phase via a profile (see [Stack 
Overflow](https://stackoverflow.com/a/574650/70465)). Please let me know if I'm 
missing something here

I ran the scenario you suggested by generating some flowfiles into a queue 
and then removing the `content_repository` directory contents. When I did that, 
I got this message:

```

hw12203:/Users/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo 
(pr2502) alopresto
ð 149s @ 17:17:25 $ cd target/

hw12203:...ers/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo/target
 (pr2502) alopresto
ð 0s @ 17:17:31 $ java -cp 
nifi-toolkit-flowfile-repo-1.7.0-SNAPSHOT-jar-with-dependencies.jar:../../nifi-toolkit-assembly/target/nifi-toolkit-1.7.0-SNAPSHOT-bin/nifi-toolkit-1.7.0-SNAPSHOT/lib/slf4j-api-1.7.25.jar
 org.apache.nifi.toolkit.repos.flowfile.RemoveFlowFilesWithMissingContent 
~/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/conf/nifi.properties
 
~/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/flowfile_repository/
17:17:35.865 [main] INFO org.apache.nifi.properties.NiFiPropertiesLoader - 
Loaded 148 properties from 
/Users/alopresto/Workspace/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT/conf/nifi.properties
17:17:35.872 [main] DEBUG 
org.apache.nifi.properties.ProtectedNiFiProperties - Loaded 148 properties 
(including 0 protection schemes) into ProtectedNiFiProperties
17:17:35.872 [main] DEBUG 
org.apache.nifi.properties.ProtectedNiFiProperties - No protected properties
Cannot find or cannot read ./content_repository or it is not a directory

hw12203:...ers/alopresto/Workspace/nifi/nifi-toolkit/nifi-toolkit-flowfile-repo/target
 (pr2502) alopresto
ð 0s @ 17:17:36 $
```

The directory definitely exists:

```

hw12203:...space/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT
 (pr2502) alopresto
ð 0s @ 17:17:48 $ ll
total 416
drwxr-xr-x   17 alopresto  staff   578B May 10 16:40 ./
drwxr-xr-x3 alopresto  staff   102B May 10 10:20 ../
-rw-r--r--1 alopresto  staff   119K Mar 13 17:25 LICENSE
-rw-r--r--1 alopresto  staff80K May 10 09:23 NOTICE
-rw-r--r--1 alopresto  staff   4.4K Dec 13 15:56 README
drwxr-xr-x8 alopresto  staff   272B May 10 10:20 bin/
drwxr-xr-x   12 alopresto  staff   408B May 18 16:51 conf/
drwxr-xr-x2 alopresto  staff68B May 18 16:51 content_repository/
drwxr-xr-x6 alopresto  staff   204B May 18 16:50 database_repository/
drwxr-xr-x3 alopresto  staff   102B May 10 10:20 docs/
drwxr-xr-x5 alopresto  staff   170B May 18 16:52 flowfile_repository/
drwxr-xr-x  113 alopresto  staff   3.8K May 10 10:20 lib/
drwxr-xr-x   10 alopresto  staff   340B May 18 17:00 logs/
drwxr-xr-x9 alopresto  staff   306B May 18 16:51 provenance_repository/
drwxr-xr-x4 alopresto  staff   136B May 18 16:49 run/
drwxr-xr-x3 alopresto  staff   102B May 10 16:40 state/
drwxr-xr-x5 alopresto  staff   170B May 18 16:50 work/

hw12203:...space/nifi/nifi-assembly/target/nifi-1.7.0-SNAPSHOT-bin/nifi-1.7.0-SNAPSHOT
 (pr2502) alopresto
ð 0s @ 17:19:35 $ ll content_repository/
total 0
drwxr-xr-x   2 alopresto  staff68B May 18 16:51 ./
drwxr-xr-x  17 alopresto  staff   578B May 10 16:40 ../
```

I believe this is because in the default `nifi.properties` file, the 
content repository is defined as a relative path `./content_repository`, so I 
think there should be code in the tool to resolve this path if it is not 
absolute. 

Let me know what you think about those comments. I pushed

[jira] [Resolved] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread Aldrin Piri (JIRA)


 [ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-472.
---
   Resolution: Done
Fix Version/s: 0.5.0

> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
> Fix For: 0.5.0
>
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481369#comment-16481369
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/315


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
> Fix For: 0.5.0
>
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #315: MINIFICPP-472 Added date formatting EL fu...

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/315


---

[jira] [Commented] (NIFI-5205) NiFi SysAdmin Guide max.appendable.size Default Value

2018-05-18 Thread Andrew Lim (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481328#comment-16481328
 ] 

Andrew Lim commented on NIFI-5205:
--

Hi [~albanes3]

This doc update won't be seen on the website until NiFi 1.7.0 is released.  The 
online docs (https://nifi.apache.org/docs.html) are in sync with the latest 
released version which is currently 1.6.0.

There is a ticket to improve this:  
https://issues.apache.org/jira/browse/NIFI-3513

> NiFi SysAdmin Guide max.appendable.size Default Value
> -
>
> Key: NIFI-5205
> URL: https://issues.apache.org/jira/browse/NIFI-5205
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation  Website
>Affects Versions: 1.6.0
>Reporter: Mike Albanese
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.7.0
>
> Attachments: Screen Shot 2018-05-16 at 3.56.48 PM.png
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> Documentation for nifi.content.claim.max.appendable.size does not match 
> default value of 1 MB in nifi.properties for 1.6.0.
> Keep in mind that I am making the assumption that NiFi defaults to this same 
> value of 1 MB when it starts up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread veteranbv

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

https://github.com/apache/nifi/pull/2715#discussion_r189410920
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/src/main/java/org/apache/nifi/processors/yandex/util/Languages.java
 ---
@@ -25,6 +25,7 @@
 private static final Map languageAbbreviationMap = new 
HashMap<>();
 
 static {
+languageAbbreviationMap.put("", "blank");
--- End diff --

@joewitt I took a little different route by deleting the blank reference in 
this file and updating the validator logic


---

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread veteranbv

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

https://github.com/apache/nifi/pull/2715#discussion_r189410848
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/src/main/java/org/apache/nifi/processors/yandex/YandexTranslate.java
 ---
@@ -211,10 +211,14 @@ public void destroyClient() {
 protected Invocation prepareResource(final String key, final 
List text, final String sourceLanguage, final String destLanguage) {
 Invocation.Builder builder = 
client.target(URL).request(MediaType.APPLICATION_JSON);
 
-final MultivaluedHashMap entity = new MultivaluedHashMap();;
+final MultivaluedHashMap entity = new MultivaluedHashMap();
 entity.put("text", text);
 entity.add("key", key);
-entity.add("lang", sourceLanguage + "-" + destLanguage);
+if (sourceLanguage != "") {
--- End diff --

@joewitt Updated using your recommendations


---

[jira] [Commented] (NIFI-4907) Provenance authorization refactoring

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481244#comment-16481244
 ] 

ASF GitHub Bot commented on NIFI-4907:
--

Github user markobean commented on the issue:

https://github.com/apache/nifi/pull/2703
  
Fixed conflicts with master.
Added NIFI-5207 since it is from the same policy refactor and required 
minimal code change.


> Provenance authorization refactoring
> 
>
> Key: NIFI-4907
> URL: https://issues.apache.org/jira/browse/NIFI-4907
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Affects Versions: 1.5.0
>Reporter: Mark Bean
>Assignee: Mark Bean
>Priority: Major
>
> Currently, the 'view the data' component policy is too tightly coupled with 
> Provenance queries. The 'query provenance' policy should be the only policy 
> required for viewing Provenance query results. Both 'view the component' and 
> 'view the data' policies should be used to refine the appropriate visibility 
> of event details - but not the event itself.
> 1) Component Visibility
> The authorization of Provenance events is inconsistent with the behavior of 
> the graph. For example, if a user does not have 'view the component' policy, 
> the graph shows this component as a "black box" (no details such as name, 
> UUID, etc.) However, when querying Provenance, this component will show up 
> including the Component Type and the Component Name. This is in effect a 
> violation of the policy. These component details should be obscured in the 
> Provenance event displayed if user does not have the appropriate 'view the 
> component' policy.
> 2) Data Visibility
> For a Provenance query, all events should be visible as long as the user 
> performing the query belongs to the 'query provenance' global policy. As 
> mentioned above, some information about the component may be obscured 
> depending on 'view the component' policy, but the event itself should be 
> visible. Additionally, details of the event (clicking the View Details "i" 
> icon) should only be accessible if the user belongs to the 'view the data' 
> policy for the affected component. If the user is not in the appropriate 
> 'view the data' policy, a popup warning should be displayed indicating the 
> reason details are not visible with more specific detail than the current 
> "Contact the system administrator".
> 3) Lineage Graphs
> As with the Provenance table view recommendation above, the lineage graph 
> should display all events. Currently, if the lineage graph includes an event 
> belonging to a component which the user does not have 'view the data', it is 
> shown on the graph as "UNKNOWN". As with Data Visibility mentioned above, the 
> graph should indicate the event type as long as the user is in the 'view the 
> component'. Subsequent "View Details" on the event should only be visible if 
> the user is in the 'view the data' policy.
> In summary, for Provenance query results and lineage graphs, all events 
> should be shown. Component Name and Component Type information should be 
> conditionally visible depending on the corresponding component policy 'view 
> the component' policy. Event details including Provenance event type and 
> FlowFile information should be conditionally available depending on the 
> corresponding component policy 'view the data'. Inability to display event 
> details should provide feedback to the user indicating the reason.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2703: NIFI-4907: add 'view provenance' component policy

2018-05-18 Thread markobean

Github user markobean commented on the issue:

https://github.com/apache/nifi/pull/2703
  
Fixed conflicts with master.
Added NIFI-5207 since it is from the same policy refactor and required 
minimal code change.


---

[jira] [Commented] (NIFI-5186) Update UI to account for asynchronous validation

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481191#comment-16481191
 ] 

ASF GitHub Bot commented on NIFI-5186:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2722
  
@markap14 @mcgilman in looking at this from a user point of view a couple 
thoughts:

When validating things which are slow and things which are fast it appears 
fast things can be bottlenecked behind fast things.  This makes sense but can 
we do better?  For instance I have a DebugFlow with a 10 sec validation cycle 
and an UpdateAttribute processor.  it took 10 secs or more for UpdateAttribute 
to come back as valid presumably because it was waiting for the next validation 
cycle and then perhaps it had to wait behind the slow DebugFlow proc.
Question: Do we have 1 thread or more than one thread for validation?  Or 
is it just a task we fire off in the typical timer task thread pool?
Question: Can we force a validation cycle whenever some component is change 
or more to the point could we initiate 'that component' which changed to be 
validated.




> Update UI to account for asynchronous validation
> 
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation 
> introduces a new state VALIDATING. This VALIDATING state will be entered 
> following any modifications (create, update) to the component (Processor, 
> Controller Service, Reporting Task). All component validation is done in the 
> background on a recurring interval. When obtaining the current state, we will 
> return the last known state unless it is VALIDATING as a result of a 
> modification. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2722: NIFI-5186: Updating UI to support asynchronous validation

2018-05-18 Thread joewitt

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2722
  
@markap14 @mcgilman in looking at this from a user point of view a couple 
thoughts:

When validating things which are slow and things which are fast it appears 
fast things can be bottlenecked behind fast things.  This makes sense but can 
we do better?  For instance I have a DebugFlow with a 10 sec validation cycle 
and an UpdateAttribute processor.  it took 10 secs or more for UpdateAttribute 
to come back as valid presumably because it was waiting for the next validation 
cycle and then perhaps it had to wait behind the slow DebugFlow proc.
Question: Do we have 1 thread or more than one thread for validation?  Or 
is it just a task we fire off in the typical timer task thread pool?
Question: Can we force a validation cycle whenever some component is change 
or more to the point could we initiate 'that component' which changed to be 
validated.




---

[jira] [Commented] (NIFI-5186) Update UI to account for asynchronous validation

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481169#comment-16481169
 ] 

ASF GitHub Bot commented on NIFI-5186:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2722
  
@mcgilman @markap14 this test finding is related to Mark's preceding PR for 
this most likely but 

`[ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 
16.555 s <<< FAILURE! - in 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle
[ERROR] 
validateProcessorCanBeStoppedWhenOnTriggerThrowsException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
  Time elapsed: 3.11 s  <<< FAILURE!
java.lang.AssertionError
at 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.assertCondition(TestProcessorLifecycle.java:116)
at 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException(TestProcessorLifecycle.java:496)

`

Otherwise, I'm doing some functional testing now and obviously 
contrib-check is good.  This is really cool and will greatly aid flow 
performance for large scale flows or user code in validation that doesn't 
behave nicely.


> Update UI to account for asynchronous validation
> 
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation 
> introduces a new state VALIDATING. This VALIDATING state will be entered 
> following any modifications (create, update) to the component (Processor, 
> Controller Service, Reporting Task). All component validation is done in the 
> background on a recurring interval. When obtaining the current state, we will 
> return the last known state unless it is VALIDATING as a result of a 
> modification. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2722: NIFI-5186: Updating UI to support asynchronous validation

2018-05-18 Thread joewitt

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2722
  
@mcgilman @markap14 this test finding is related to Mark's preceding PR for 
this most likely but 

`[ERROR] Tests run: 15, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 
16.555 s <<< FAILURE! - in 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle
[ERROR] 
validateProcessorCanBeStoppedWhenOnTriggerThrowsException(org.apache.nifi.controller.scheduling.TestProcessorLifecycle)
  Time elapsed: 3.11 s  <<< FAILURE!
java.lang.AssertionError
at 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.assertCondition(TestProcessorLifecycle.java:116)
at 
org.apache.nifi.controller.scheduling.TestProcessorLifecycle.validateProcessorCanBeStoppedWhenOnTriggerThrowsException(TestProcessorLifecycle.java:496)

`

Otherwise, I'm doing some functional testing now and obviously 
contrib-check is good.  This is really cool and will greatly aid flow 
performance for large scale flows or user code in validation that doesn't 
behave nicely.


---

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread joewitt

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

https://github.com/apache/nifi/pull/2715#discussion_r189384435
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/src/main/java/org/apache/nifi/processors/yandex/util/Languages.java
 ---
@@ -25,6 +25,7 @@
 private static final Map languageAbbreviationMap = new 
HashMap<>();
 
 static {
+languageAbbreviationMap.put("", "blank");
--- End diff --

perhaps this should be 'auto-detect' and 'auto-detect'.  In your previous 
logic looking for "" it could look for equals("auto-detect") or some constant 
string value


---

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread joewitt

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

https://github.com/apache/nifi/pull/2715#discussion_r189384008
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/src/main/java/org/apache/nifi/processors/yandex/YandexTranslate.java
 ---
@@ -211,10 +211,14 @@ public void destroyClient() {
 protected Invocation prepareResource(final String key, final 
List text, final String sourceLanguage, final String destLanguage) {
 Invocation.Builder builder = 
client.target(URL).request(MediaType.APPLICATION_JSON);
 
-final MultivaluedHashMap entity = new MultivaluedHashMap();;
+final MultivaluedHashMap entity = new MultivaluedHashMap();
 entity.put("text", text);
 entity.add("key", key);
-entity.add("lang", sourceLanguage + "-" + destLanguage);
+if (sourceLanguage != "") {
--- End diff --

@veteranbv consider using StringUtils.isBlank(sourceLanguage) instead of 
the empty string equality check


---

[jira] [Resolved] (MINIFICPP-403) Enable tagging of flowfiles with flow metadata information in C++

2018-05-18 Thread Aldrin Piri (JIRA)


 [ 
https://issues.apache.org/jira/browse/MINIFICPP-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-403.
---
   Resolution: Fixed
 Assignee: marco polo  (was: bqiu)
Fix Version/s: (was: 1.0.0)
   0.5.0

> Enable tagging of flowfiles with flow metadata information in C++
> -
>
> Key: MINIFICPP-403
> URL: https://issues.apache.org/jira/browse/MINIFICPP-403
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: bqiu
>Assignee: marco polo
>Priority: Minor
> Fix For: 0.5.0
>
>
> Provide framework level support to tag flowfiles with metadata about the flow 
> that created them.
> Design proposal
> Right now, MiNiFi support core attributes like 
> // FlowFile Attribute
> enum FlowAttribute {
>  // The flowfile's path indicates the relative directory to which a FlowFile 
> belongs and does not contain the filename
>  PATH = 0,
>  // The flowfile's absolute path indicates the absolute directory to which a 
> FlowFile belongs and does not contain the filename
>  ABSOLUTE_PATH,
>  // The filename of the FlowFile. The filename should not contain any 
> directory structure.
>  FILENAME,
>  // A unique UUID assigned to this FlowFile.
>  UUID,
>  // A numeric value indicating the FlowFile priority
>  priority,
>  // The MIME Type of this FlowFile
>  MIME_TYPE,
>  // Specifies the reason that a FlowFile is being discarded
>  DISCARD_REASON,
>  // Indicates an identifier other than the FlowFile's UUID that is known to 
> refer to this FlowFile.
>  ALTERNATE_IDENTIFIER,
>  MAX_FLOW_ATTRIBUTES
> };
> So one approach is in the flow YAML file, specific the list of core flow 
> attributes along with the processors that inject/import/create the flow files.
> When flow was created/imported/injected by this processor, we can apply these 
> core attributes to the new flow.
> Also user can define their own core attributes template and EL for populate 
> value for these core attributes, for example protocol, TTL, record route 
> (expected route), key, version, etc.
> In current implementation, FILENAME, PATH and UUID are required attributes 
> when flow was created, others are optional
> // Populate the default attributes
> addKeyedAttribute(FILENAME,
> std::to_string(getTimeNano()));
> addKeyedAttribute(PATH, DEFAULT_FLOWFILE_PATH);
> addKeyedAttribute(UUID,
> getUUIDStr())
> So if user specify the optional meta flow info section for the processor with 
> the key/value pairs as above, MiNiFI will add these key attributes to the 
> flow when flow was created by this processor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-403) Enable tagging of flowfiles with flow metadata information in C++

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481144#comment-16481144
 ] 

ASF GitHub Bot commented on MINIFICPP-403:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/313


> Enable tagging of flowfiles with flow metadata information in C++
> -
>
> Key: MINIFICPP-403
> URL: https://issues.apache.org/jira/browse/MINIFICPP-403
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: bqiu
>Assignee: bqiu
>Priority: Minor
> Fix For: 1.0.0
>
>
> Provide framework level support to tag flowfiles with metadata about the flow 
> that created them.
> Design proposal
> Right now, MiNiFi support core attributes like 
> // FlowFile Attribute
> enum FlowAttribute {
>  // The flowfile's path indicates the relative directory to which a FlowFile 
> belongs and does not contain the filename
>  PATH = 0,
>  // The flowfile's absolute path indicates the absolute directory to which a 
> FlowFile belongs and does not contain the filename
>  ABSOLUTE_PATH,
>  // The filename of the FlowFile. The filename should not contain any 
> directory structure.
>  FILENAME,
>  // A unique UUID assigned to this FlowFile.
>  UUID,
>  // A numeric value indicating the FlowFile priority
>  priority,
>  // The MIME Type of this FlowFile
>  MIME_TYPE,
>  // Specifies the reason that a FlowFile is being discarded
>  DISCARD_REASON,
>  // Indicates an identifier other than the FlowFile's UUID that is known to 
> refer to this FlowFile.
>  ALTERNATE_IDENTIFIER,
>  MAX_FLOW_ATTRIBUTES
> };
> So one approach is in the flow YAML file, specific the list of core flow 
> attributes along with the processors that inject/import/create the flow files.
> When flow was created/imported/injected by this processor, we can apply these 
> core attributes to the new flow.
> Also user can define their own core attributes template and EL for populate 
> value for these core attributes, for example protocol, TTL, record route 
> (expected route), key, version, etc.
> In current implementation, FILENAME, PATH and UUID are required attributes 
> when flow was created, others are optional
> // Populate the default attributes
> addKeyedAttribute(FILENAME,
> std::to_string(getTimeNano()));
> addKeyedAttribute(PATH, DEFAULT_FLOWFILE_PATH);
> addKeyedAttribute(UUID,
> getUUIDStr())
> So if user specify the optional meta flow info section for the processor with 
> the key/value pairs as above, MiNiFI will add these key attributes to the 
> flow when flow was created by this processor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-403) Enable tagging of flowfiles with flow metadata information in C++

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481143#comment-16481143
 ] 

ASF GitHub Bot commented on MINIFICPP-403:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/331


> Enable tagging of flowfiles with flow metadata information in C++
> -
>
> Key: MINIFICPP-403
> URL: https://issues.apache.org/jira/browse/MINIFICPP-403
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Affects Versions: 1.0.0
>Reporter: bqiu
>Assignee: bqiu
>Priority: Minor
> Fix For: 1.0.0
>
>
> Provide framework level support to tag flowfiles with metadata about the flow 
> that created them.
> Design proposal
> Right now, MiNiFi support core attributes like 
> // FlowFile Attribute
> enum FlowAttribute {
>  // The flowfile's path indicates the relative directory to which a FlowFile 
> belongs and does not contain the filename
>  PATH = 0,
>  // The flowfile's absolute path indicates the absolute directory to which a 
> FlowFile belongs and does not contain the filename
>  ABSOLUTE_PATH,
>  // The filename of the FlowFile. The filename should not contain any 
> directory structure.
>  FILENAME,
>  // A unique UUID assigned to this FlowFile.
>  UUID,
>  // A numeric value indicating the FlowFile priority
>  priority,
>  // The MIME Type of this FlowFile
>  MIME_TYPE,
>  // Specifies the reason that a FlowFile is being discarded
>  DISCARD_REASON,
>  // Indicates an identifier other than the FlowFile's UUID that is known to 
> refer to this FlowFile.
>  ALTERNATE_IDENTIFIER,
>  MAX_FLOW_ATTRIBUTES
> };
> So one approach is in the flow YAML file, specific the list of core flow 
> attributes along with the processors that inject/import/create the flow files.
> When flow was created/imported/injected by this processor, we can apply these 
> core attributes to the new flow.
> Also user can define their own core attributes template and EL for populate 
> value for these core attributes, for example protocol, TTL, record route 
> (expected route), key, version, etc.
> In current implementation, FILENAME, PATH and UUID are required attributes 
> when flow was created, others are optional
> // Populate the default attributes
> addKeyedAttribute(FILENAME,
> std::to_string(getTimeNano()));
> addKeyedAttribute(PATH, DEFAULT_FLOWFILE_PATH);
> addKeyedAttribute(UUID,
> getUUIDStr())
> So if user specify the optional meta flow info section for the processor with 
> the key/value pairs as above, MiNiFI will add these key attributes to the 
> flow when flow was created by this processor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #313: MINIFICPP-403: Add version into flow attr...

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/313


---

[GitHub] nifi-minifi-cpp pull request #331: MINIFICPP-403: Update connectables so tha...

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/331


---

[GitHub] nifi-minifi-cpp pull request #295: MINFICPP-403: Flow Meta tagging

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/295


---

[jira] [Commented] (NIFI-5205) NiFi SysAdmin Guide max.appendable.size Default Value

2018-05-18 Thread Mike Albanese (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481142#comment-16481142
 ] 

Mike Albanese commented on NIFI-5205:
-

Seeing the issue is marked as 'Resolved' yet the website has not been updated. 
I take it this is because changes are only deployed to the web server so often. 
Any confirmation on when these changes will be reflected would be great. Thanks 
again for tackling this :)

> NiFi SysAdmin Guide max.appendable.size Default Value
> -
>
> Key: NIFI-5205
> URL: https://issues.apache.org/jira/browse/NIFI-5205
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Documentation  Website
>Affects Versions: 1.6.0
>Reporter: Mike Albanese
>Assignee: Andrew Lim
>Priority: Minor
> Fix For: 1.7.0
>
> Attachments: Screen Shot 2018-05-16 at 3.56.48 PM.png
>
>   Original Estimate: 1m
>  Remaining Estimate: 1m
>
> Documentation for nifi.content.claim.max.appendable.size does not match 
> default value of 1 MB in nifi.properties for 1.6.0.
> Keep in mind that I am making the assumption that NiFi defaults to this same 
> value of 1 MB when it starts up. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481140#comment-16481140
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson ah, fair point.  otherwise looks good to go.  thanks for the 
fixes!


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread apiri

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson ah, fair point.  otherwise looks good to go.  thanks for the 
fixes!


---

[jira] [Updated] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread Matt Burgess (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-5217:
---
Resolution: Fixed
Status: Resolved  (was: Patch Available)

> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.7.0
>
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481119#comment-16481119
 ] 

ASF GitHub Bot commented on NIFI-5217:
--

Github user asfgit closed the pull request at:

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


> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.7.0
>
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread ASF subversion and git services (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481118#comment-16481118
 ] 

ASF subversion and git services commented on NIFI-5217:
---

Commit d79216d6b08a842dc0c5f6b847429aae87fb5561 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d79216d ]

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser

Signed-off-by: Matthew Burgess 

This closes #2720


> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.7.0
>
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread Matt Burgess (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-5217:
---
Fix Version/s: 1.7.0

> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
> Fix For: 1.7.0
>
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2720: NIFI-5217: Allow non-nullable fields to be added to MockRe...

2018-05-18 Thread mattyb149

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/2720
  
The Travis failure was on one build because of a port conflict, the others 
pass (with contrib-check). Merging to master, thanks!


---

[GitHub] nifi pull request #2720: NIFI-5217: Allow non-nullable fields to be added to...

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

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


---

[jira] [Commented] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481117#comment-16481117
 ] 

ASF GitHub Bot commented on NIFI-5217:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/2720
  
The Travis failure was on one build because of a port conflict, the others 
pass (with contrib-check). Merging to master, thanks!


> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481109#comment-16481109
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri I think that might be more of a container issue vs. a build issue. 
The date lib interacts with the system zoneinfo db, so I think trouble with 
that is why it is raising a runtime exception during the test.


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread achristianson

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri I think that might be more of a container issue vs. a build issue. 
The date lib interacts with the system zoneinfo db, so I think trouble with 
that is why it is raising a runtime exception during the test.


---

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481107#comment-16481107
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
Looks like we have build issues with that change.  I attempted building in 
an Ubuntu 17.10 container:

```
ExpressionLanguageTests is a Catch v1.6.1 host application.
Run with -? for options


---
Parse Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1216

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1221:
 FAILED:
  REQUIRE( "139884120" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Format Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1224

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1229:
 FAILED:
  REQUIRE( "03-14-2014" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Reformat Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1232

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1237:
 FAILED:
  REQUIRE( "03-13-2014" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Now Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1240

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1249:
 FAILED:
  REQUIRE( (lt.tm_year + 1900) == expr({flow_file_a}).asUnsignedLong() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo

```


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread apiri

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
Looks like we have build issues with that change.  I attempted building in 
an Ubuntu 17.10 container:

```
ExpressionLanguageTests is a Catch v1.6.1 host application.
Run with -? for options


---
Parse Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1216

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1221:
 FAILED:
  REQUIRE( "139884120" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Format Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1224

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1229:
 FAILED:
  REQUIRE( "03-14-2014" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Reformat Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1232

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1237:
 FAILED:
  REQUIRE( "03-13-2014" == expr({flow_file_a}).asString() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo



---
Now Date

---

/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1240

...


/root/nifi-minifi-cpp/libminifi/test/expression-language-tests/ExpressionLanguageTests.cpp:1249:
 FAILED:
  REQUIRE( (lt.tm_year + 1900) == expr({flow_file_a}).asUnsignedLong() )
due to unexpected exception with message:
  discover_tz_dir failed to find zoneinfo

```


---

[jira] [Commented] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481090#comment-16481090
 ] 

ASF GitHub Bot commented on NIFI-5217:
--

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2720
  
+1 @mattyb149 please feel free to merge if contrib-check clears


> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2720: NIFI-5217: Allow non-nullable fields to be added to MockRe...

2018-05-18 Thread joewitt

Github user joewitt commented on the issue:

https://github.com/apache/nifi/pull/2720
  
+1 @mattyb149 please feel free to merge if contrib-check clears


---

[jira] [Commented] (NIFI-5186) Update UI to account for asynchronous validation

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481054#comment-16481054
 ] 

ASF GitHub Bot commented on NIFI-5186:
--

GitHub user mcgilman opened a pull request:

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

NIFI-5186: Updating UI to support asynchronous validation

NIFI-5186:
- Updating UI to support showing when a component is validating.
- Code clean up.

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

$ git pull https://github.com/mcgilman/nifi NIFI-5186

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

https://github.com/apache/nifi/pull/2722.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 #2722


commit b4d3a48ca4b7081c272ca01d386ed7962e66f6ee
Author: Matt Gilman 
Date:   2018-05-18T18:56:10Z

NIFI-5186:
- Updating UI to support showing when a component is validating.




> Update UI to account for asynchronous validation
> 
>
> Key: NIFI-5186
> URL: https://issues.apache.org/jira/browse/NIFI-5186
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Matt Gilman
>Priority: Blocker
> Fix For: 1.7.0
>
>
> This Jira is a follow up to NIFI-950. The new asynchronous validation 
> introduces a new state VALIDATING. This VALIDATING state will be entered 
> following any modifications (create, update) to the component (Processor, 
> Controller Service, Reporting Task). All component validation is done in the 
> background on a recurring interval. When obtaining the current state, we will 
> return the last known state unless it is VALIDATING as a result of a 
> modification. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2722: NIFI-5186: Updating UI to support asynchronous vali...

2018-05-18 Thread mcgilman

GitHub user mcgilman opened a pull request:

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

NIFI-5186: Updating UI to support asynchronous validation

NIFI-5186:
- Updating UI to support showing when a component is validating.
- Code clean up.

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

$ git pull https://github.com/mcgilman/nifi NIFI-5186

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

https://github.com/apache/nifi/pull/2722.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 #2722


commit b4d3a48ca4b7081c272ca01d386ed7962e66f6ee
Author: Matt Gilman 
Date:   2018-05-18T18:56:10Z

NIFI-5186:
- Updating UI to support showing when a component is validating.




---

[jira] [Commented] (NIFI-5215) Upgrade AngularJS to v1.7.0

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481050#comment-16481050
 ] 

ASF GitHub Bot commented on NIFI-5215:
--

GitHub user scottyaslan opened a pull request:

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

[NIFI-5215] Upgrade AngularJS to v1.7.0. Also, adding package-lock.js…

…on to source control

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/scottyaslan/nifi NIFI-5215

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

https://github.com/apache/nifi/pull/2721.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 #2721


commit de2705386aa1fb7f4d98b3a4fd05606a117238c9
Author: Scott Aslan 
Date:   2018-05-18T18:50:23Z

[NIFI-5215] Upgrade AngularJS to v1.7.0. Also, adding package-lock.json to 
source control




> Upgrade AngularJS to v1.7.0
> ---
>
> Key: NIFI-5215
> URL: https://issues.apache.org/jira/browse/NIFI-5215
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
> Fix For: 1.7.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-5215) Upgrade AngularJS to v1.7.0

2018-05-18 Thread Scott Aslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan updated NIFI-5215:
--
Status: Patch Available  (was: In Progress)

> Upgrade AngularJS to v1.7.0
> ---
>
> Key: NIFI-5215
> URL: https://issues.apache.org/jira/browse/NIFI-5215
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-5215) Upgrade AngularJS to v1.7.0

2018-05-18 Thread Scott Aslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan updated NIFI-5215:
--
Fix Version/s: 1.7.0

> Upgrade AngularJS to v1.7.0
> ---
>
> Key: NIFI-5215
> URL: https://issues.apache.org/jira/browse/NIFI-5215
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
> Fix For: 1.7.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2721: [NIFI-5215] Upgrade AngularJS to v1.7.0. Also, addi...

2018-05-18 Thread scottyaslan

GitHub user scottyaslan opened a pull request:

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

[NIFI-5215] Upgrade AngularJS to v1.7.0. Also, adding package-lock.jsâ¦

â¦on to source control

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/scottyaslan/nifi NIFI-5215

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

https://github.com/apache/nifi/pull/2721.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 #2721


commit de2705386aa1fb7f4d98b3a4fd05606a117238c9
Author: Scott Aslan 
Date:   2018-05-18T18:50:23Z

[NIFI-5215] Upgrade AngularJS to v1.7.0. Also, adding package-lock.json to 
source control




---

[jira] [Updated] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread Matt Burgess (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess updated NIFI-5217:
---
Status: Patch Available  (was: In Progress)

> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481044#comment-16481044
 ] 

ASF GitHub Bot commented on NIFI-5217:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/mattyb149/nifi NIFI-5217

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

https://github.com/apache/nifi/pull/2720.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 #2720


commit d0ce41f202c63ff4f108abcd050506c525098568
Author: Matthew Burgess 
Date:   2018-05-18T18:47:57Z

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser




> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2720: NIFI-5217: Allow non-nullable fields to be added to...

2018-05-18 Thread mattyb149

GitHub user mattyb149 opened a pull request:

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

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser

Thank you for submitting a contribution to Apache NiFi.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [x] Does your PR title start with NIFI- where  is the JIRA number 
you are trying to resolve? Pay particular attention to the hyphen "-" character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to 
.name (programmatic access) for each of the new properties?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/mattyb149/nifi NIFI-5217

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

https://github.com/apache/nifi/pull/2720.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 #2720


commit d0ce41f202c63ff4f108abcd050506c525098568
Author: Matthew Burgess 
Date:   2018-05-18T18:47:57Z

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser




---

[jira] [Assigned] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread Matt Burgess (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Burgess reassigned NIFI-5217:
--

Assignee: Matt Burgess

> Allow MockRecordParser to add non-nullable fields
> -
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Extensions
>Reporter: Matt Burgess
>Assignee: Matt Burgess
>Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
> but it does not have a parameter to set whether the field is nullable or not. 
> Thus it creates a new RecordField without the nullable parameter, in which 
> case it defaults to "true". This prevents tests from adding a non-nullable 
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
> parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-5217) Allow MockRecordParser to add non-nullable fields

2018-05-18 Thread Matt Burgess (JIRA)

Matt Burgess created NIFI-5217:
--

 Summary: Allow MockRecordParser to add non-nullable fields
 Key: NIFI-5217
 URL: https://issues.apache.org/jira/browse/NIFI-5217
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Extensions
Reporter: Matt Burgess


MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method, 
but it does not have a parameter to set whether the field is nullable or not. 
Thus it creates a new RecordField without the nullable parameter, in which case 
it defaults to "true". This prevents tests from adding a non-nullable field.

This Jira proposes to overload addSchemaField() with a boolean "isNullable" 
parameter that will be passed along to the RecordField constructor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (MINIFICPP-369) Implement multiple attribute expressions in expression language

2018-05-18 Thread Aldrin Piri (JIRA)


 [ 
https://issues.apache.org/jira/browse/MINIFICPP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Aldrin Piri resolved MINIFICPP-369.
---
   Resolution: Fixed
Fix Version/s: 0.5.0

> Implement multiple attribute expressions in expression language
> ---
>
> Key: MINIFICPP-369
> URL: https://issues.apache.org/jira/browse/MINIFICPP-369
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
> Fix For: 0.5.0
>
>
> Evaluating Multiple Attributes
> anyAttribute
> allAttributes
> anyMatchingAttribute
> allMatchingAttributes
> anyDelineatedValue
> allDelineatedValues
> join
> count



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-369) Implement multiple attribute expressions in expression language

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481005#comment-16481005
 ] 

ASF GitHub Bot commented on MINIFICPP-369:
--

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/325


> Implement multiple attribute expressions in expression language
> ---
>
> Key: MINIFICPP-369
> URL: https://issues.apache.org/jira/browse/MINIFICPP-369
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
> Fix For: 0.5.0
>
>
> Evaluating Multiple Attributes
> anyAttribute
> allAttributes
> anyMatchingAttribute
> allMatchingAttributes
> anyDelineatedValue
> allDelineatedValues
> join
> count



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16481004#comment-16481004
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri done.


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #325: MINIFICPP-369 Added multiple attribute/ag...

2018-05-18 Thread asfgit

Github user asfgit closed the pull request at:

https://github.com/apache/nifi-minifi-cpp/pull/325


---

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread achristianson

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri done.


---

[jira] [Commented] (MINIFICPP-499) Incorporate property required into agent manifest

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480998#comment-16480998
 ] 

ASF GitHub Bot commented on MINIFICPP-499:
--

GitHub user achristianson opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/332

MINIFICPP-499 Incorporate property required validation metadata into …

…agent manifest

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
 in the commit message?

- [x] Does your PR title start with MINIFI- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] If applicable, have you updated the LICENSE file?
- [x] If applicable, have you updated the NOTICE file?

### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-499

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

https://github.com/apache/nifi-minifi-cpp/pull/332.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 #332


commit 32cfb50ea9557b424abfde609cd98023cb7b2a37
Author: Andrew I. Christianson 
Date:   2018-05-18T18:07:16Z

MINIFICPP-499 Incorporate property required validation metadata into agent 
manifest




> Incorporate property required into agent manifest
> -
>
> Key: MINIFICPP-499
> URL: https://issues.apache.org/jira/browse/MINIFICPP-499
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Report to consumers whether or not each property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #332: MINIFICPP-499 Incorporate property requir...

2018-05-18 Thread achristianson

GitHub user achristianson opened a pull request:

https://github.com/apache/nifi-minifi-cpp/pull/332

MINIFICPP-499 Incorporate property required validation metadata into â¦

â¦agent manifest

Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
 in the commit message?

- [x] Does your PR title start with MINIFI- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [x] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [x] Is your initial contribution a single, squashed commit?

### For code changes:
- [x] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [x] If applicable, have you updated the LICENSE file?
- [x] If applicable, have you updated the NOTICE file?

### For documentation related changes:
- [x] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


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

$ git pull https://github.com/achristianson/nifi-minifi-cpp MINIFICPP-499

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

https://github.com/apache/nifi-minifi-cpp/pull/332.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 #332


commit 32cfb50ea9557b424abfde609cd98023cb7b2a37
Author: Andrew I. Christianson 
Date:   2018-05-18T18:07:16Z

MINIFICPP-499 Incorporate property required validation metadata into agent 
manifest




---

[jira] [Updated] (NIFI-5216) Facilitate npm publish

2018-05-18 Thread Scott Aslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan updated NIFI-5216:
--
Description: 
Add a bash script that takes the built target dir and stage it for deployment 
to npm. The demo-app, node_modules, and several other files should not be 
published to npm for distribution.

 

> Facilitate npm publish
> --
>
> Key: NIFI-5216
> URL: https://issues.apache.org/jira/browse/NIFI-5216
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: FDS
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>
> Add a bash script that takes the built target dir and stage it for deployment 
> to npm. The demo-app, node_modules, and several other files should not be 
> published to npm for distribution.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-5216) Facilitate npm publish

2018-05-18 Thread Scott Aslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan updated NIFI-5216:
--
Issue Type: Improvement  (was: Bug)

> Facilitate npm publish
> --
>
> Key: NIFI-5216
> URL: https://issues.apache.org/jira/browse/NIFI-5216
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: FDS
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>
> Add a bash script that takes the built target dir and stage it for deployment 
> to npm. The demo-app, node_modules, and several other files should not be 
> published to npm for distribution.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (NIFI-5216) Facilitate npm publish

2018-05-18 Thread Scott Aslan (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Scott Aslan updated NIFI-5216:
--
Summary: Facilitate npm publish  (was: Incorrect path to material and 
covalent SASS files)

> Facilitate npm publish
> --
>
> Key: NIFI-5216
> URL: https://issues.apache.org/jira/browse/NIFI-5216
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: FDS
>Reporter: Scott Aslan
>Assignee: Scott Aslan
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-5216) Incorrect path to material and covalent SASS files

2018-05-18 Thread Scott Aslan (JIRA)

Scott Aslan created NIFI-5216:
-

 Summary: Incorrect path to material and covalent SASS files
 Key: NIFI-5216
 URL: https://issues.apache.org/jira/browse/NIFI-5216
 Project: Apache NiFi
  Issue Type: Bug
  Components: FDS
Reporter: Scott Aslan
Assignee: Scott Aslan






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480884#comment-16480884
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson Looks like we need to define the date macro.  We should 
probably also clear out the test elements from the thirdparty source.


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4585) Document nifi.cluster.node.max.concurrent.requests property

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480882#comment-16480882
 ] 

ASF GitHub Bot commented on NIFI-4585:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-4585 Add nifi.cluster.node.max.concurrent.requests to Cluster No…

…de Properties section of Admin Guide

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

$ git pull https://github.com/andrewmlim/nifi NIFI-4585

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

https://github.com/apache/nifi/pull/2719.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 #2719


commit d4f63af1b2b0243d65f30043a0d52dbd38d35b14
Author: Andrew Lim 
Date:   2018-05-18T16:40:23Z

NIFI-4585 Add nifi.cluster.node.max.concurrent.requests to Cluster Node 
Properties section of Admin Guide




> Document nifi.cluster.node.max.concurrent.requests property
> ---
>
> Key: NIFI-4585
> URL: https://issues.apache.org/jira/browse/NIFI-4585
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation  Website
>Reporter: Pierre Villard
>Assignee: Andrew Lim
>Priority: Minor
>
> The property:
> {noformat}
> nifi.cluster.node.max.concurrent.requests
> {noformat}
> needs to be documented in:
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-node-properties



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread apiri

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson Looks like we need to define the date macro.  We should 
probably also clear out the test elements from the thirdparty source.


---

[GitHub] nifi pull request #2719: NIFI-4585 Add nifi.cluster.node.max.concurrent.requ...

2018-05-18 Thread andrewmlim

GitHub user andrewmlim opened a pull request:

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

NIFI-4585 Add nifi.cluster.node.max.concurrent.requests to Cluster Noâ¦

â¦de Properties section of Admin Guide

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

$ git pull https://github.com/andrewmlim/nifi NIFI-4585

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

https://github.com/apache/nifi/pull/2719.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 #2719


commit d4f63af1b2b0243d65f30043a0d52dbd38d35b14
Author: Andrew Lim 
Date:   2018-05-18T16:40:23Z

NIFI-4585 Add nifi.cluster.node.max.concurrent.requests to Cluster Node 
Properties section of Admin Guide




---

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480881#comment-16480881
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

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

https://github.com/apache/nifi-minifi-cpp/pull/315#discussion_r189322613
  
--- Diff: extensions/expression-language/impl/expression/Expression.h ---
@@ -25,6 +25,11 @@
 #undef EXPRESSION_LANGUAGE_USE_REGEX
 #endif
 
+// Disable date in EL for incompatible compilers
--- End diff --

Need to define EXPRESSION_LANGUAGE_USE_DATE


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480880#comment-16480880
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

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

https://github.com/apache/nifi-minifi-cpp/pull/315#discussion_r189289574
  
--- Diff: thirdparty/date/test/clock_cast_test/custom_clock.pass.cpp ---
@@ -0,0 +1,187 @@
+// The MIT License (MIT)
--- End diff --

to minimize what we are carrying with our codebase, could we remove the 
test subdirectory from our thirdparty?


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp pull request #315: MINIFICPP-472 Added date formatting EL fu...

2018-05-18 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/315#discussion_r189289574
  
--- Diff: thirdparty/date/test/clock_cast_test/custom_clock.pass.cpp ---
@@ -0,0 +1,187 @@
+// The MIT License (MIT)
--- End diff --

to minimize what we are carrying with our codebase, could we remove the 
test subdirectory from our thirdparty?


---

[GitHub] nifi-minifi-cpp pull request #315: MINIFICPP-472 Added date formatting EL fu...

2018-05-18 Thread apiri

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

https://github.com/apache/nifi-minifi-cpp/pull/315#discussion_r189322613
  
--- Diff: extensions/expression-language/impl/expression/Expression.h ---
@@ -25,6 +25,11 @@
 #undef EXPRESSION_LANGUAGE_USE_REGEX
 #endif
 
+// Disable date in EL for incompatible compilers
--- End diff --

Need to define EXPRESSION_LANGUAGE_USE_DATE


---

[jira] [Commented] (NIFI-5051) Create a LookupService that uses ElasticSearch

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480875#comment-16480875
 ] 

ASF GitHub Bot commented on NIFI-5051:
--

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2615
  
@mattyb149 I converted it over to be a subclass of `SchemaRegistryService`. 
Let me know if it needs anything else.


> Create a LookupService that uses ElasticSearch
> --
>
> Key: NIFI-5051
> URL: https://issues.apache.org/jira/browse/NIFI-5051
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Mike Thomsen
>Assignee: Mike Thomsen
>Priority: Major
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2615: NIFI-5051 Created ElasticSearch lookup service.

2018-05-18 Thread MikeThomsen

Github user MikeThomsen commented on the issue:

https://github.com/apache/nifi/pull/2615
  
@mattyb149 I converted it over to be a subclass of `SchemaRegistryService`. 
Let me know if it needs anything else.


---

[jira] [Created] (MINIFICPP-502) Support required processor properties

2018-05-18 Thread Andrew Christianson (JIRA)

Andrew Christianson created MINIFICPP-502:
-

 Summary: Support required processor properties
 Key: MINIFICPP-502
 URL: https://issues.apache.org/jira/browse/MINIFICPP-502
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson
Assignee: Andrew Christianson


Allow developers to specify properties as required, and validate this in the 
configuration reader.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (NIFI-5215) Upgrade AngularJS to v1.7.0

2018-05-18 Thread Scott Aslan (JIRA)

Scott Aslan created NIFI-5215:
-

 Summary: Upgrade AngularJS to v1.7.0
 Key: NIFI-5215
 URL: https://issues.apache.org/jira/browse/NIFI-5215
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Scott Aslan
Assignee: Scott Aslan






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2702: Added Apache Pulsar processors

2018-05-18 Thread david-streamlio

Github user david-streamlio commented on the issue:

https://github.com/apache/nifi/pull/2702
  
> Also, something to think about is whether Pulsar's client will work well 
across different broker versions. For example, when Pulsar 2.x comes out, will 
the 1.x client work well against a 2.x broker? or vice versa?

Pulsar API compatibility vs binary protocol compatibility guidelines:
* Protocol compatibility will be always ensured (unless major reasons)
* API can be broken across major releases
The problem is that Kafka broke protocol compatibility at every release, 
which necessitated the 0.9, .0.10, 0.11, and 1.0 versions.

FYI, the 2.0 release is under voting, and should be officially available in 
maven central next week, but I have downloaded the code an built the jar 
locally and am in the process of replacing the deprecated classes with 2.0+ API 
changes.


---

[jira] [Created] (MINIFICPP-501) Incorporate dependent property metadata into agent information

2018-05-18 Thread Andrew Christianson (JIRA)

Andrew Christianson created MINIFICPP-501:
-

 Summary: Incorporate dependent property metadata into agent 
information
 Key: MINIFICPP-501
 URL: https://issues.apache.org/jira/browse/MINIFICPP-501
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson
Assignee: Andrew Christianson


Report which properties a property is dependent upon.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MINIFICPP-500) Incorporate mutally-exlusive property metadata into agent manifest

2018-05-18 Thread Andrew Christianson (JIRA)

Andrew Christianson created MINIFICPP-500:
-

 Summary: Incorporate mutally-exlusive property metadata into agent 
manifest
 Key: MINIFICPP-500
 URL: https://issues.apache.org/jira/browse/MINIFICPP-500
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson
Assignee: Andrew Christianson


Report properties which are mutually-exclusive.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MINIFICPP-499) Incorporate property required into agent manifest

2018-05-18 Thread Andrew Christianson (JIRA)

Andrew Christianson created MINIFICPP-499:
-

 Summary: Incorporate property required into agent manifest
 Key: MINIFICPP-499
 URL: https://issues.apache.org/jira/browse/MINIFICPP-499
 Project: NiFi MiNiFi C++
  Issue Type: Improvement
Reporter: Andrew Christianson
Assignee: Andrew Christianson


Report to consumers whether or not each property is required.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-5171) YandexTranslate Processor Improvement

2018-05-18 Thread Henry Sowell (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480797#comment-16480797
 ] 

Henry Sowell commented on NIFI-5171:


I'm copying in the app logs for the Jersey errors this patch also fixes, which 
caused the processor to stop working after 1.5.0 came out, so that anyone 
encountering similar issues can see what we put together. We fixed the issue by 
adding the following dependency to the pom:
{code:java}
// 
org.glassfish.jersey.inject
jersey-hk2
${jersey.version}

{code}
nifi-app log (error message):
{code:java}
// 2018-04-17 19:35:57,474 INFO [main] org.apache.nifi.NiFi Launching NiFi...
2018-04-17 19:35:57,829 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader 
Determined default nifi.properties path to be 
'/opt/nifi/nifi-1.6.0/./conf/nifi.properties'
2018-04-17 19:35:57,832 INFO [main] o.a.nifi.properties.NiFiPropertiesLoader 
Loaded 146 properties from /opt/nifi/nifi-1.6.0/./conf/nifi.properties
2018-04-17 19:35:57,838 INFO [main] org.apache.nifi.NiFi Loaded 146 properties
2018-04-17 19:35:57,849 INFO [main] org.apache.nifi.BootstrapListener Started 
Bootstrap Listener, Listening for incoming requests on port 37435
2018-04-17 19:35:57,859 INFO [main] org.apache.nifi.BootstrapListener 
Successfully initiated communication with Bootstrap
2018-04-17 19:35:57,871 INFO [main] org.apache.nifi.nar.NarUnpacker Expanding 
97 NAR files with all processors...
2018-04-17 19:36:11,715 INFO [main] org.apache.nifi.nar.NarUnpacker NAR loading 
process took 13843813967 nanoseconds (13 seconds).
2018-04-17 19:36:12,070 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-jetty-bundle-1.6.0.nar-unpacked 
as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-jetty-bundle-1.6.0.nar-unpacked]
2018-04-17 19:36:12,078 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/framework/nifi-framework-nar-1.6.0.nar-unpacked 
as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/framework/nifi-framework-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,079 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-language-translation-nar-1.6.0.nar-unpacked
 as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-language-translation-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,080 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-tcp-nar-1.6.0.nar-unpacked as 
class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-tcp-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,081 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-avro-nar-1.6.0.nar-unpacked as 
class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-avro-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,082 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-ambari-nar-1.6.0.nar-unpacked 
as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-ambari-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,082 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-gcp-services-api-nar-1.6.0.nar-unpacked
 as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-gcp-services-api-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,083 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-kerberos-iaa-providers-nar-1.6.0.nar-unpacked
 as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-kerberos-iaa-providers-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,084 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-hl7-nar-1.6.0.nar-unpacked as 
class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-hl7-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,084 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-spring-nar-1.6.0.nar-unpacked 
as class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-spring-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,085 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-snmp-nar-1.6.0.nar-unpacked as 
class loader 
org.apache.nifi.nar.NarClassLoader[./work/nar/extensions/nifi-snmp-nar-1.6.0.nar-unpacked]
2018-04-17 19:36:12,085 INFO [main] org.apache.nifi.nar.NarClassLoaders Loaded 
NAR file: 
/opt/nifi/nifi-1.6.0/./work/nar/extensions/nifi-slack-nar-1.6.0.nar-unpacked as 
class loader

[jira] [Assigned] (NIFI-4585) Document nifi.cluster.node.max.concurrent.requests property

2018-05-18 Thread Andrew Lim (JIRA)


 [ 
https://issues.apache.org/jira/browse/NIFI-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrew Lim reassigned NIFI-4585:


Assignee: Andrew Lim

> Document nifi.cluster.node.max.concurrent.requests property
> ---
>
> Key: NIFI-4585
> URL: https://issues.apache.org/jira/browse/NIFI-4585
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation  Website
>Reporter: Pierre Villard
>Assignee: Andrew Lim
>Priority: Minor
>
> The property:
> {noformat}
> nifi.cluster.node.max.concurrent.requests
> {noformat}
> needs to be documented in:
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-node-properties



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4585) Document nifi.cluster.node.max.concurrent.requests property

2018-05-18 Thread Andrew Lim (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480770#comment-16480770
 ] 

Andrew Lim commented on NIFI-4585:
--

Consulted with [~markap14].  Here is the description that will be added to the 
docs for this property:

{{The maximum number of outstanding web requests that can be replicated to 
nodes in the cluster. If this number of requests is exceeded, the embedded 
Jetty server will return a "409: Conflict" response.  This property defaults to 
100.}}

 

> Document nifi.cluster.node.max.concurrent.requests property
> ---
>
> Key: NIFI-4585
> URL: https://issues.apache.org/jira/browse/NIFI-4585
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation  Website
>Reporter: Pierre Villard
>Priority: Minor
>
> The property:
> {noformat}
> nifi.cluster.node.max.concurrent.requests
> {noformat}
> needs to be documented in:
> https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#cluster-node-properties



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread veteranbv

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

https://github.com/apache/nifi/pull/2715#discussion_r189294140
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/pom.xml
 ---
@@ -53,7 +53,12 @@
 jersey-media-json-jackson
 ${jersey.version}
 
-
+
+org.glassfish.jersey.inject
+jersey-hk2
--- End diff --

@mattyb149 Added


---

[GitHub] nifi pull request #2715: Nifi-5171 - fixed Yandex Jersey issues by adding de...

2018-05-18 Thread veteranbv

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

https://github.com/apache/nifi/pull/2715#discussion_r189289257
  
--- Diff: 
nifi-nar-bundles/nifi-language-translation-bundle/nifi-yandex-processors/pom.xml
 ---
@@ -53,7 +53,12 @@
 jersey-media-json-jackson
 ${jersey.version}
 
-
+
+org.glassfish.jersey.inject
+jersey-hk2
--- End diff --

I'll get the following line added to the NOTICE file:
`(CDDL 1.1) (GPL2 w/ CPE) jersey-hk2 
(org.glassfish.jersey.inject:jersey-hk2:jar:2.26 - https://jersey.github.io/)`


---

[jira] [Commented] (NIFI-5041) Add convenient SPNEGO/Kerberos authentication support to LivySessionController

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480729#comment-16480729
 ] 

ASF GitHub Bot commented on NIFI-5041:
--

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

https://github.com/apache/nifi/pull/2630#discussion_r189287529
  
--- Diff: 
nifi-nar-bundles/nifi-spark-bundle/nifi-livy-controller-service/src/main/java/org/apache/nifi/controller/livy/LivySessionController.java
 ---
@@ -551,4 +561,11 @@ private SSLContext 
getSslSocketFactory(SSLContextService sslService)
 return sslContext;
 }
 
+private void checkSessionManagerError() throws IOException {
+Exception exception = sessionManagerError;
+if (exception != null) {
+throw new IOException(exception);
--- End diff --

I'm thinking this should be a custom exception type, probably thrown from 
the manageSession() thread itself and just propagated to the client via this 
method, in order to be able to tell the difference between an IOException that 
occurred from the mgmt thread vs an IOException that occurred from the 
operation the client is trying to perform. Thoughts?


> Add convenient SPNEGO/Kerberos authentication support to LivySessionController
> --
>
> Key: NIFI-5041
> URL: https://issues.apache.org/jira/browse/NIFI-5041
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Peter Toth
>Priority: Minor
>
> Livy requires SPNEGO/Kerberos authentication on a secured cluster. Initiating 
> such an authentication from NiFi is a viable by providing a 
> java.security.auth.login.config system property 
> (https://docs.oracle.com/javase/8/docs/technotes/guides/security/jgss/lab/part6.html),
>  but this is a bit cumbersome and needs kinit running outside of NiFi.
> An alternative and more sophisticated solution would be to do the SPNEGO 
> negotiation programmatically.
>  * This solution would add some new properties to the LivySessionController 
> to fetch kerberos principal and password/keytab
>  * Add the required HTTP Negotiate header (with an SPNEGO token) to the 
> HttpURLConnection to do the authentication programmatically 
> (https://tools.ietf.org/html/rfc4559)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi pull request #2630: NIFI-5041 Adds SPNEGO authentication to LivySession...

2018-05-18 Thread mattyb149

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

https://github.com/apache/nifi/pull/2630#discussion_r189287529
  
--- Diff: 
nifi-nar-bundles/nifi-spark-bundle/nifi-livy-controller-service/src/main/java/org/apache/nifi/controller/livy/LivySessionController.java
 ---
@@ -551,4 +561,11 @@ private SSLContext 
getSslSocketFactory(SSLContextService sslService)
 return sslContext;
 }
 
+private void checkSessionManagerError() throws IOException {
+Exception exception = sessionManagerError;
+if (exception != null) {
+throw new IOException(exception);
--- End diff --

I'm thinking this should be a custom exception type, probably thrown from 
the manageSession() thread itself and just propagated to the client via this 
method, in order to be able to tell the difference between an IOException that 
occurred from the mgmt thread vs an IOException that occurred from the 
operation the client is trying to perform. Thoughts?


---

[jira] [Created] (NIFI-5214) Add a REST lookup service

2018-05-18 Thread Mike Thomsen (JIRA)

Mike Thomsen created NIFI-5214:
--

 Summary: Add a REST lookup service
 Key: NIFI-5214
 URL: https://issues.apache.org/jira/browse/NIFI-5214
 Project: Apache NiFi
  Issue Type: New Feature
Reporter: Mike Thomsen
Assignee: Mike Thomsen


* Should have reader API support
 * Should be able to drill down through complex XML and JSON responses to a 
nested record.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480685#comment-16480685
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson will scope out in a bit


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread apiri

Github user apiri commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@achristianson will scope out in a bit


---

[jira] [Commented] (MINIFICPP-472) Implement date manipulation EL functions

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480633#comment-16480633
 ] 

ASF GitHub Bot commented on MINIFICPP-472:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri looks like travis issue is fixed. Did you see any other issues?


> Implement date manipulation EL functions
> 
>
> Key: MINIFICPP-472
> URL: https://issues.apache.org/jira/browse/MINIFICPP-472
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> [Date 
> Manipulation|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates]
>  * 
> [format|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#format]
>  * 
> [toDate|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#todate]
>  * 
> [now|https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#now]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #325: MINIFICPP-369 Added multiple attribute/aggregate...

2018-05-18 Thread achristianson

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/325
  
@phrocker fixed travis & rebased. Did you see anything else?


---

[jira] [Commented] (MINIFICPP-369) Implement multiple attribute expressions in expression language

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/MINIFICPP-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480634#comment-16480634
 ] 

ASF GitHub Bot commented on MINIFICPP-369:
--

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/325
  
@phrocker fixed travis & rebased. Did you see anything else?


> Implement multiple attribute expressions in expression language
> ---
>
> Key: MINIFICPP-369
> URL: https://issues.apache.org/jira/browse/MINIFICPP-369
> Project: NiFi MiNiFi C++
>  Issue Type: Improvement
>Reporter: Andrew Christianson
>Assignee: Andrew Christianson
>Priority: Major
>
> Evaluating Multiple Attributes
> anyAttribute
> allAttributes
> anyMatchingAttribute
> allMatchingAttributes
> anyDelineatedValue
> allDelineatedValues
> join
> count



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi-minifi-cpp issue #315: MINIFICPP-472 Added date formatting EL functions

2018-05-18 Thread achristianson

Github user achristianson commented on the issue:

https://github.com/apache/nifi-minifi-cpp/pull/315
  
@apiri looks like travis issue is fixed. Did you see any other issues?


---

[jira] [Commented] (NIFI-4199) NiFi processors should be able to share proxy settings

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480554#comment-16480554
 ] 

ASF GitHub Bot commented on NIFI-4199:
--

Github user ottobackwards commented on the issue:

https://github.com/apache/nifi/pull/2704
  
Should the tests for InvokeHTTP be updated to test with the changes?


> NiFi processors should be able to share proxy settings
> --
>
> Key: NIFI-4199
> URL: https://issues.apache.org/jira/browse/NIFI-4199
> Project: Apache NiFi
>  Issue Type: Improvement
>Reporter: Andre F de Miranda
>Assignee: Koji Kawamura
>Priority: Major
>
> Currently, configuring proxy settings for NiFi processors may be a tedious 
> process that requires the DFM to set proxy settings on individual processors. 
> This leads to:
> * Duplication of work
> * Management overhead (as password must be changed on multiple locations)
> * Lower security (as proxy credentials must be known by "n" DFMs)
> Ideally, NiFi should offer a way to minimise duplication of work by offering 
> a something similar to the Standard SSL Context services. This way, the DFM 
> could set the proxy settings once an all authorised users could tap into 
> those settings.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2704: NIFI-4199: Consistent proxy support across components

2018-05-18 Thread ottobackwards

Github user ottobackwards commented on the issue:

https://github.com/apache/nifi/pull/2704
  
Should the tests for InvokeHTTP be updated to test with the changes?


---

[jira] [Commented] (NIFI-5022) Create an AWS Gateway Web API version of InvokeHTTP

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480493#comment-16480493
 ] 

ASF GitHub Bot commented on NIFI-5022:
--

Github user ottobackwards commented on the issue:

https://github.com/apache/nifi/pull/2588
  
@mattyb149 no word on that pr.  @jvwing any chance you may be able to 
review?



> Create an AWS Gateway Web API version of InvokeHTTP
> ---
>
> Key: NIFI-5022
> URL: https://issues.apache.org/jira/browse/NIFI-5022
> Project: Apache NiFi
>  Issue Type: New Feature
>Reporter: Otto Fowler
>Assignee: Otto Fowler
>Priority: Major
>
> Currently the AWS processors are lacking support to call AWS Gateway Web Apis.
> Nifi should provide support for calling this apis, including support for all 
> the same authentication methods available to the other AWS client processors.
> Since these APIs are web services, their expected use would require an 
> interface more like InvokeHTTP however, than the specialized interfaces for 
> the other AWS Services.
> What would be required then would be a new AWS Processor that exposed the 
> same interface as InvokeHTTP, but backed by the AWS client support ( and of 
> course modified to fit the differences between the OK http client and the 
> Amazon client ).
> This new processor should be able to pass all the applicable tests available 
> in the InvokeHttp test suite.
> The processor should also be factored in such a way as to make it possible 
> for the creation of custom processors for specific apis
>  
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] nifi issue #2588: NIFI-5022 InvokeAWSGatewayApi processor

2018-05-18 Thread ottobackwards

Github user ottobackwards commented on the issue:

https://github.com/apache/nifi/pull/2588
  
@mattyb149 no word on that pr.  @jvwing any chance you may be able to 
review?



---

[GitHub] nifi pull request #2682: NIFI-4731: BQ Processors and GCP library update.

2018-05-18 Thread danieljimenez

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

https://github.com/apache/nifi/pull/2682#discussion_r189218048
  
--- Diff: 
nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/BigQueryAttributes.java
 ---
@@ -0,0 +1,81 @@
+/*
+ * 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.processors.gcp.bigquery;
+
+/**
+ * Attributes associated with the BigQuery processors
+ */
+public class BigQueryAttributes {
+private BigQueryAttributes() {}
+
+public static final String DATASET_ATTR = "bq.dataset";
--- End diff --

That sounds okay to me, I'll try and cover that in the rebase.


---

[jira] [Commented] (NIFI-4731) BigQuery processors

2018-05-18 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4731?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480422#comment-16480422
 ] 

ASF GitHub Bot commented on NIFI-4731:
--

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

https://github.com/apache/nifi/pull/2682#discussion_r189218048
  
--- Diff: 
nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery/BigQueryAttributes.java
 ---
@@ -0,0 +1,81 @@
+/*
+ * 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.processors.gcp.bigquery;
+
+/**
+ * Attributes associated with the BigQuery processors
+ */
+public class BigQueryAttributes {
+private BigQueryAttributes() {}
+
+public static final String DATASET_ATTR = "bq.dataset";
--- End diff --

That sounds okay to me, I'll try and cover that in the rebase.


> BigQuery processors
> ---
>
> Key: NIFI-4731
> URL: https://issues.apache.org/jira/browse/NIFI-4731
> Project: Apache NiFi
>  Issue Type: New Feature
>  Components: Extensions
>Reporter: Mikhail Sosonkin
>Priority: Major
>
> NIFI should have processors for putting data into BigQuery (Streaming and 
> Batch).
> Initial working processors can be found this repository: 
> https://github.com/nologic/nifi/tree/NIFI-4731/nifi-nar-bundles/nifi-gcp-bundle/nifi-gcp-processors/src/main/java/org/apache/nifi/processors/gcp/bigquery
> I'd like to get them into Nifi proper.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (NIFI-4535) Set the Page Title to the name of the Root Process Group

2018-05-18 Thread Daniel (JIRA)


[ 
https://issues.apache.org/jira/browse/NIFI-4535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16480393#comment-16480393
 ] 

Daniel commented on NIFI-4535:
--

Brilliant idea.

> Set the Page Title to the name of the Root Process Group
> 
>
> Key: NIFI-4535
> URL: https://issues.apache.org/jira/browse/NIFI-4535
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Core UI
>Reporter: Peter Wicks
>Priority: Minor
>
> NiFi's UI has a hard coded page title of NiFi. I have many servers and it's 
> hard to keep track of the tabs in Chrome.
> Please change the Title of the page so it matches the name of the Root 
> processor group. This way I can name the root group by server/instance, and 
> easily identify the right tab/window.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

1 2 >

1 - 100 of 115 matches

Mail list logo