date:20161201

[jira] [Resolved] (NIFI-3056) Update documentation/screenshots for color changes to icons for status (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)

2016-12-01 Thread Andy LoPresto (JIRA)


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

Andy LoPresto resolved NIFI-3056.
-
Resolution: Fixed

> Update documentation/screenshots for color changes to icons for status 
> (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)
> --
>
> Key: NIFI-3056
> URL: https://issues.apache.org/jira/browse/NIFI-3056
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Sarah Olson
>Priority: Minor
>
> In NIFI-3052, the iconRun, iconStop and iconAlert icons were replaced with 
> colored versions for the Admin Guide and Getting Started guide.   However, in 
> other docs like the User Guide these icons were referenced but not for 
> processor status, but for processor actions (Operate Palette and context menu 
> buttons/selections).  New screenshots should be created for the processor 
> actions.
> Other docs should also be looked at to update enabled/disabled and 
> transmitting/not transmitting screenshots per NIFI-2603. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1269: NIFI-3056 Updated User Guide screenshot and text wi...

2016-12-01 Thread asfgit

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2325) Add support for LDAPS in authentication provider

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-2325:
--

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1275
  
I set up a Docker container running OpenLDAP with certificates I generated 
using the NiFI TLS toolkit. If I configure `TLS_VERIFY_CLIENT=never` on 
OpenLDAP and `NONE` in 
`login-identity-providers.xml`, the LDAP login provider works fine. 

https://cloud.githubusercontent.com/assets/798465/20823670/2c913e58-b80b-11e6-8353-a98746c5dfb6.png;>

However, if I switch to `TLS_VERIFY_CLIENT=demand` and `REQUIRED`, I get a "Unable to validate the supplied 
credentials" error on login and the `logs/nifi-bootstrap.log` fills with TLS 
negotiation output including the lines below:

```
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** CertificateVerify
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Signature Algorithm SHA256withRSA
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Handshake, length = 264
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Change Cipher Spec, length = 1
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** Finished
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
verify_data:  { 12, 201, 103, 33, 205, 116, 165, 164, 117, 65, 44, 206 }
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
***
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Handshake, length = 96
2016-12-01 21:19:12,956 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, READ: TLSv1.2 Change Cipher Spec, length = 1
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, READ: TLSv1.2 Handshake, length = 96
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** Finished
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
verify_data:  { 67, 162, 103, 118, 253, 199, 182, 215, 157, 89, 207, 22 }
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
***
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
%% Cached client session: [Session-346, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384]
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, setSoTimeout(0) called
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 112
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, received EOFException: ignored
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeInternal(false)
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, SEND TLSv1.2 ALERT:  warning, description = close_notify
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, WRITE: TLSv1.2 Alert, length = 80
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeSocket(false)
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called close()
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeInternal(true)
2016-12-01 21:19:12,970 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 250
2016-12-01 21:19:12,970 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 7
```

I want to continue investigating this tomorrow because I can produce odd 
results even using the `ldapsearch` tool locally (OpenLDAP configured with 
client verify `never`):

```
### Trying on port 389 (no TLS)

hw12203:/Users/alopresto/Workspace/certificates/ldaps (master) alopresto
 4s @ 21:41:04 $ ldapsearch -x -h localhost -b dc=example,dc=org -D 
"cn=admin,dc=example,dc=org" -w admin -p 389 -v
ldap_initialize( ldap://localhost:389 )
filter: (objectclass=*)
requesting: All userApplication attributes
# extended LDIF
#
# LDAPv3
# base

[GitHub] nifi issue #1275: NIFI-2325 - Add support for LDAPS

2016-12-01 Thread alopresto

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1275
  
I set up a Docker container running OpenLDAP with certificates I generated 
using the NiFI TLS toolkit. If I configure `TLS_VERIFY_CLIENT=never` on 
OpenLDAP and `NONE` in 
`login-identity-providers.xml`, the LDAP login provider works fine. 

https://cloud.githubusercontent.com/assets/798465/20823670/2c913e58-b80b-11e6-8353-a98746c5dfb6.png;>

However, if I switch to `TLS_VERIFY_CLIENT=demand` and `REQUIRED`, I get a "Unable to validate the supplied 
credentials" error on login and the `logs/nifi-bootstrap.log` fills with TLS 
negotiation output including the lines below:

```
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** CertificateVerify
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Signature Algorithm SHA256withRSA
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Handshake, length = 264
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Change Cipher Spec, length = 1
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** Finished
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
verify_data:  { 12, 201, 103, 33, 205, 116, 165, 164, 117, 65, 44, 206 }
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
***
2016-12-01 21:19:12,954 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Handshake, length = 96
2016-12-01 21:19:12,956 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, READ: TLSv1.2 Change Cipher Spec, length = 1
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, READ: TLSv1.2 Handshake, length = 96
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
*** Finished
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
verify_data:  { 67, 162, 103, 118, 253, 199, 182, 215, 157, 89, 207, 22 }
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
***
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
%% Cached client session: [Session-346, TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384]
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, setSoTimeout(0) called
2016-12-01 21:19:12,957 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 112
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, received EOFException: ignored
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeInternal(false)
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, SEND TLSv1.2 ALERT:  warning, description = close_notify
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, WRITE: TLSv1.2 Alert, length = 80
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeSocket(false)
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called close()
2016-12-01 21:19:12,958 INFO [NiFi logging handler] org.apache.nifi.StdOut 
Thread-36, called closeInternal(true)
2016-12-01 21:19:12,970 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 250
2016-12-01 21:19:12,970 INFO [NiFi logging handler] org.apache.nifi.StdOut 
NiFi Web Server-95, WRITE: TLSv1.2 Application Data, length = 7
```

I want to continue investigating this tomorrow because I can produce odd 
results even using the `ldapsearch` tool locally (OpenLDAP configured with 
client verify `never`):

```
### Trying on port 389 (no TLS)

hw12203:/Users/alopresto/Workspace/certificates/ldaps (master) alopresto
ð 4s @ 21:41:04 $ ldapsearch -x -h localhost -b dc=example,dc=org -D 
"cn=admin,dc=example,dc=org" -w admin -p 389 -v
ldap_initialize( ldap://localhost:389 )
filter: (objectclass=*)
requesting: All userApplication attributes
# extended LDIF
#
# LDAPv3
# base

[jira] [Commented] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3141:
--

GitHub user ijokarumawak opened a pull request:

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

NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

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:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?

### 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.

- Added unit test cases to simulate NiFi version update which fails without 
this fix.
- Added state object migration code, add file.0. prefix to state keys,
  and add length from stored position.

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

$ git pull https://github.com/ijokarumawak/nifi nifi-3141

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

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


commit 28676fdb95af98cca5d30f3ce37af6f5ace7a19a
Author: Koji Kawamura 
Date:   2016-12-02T02:23:33Z

NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

- Added unit test cases to simulate NiFi version update which fails without 
this fix.
- Added state object migration code, add file.0. prefix to state keys,
  and add length from stored position.




> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1289: NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

2016-12-01 Thread ijokarumawak

GitHub user ijokarumawak opened a pull request:

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

NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

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:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?

### 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.

- Added unit test cases to simulate NiFi version update which fails without 
this fix.
- Added state object migration code, add file.0. prefix to state keys,
  and add length from stored position.

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

$ git pull https://github.com/ijokarumawak/nifi nifi-3141

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

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


commit 28676fdb95af98cca5d30f3ce37af6f5ace7a19a
Author: Koji Kawamura 
Date:   2016-12-02T02:23:33Z

NIFI-3141: Fixed TailFile ArrayIndexOutOfBounds.

- Added unit test cases to simulate NiFi version update which fails without 
this fix.
- Added state object migration code, add file.0. prefix to state keys,
  and add length from stored position.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

2016-12-01 Thread Koji Kawamura (JIRA)


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

Koji Kawamura updated NIFI-3141:

Attachment: NiFi 1.1.0 TailFile status.png

> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

2016-12-01 Thread Koji Kawamura (JIRA)


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

Koji Kawamura updated NIFI-3141:

Attachment: NiFi 1.0.0 TailFile status.png

> TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 
> 1.1.0
> 
>
> Key: NIFI-3141
> URL: https://issues.apache.org/jira/browse/NIFI-3141
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Koji Kawamura
> Attachments: NiFi 1.0.0 TailFile status.png, NiFi 1.1.0 TailFile 
> status.png
>
>
> TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
> have index in state key name. But the updated TailFile expects stored state 
> key has index in it, tried to extract the index and failed.
> {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
> at 
> org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
> ~[na:na]
> at 
> org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
> ~[na:na]
> ... 16 common frames omitted
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3141) TailFile failed with ArrayIndexOutOfBoundsException after updating NiFi to 1.1.0

2016-12-01 Thread Koji Kawamura (JIRA)

Koji Kawamura created NIFI-3141:
---

 Summary: TailFile failed with ArrayIndexOutOfBoundsException after 
updating NiFi to 1.1.0
 Key: NIFI-3141
 URL: https://issues.apache.org/jira/browse/NIFI-3141
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Koji Kawamura


TailFile with NiFi 1.0.0 or earlier only handles single file. So it doesn't 
have index in state key name. But the updated TailFile expects stored state key 
has index in it, tried to extract the index and failed.

{code}
Caused by: java.lang.ArrayIndexOutOfBoundsException: 1
at 
org.apache.nifi.processors.standard.TailFile.initStates(TailFile.java:365) 
~[na:na]
at 
org.apache.nifi.processors.standard.TailFile.recoverState(TailFile.java:348) 
~[na:na]
... 16 common frames omitted
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3140:
--

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1288
  
@gresockj Do you mind taking a look at this? I want to make sure I didn't 
miss something in the API or any potential differences between versions. For 
the Http processors I'd like to keep the least-common-denominator principle, 
since they are the alternative to the other Transport-based processors that 
require a particular (major) version.  Thanks!


> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1288: NIFI-3140: Restored optional type handling in FetchElastic...

2016-12-01 Thread mattyb149

Github user mattyb149 commented on the issue:

https://github.com/apache/nifi/pull/1288
  
@gresockj Do you mind taking a look at this? I want to make sure I didn't 
miss something in the API or any potential differences between versions. For 
the Http processors I'd like to keep the least-common-denominator principle, 
since they are the alternative to the other Transport-based processors that 
require a particular (major) version.  Thanks!


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3140:
--

GitHub user mattyb149 opened a pull request:

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

NIFI-3140: Restored optional type handling in FetchElasticsearchHttp

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:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] 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-3140

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

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


commit 8f0db002a4abb571980f0d2fe61c864f20b77693
Author: Matt Burgess 
Date:   2016-12-02T00:32:49Z

NIFI-3140: Restored optional type handling in FetchElasticsearchHttp




> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1288: NIFI-3140: Restored optional type handling in Fetch...

2016-12-01 Thread mattyb149

GitHub user mattyb149 opened a pull request:

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

NIFI-3140: Restored optional type handling in FetchElasticsearchHttp

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:
- [x] Have you ensured that the full suite of tests is executed via mvn 
-Pcontrib-check clean install at the root nifi folder?
- [x] 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-3140

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

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


commit 8f0db002a4abb571980f0d2fe61c864f20b77693
Author: Matt Burgess 
Date:   2016-12-02T00:32:49Z

NIFI-3140: Restored optional type handling in FetchElasticsearchHttp




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

2016-12-01 Thread Matt Burgess (JIRA)


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

Matt Burgess updated NIFI-3140:
---
Affects Version/s: 1.1.0

> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

2016-12-01 Thread Matt Burgess (JIRA)


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

Matt Burgess updated NIFI-3140:
---
Issue Type: Bug  (was: Improvement)

> FetchElasticsearchHttp no longer accepts optional type
> --
>
> Key: NIFI-3140
> URL: https://issues.apache.org/jira/browse/NIFI-3140
> Project: Apache NiFi
>  Issue Type: Bug
>Reporter: Matt Burgess
>Assignee: Matt Burgess
> Fix For: 1.2.0
>
>
> In NiFi 1.1.0, if the Type property is omitted from the 
> FetchElasticsearchHttp configuration (and a specific index is specified 
> rather than _all), the processor fails with an error "400 Bad Request".
> This is a result of FetchElasticsearchHttp URL building being aligned with 
> those used in the Query/ScrollElasticsearchHttp processors (added in 
> NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
> Search APIs.
> For FetchElasticsearchHttp, the logic should be restored to insert a path 
> segment of "_all" if the Type is not provided, and the Index property 
> description should be reverted to not imply the use of "_all". Although it is 
> possible to issue a successful Get against all indexes, it cannot have a type 
> or document ID specified, and even then it does not return a document but 
> instead a listing of indexes, which is inconsistent with the purpose of the 
> processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3140) FetchElasticsearchHttp no longer accepts optional type

2016-12-01 Thread Matt Burgess (JIRA)

Matt Burgess created NIFI-3140:
--

 Summary: FetchElasticsearchHttp no longer accepts optional type
 Key: NIFI-3140
 URL: https://issues.apache.org/jira/browse/NIFI-3140
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Matt Burgess
Assignee: Matt Burgess
 Fix For: 1.2.0


In NiFi 1.1.0, if the Type property is omitted from the FetchElasticsearchHttp 
configuration (and a specific index is specified rather than _all), the 
processor fails with an error "400 Bad Request".

This is a result of FetchElasticsearchHttp URL building being aligned with 
those used in the Query/ScrollElasticsearchHttp processors (added in 
NIFI-2417). Unfortunately the REST API is not consistent between the Get and 
Search APIs.

For FetchElasticsearchHttp, the logic should be restored to insert a path 
segment of "_all" if the Type is not provided, and the Index property 
description should be reverted to not imply the use of "_all". Although it is 
possible to issue a successful Get against all indexes, it cannot have a type 
or document ID specified, and even then it does not return a document but 
instead a listing of indexes, which is inconsistent with the purpose of the 
processor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (NIFI-3136) Add documentation for User Policies window

2016-12-01 Thread Andrew Lim (JIRA)


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

Andrew Lim resolved NIFI-3136.
--
Resolution: Duplicate

NIFI-3137 is a dupe.

> Add documentation for User Policies window
> --
>
> Key: NIFI-3136
> URL: https://issues.apache.org/jira/browse/NIFI-3136
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-3056) Update documentation/screenshots for color changes to icons for status (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)

2016-12-01 Thread Sarah Olson (JIRA)


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

Sarah Olson reassigned NIFI-3056:
-

Assignee: Sarah Olson

> Update documentation/screenshots for color changes to icons for status 
> (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)
> --
>
> Key: NIFI-3056
> URL: https://issues.apache.org/jira/browse/NIFI-3056
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Sarah Olson
>Priority: Minor
>
> In NIFI-3052, the iconRun, iconStop and iconAlert icons were replaced with 
> colored versions for the Admin Guide and Getting Started guide.   However, in 
> other docs like the User Guide these icons were referenced but not for 
> processor status, but for processor actions (Operate Palette and context menu 
> buttons/selections).  New screenshots should be created for the processor 
> actions.
> Other docs should also be looked at to update enabled/disabled and 
> transmitting/not transmitting screenshots per NIFI-2603. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1269: NIFI-3056 Updated User Guide screenshot and text with late...

2016-12-01 Thread thesolson

Github user thesolson commented on the issue:

https://github.com/apache/nifi/pull/1269
  
Hi Drew! These updates look great to me. Thanks for doing that. Please go 
ahead and merge as appropriate.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3056) Update documentation/screenshots for color changes to icons for status (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3056:
--

Github user thesolson commented on the issue:

https://github.com/apache/nifi/pull/1269
  
Hi Drew! These updates look great to me. Thanks for doing that. Please go 
ahead and merge as appropriate.


> Update documentation/screenshots for color changes to icons for status 
> (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)
> --
>
> Key: NIFI-3056
> URL: https://issues.apache.org/jira/browse/NIFI-3056
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Priority: Minor
>
> In NIFI-3052, the iconRun, iconStop and iconAlert icons were replaced with 
> colored versions for the Admin Guide and Getting Started guide.   However, in 
> other docs like the User Guide these icons were referenced but not for 
> processor status, but for processor actions (Operate Palette and context menu 
> buttons/selections).  New screenshots should be created for the processor 
> actions.
> Other docs should also be looked at to update enabled/disabled and 
> transmitting/not transmitting screenshots per NIFI-2603. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3056) Update documentation/screenshots for color changes to icons for status (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3056:
--

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1269
  
Incorporated some of my comments above and also added some additional 
screenshots to make PR complete.


[0001-NIFI-3056-Incorporated-feedback-and-added-additional.txt](https://github.com/apache/nifi/files/625776/0001-NIFI-3056-Incorporated-feedback-and-added-additional.txt)



> Update documentation/screenshots for color changes to icons for status 
> (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)
> --
>
> Key: NIFI-3056
> URL: https://issues.apache.org/jira/browse/NIFI-3056
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Priority: Minor
>
> In NIFI-3052, the iconRun, iconStop and iconAlert icons were replaced with 
> colored versions for the Admin Guide and Getting Started guide.   However, in 
> other docs like the User Guide these icons were referenced but not for 
> processor status, but for processor actions (Operate Palette and context menu 
> buttons/selections).  New screenshots should be created for the processor 
> actions.
> Other docs should also be looked at to update enabled/disabled and 
> transmitting/not transmitting screenshots per NIFI-2603. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1269: NIFI-3056 Updated User Guide screenshot and text with late...

2016-12-01 Thread andrewmlim

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1269
  
Incorporated some of my comments above and also added some additional 
screenshots to make PR complete.


[0001-NIFI-3056-Incorporated-feedback-and-added-additional.txt](https://github.com/apache/nifi/files/625776/0001-NIFI-3056-Incorporated-feedback-and-added-additional.txt)



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (NIFI-3139) Add Hostname:Port and Non-Empty Expression Language validators to StandardValidators

2016-12-01 Thread Matt Burgess (JIRA)

Matt Burgess created NIFI-3139:
--

 Summary: Add Hostname:Port and Non-Empty Expression Language 
validators to StandardValidators
 Key: NIFI-3139
 URL: https://issues.apache.org/jira/browse/NIFI-3139
 Project: Apache NiFi
  Issue Type: Improvement
Reporter: Matt Burgess


The Elasticsearch processors use a couple of validators to help with their 
properties:

1) Hostname:Port validator. This currently validates a comma-separated list of 
hostname:port values

2) Non-Empty Expression Language validator: This extends the 
NON_EMPTY_VALIDATOR to be valid if there is expression language present.

These could (with minor adjustments) be moved to StandardValidators for other 
components' use.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1276: NIFI-3095: Add EL support to Elasticsearch 2.x (and...

2016-12-01 Thread mattyb149

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

https://github.com/apache/nifi/pull/1276#discussion_r90534894
  
--- Diff: 
nifi-nar-bundles/nifi-elasticsearch-bundle/nifi-elasticsearch-processors/src/main/java/org/apache/nifi/processors/elasticsearch/AbstractElasticsearchProcessor.java
 ---
@@ -28,14 +29,20 @@
 
 import java.util.Collection;
 import java.util.HashSet;
-import java.util.Map;
 import java.util.Set;
 
 /**
  * A base class for all Elasticsearch processors
  */
 public abstract class AbstractElasticsearchProcessor extends 
AbstractProcessor {
 
+protected static final Validator NON_EMPTY_EL_VALIDATOR = (subject, 
value, context) -> {
--- End diff --

Opened [NIFI-3139](https://issues.apache.org/jira/browse/NIFI-3139) to move 
the validators to StandardValidators


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3137:
--

Github user asfgit closed the pull request at:

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


> Add documentation for User Policies window
> --
>
> Key: NIFI-3137
> URL: https://issues.apache.org/jira/browse/NIFI-3137
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1286: NIFI-3137 Add documentation for User Policies windo...

2016-12-01 Thread asfgit

Github user asfgit closed the pull request at:

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


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-3137 Add documentation for User Policies window

This closes #1286


> Add documentation for User Policies window
> --
>
> Key: NIFI-3137
> URL: https://issues.apache.org/jira/browse/NIFI-3137
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3137:
--

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1286
  
Reviewing...


> Add documentation for User Policies window
> --
>
> Key: NIFI-3137
> URL: https://issues.apache.org/jira/browse/NIFI-3137
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1286: NIFI-3137 Add documentation for User Policies window

2016-12-01 Thread scottyaslan

Github user scottyaslan commented on the issue:

https://github.com/apache/nifi/pull/1286
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-3135) Check restricted components on template instantiation

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3135:
--

GitHub user mcgilman opened a pull request:

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

Authorizing restricted components on snippet usage

NIFI-3135:
- Authorizing restricted components on snippet usage.
- Ensuring REST API docs accordingly.

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

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

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

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


commit feada6456421160912e1c2b0eb1e1ff1789b1a88
Author: Matt Gilman 
Date:   2016-12-01T19:54:40Z

NIFI-3135:
- Authorizing restricted components on snippet usage.
- Ensuring REST API docs accordingly.




> Check restricted components on template instantiation
> -
>
> Key: NIFI-3135
> URL: https://issues.apache.org/jira/browse/NIFI-3135
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core Framework
>Reporter: Matt Gilman
>Assignee: Matt Gilman
> Fix For: 1.2.0
>
>
> When creating components we create a temporary instance to check if the 
> component is restricted. We should also be performing this check when 
> creating the components through template instantiation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1287: Authorizing restricted components on snippet usage

2016-12-01 Thread mcgilman

GitHub user mcgilman opened a pull request:

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

Authorizing restricted components on snippet usage

NIFI-3135:
- Authorizing restricted components on snippet usage.
- Ensuring REST API docs accordingly.

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

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

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

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


commit feada6456421160912e1c2b0eb1e1ff1789b1a88
Author: Matt Gilman 
Date:   2016-12-01T19:54:40Z

NIFI-3135:
- Authorizing restricted components on snippet usage.
- Ensuring REST API docs accordingly.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Description: 
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the [1.1.0 NiFi core 
libraries|https://github.com/apache/nifi-minifi/commit/85d69eadae5bffb570a28fcb4a05649d58605ce6]):
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.

  was:
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.


> Need to add new RPG elements to

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Attachment: flow.xml.gz

> Need to add new RPG elements to FlowConfiguration.xsd
> -
>
> Key: NIFI-3138
> URL: https://issues.apache.org/jira/browse/NIFI-3138
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
> Attachments: InvokeHttpMiNiFiTemplateTest.xml, config.yml, flow.xml.gz
>
>
> There are new valid elements in the Remote Process Group portion of the 
> [standard flow serializer 
> xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
>   These are currently not part of the 
> [xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].
> This means that if these elements are in the flow.xml, you get output like 
> the following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
> {code}
> 2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> {code}
> The flow still seems to work so I think it's just a warning but still not 
> great to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Attachment: config.yml

> Need to add new RPG elements to FlowConfiguration.xsd
> -
>
> Key: NIFI-3138
> URL: https://issues.apache.org/jira/browse/NIFI-3138
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
> Attachments: InvokeHttpMiNiFiTemplateTest.xml, config.yml
>
>
> There are new valid elements in the Remote Process Group portion of the 
> [standard flow serializer 
> xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
>   These are currently not part of the 
> [xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].
> This means that if these elements are in the flow.xml, you get output like 
> the following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
> {code}
> 2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> {code}
> The flow still seems to work so I think it's just a warning but still not 
> great to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Attachment: InvokeHttpMiNiFiTemplateTest.xml

> Need to add new RPG elements to FlowConfiguration.xsd
> -
>
> Key: NIFI-3138
> URL: https://issues.apache.org/jira/browse/NIFI-3138
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
> Attachments: InvokeHttpMiNiFiTemplateTest.xml
>
>
> There are new valid elements in the Remote Process Group portion of the 
> [standard flow serializer 
> xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
>   These are currently not part of the 
> [xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].
> This means that if these elements are in the flow.xml, you get output like 
> the following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
> {code}
> 2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> {code}
> The flow still seems to work so I think it's just a warning but still not 
> great to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3056) Update documentation/screenshots for color changes to icons for status (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3056:
--

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1269
  
nifi-toolbar-components.png also should not be replaced.  It is used to 
show a blank canvas, so with no processors, there is no need to update any 
colors. 


> Update documentation/screenshots for color changes to icons for status 
> (run/stop/alert, enabled/disabled, transmitting/not transmitting, etc.)
> --
>
> Key: NIFI-3056
> URL: https://issues.apache.org/jira/browse/NIFI-3056
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Priority: Minor
>
> In NIFI-3052, the iconRun, iconStop and iconAlert icons were replaced with 
> colored versions for the Admin Guide and Getting Started guide.   However, in 
> other docs like the User Guide these icons were referenced but not for 
> processor status, but for processor actions (Operate Palette and context menu 
> buttons/selections).  New screenshots should be created for the processor 
> actions.
> Other docs should also be looked at to update enabled/disabled and 
> transmitting/not transmitting screenshots per NIFI-2603. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1269: NIFI-3056 Updated User Guide screenshot and text with late...

2016-12-01 Thread andrewmlim

Github user andrewmlim commented on the issue:

https://github.com/apache/nifi/pull/1269
  
nifi-toolbar-components.png also should not be replaced.  It is used to 
show a blank canvas, so with no processors, there is no need to update any 
colors. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Description: 
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the 1.1.0 NiFi core libraries):
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.

  was:
There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the 1.1.0 NiFi core libraries:
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.


> Need to add new RPG elements to FlowConfiguration.xsd
> -
>
> Key:

[jira] [Updated] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)


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

Bryan Rosander updated NIFI-3138:
-
Priority: Minor  (was: Major)

> Need to add new RPG elements to FlowConfiguration.xsd
> -
>
> Key: NIFI-3138
> URL: https://issues.apache.org/jira/browse/NIFI-3138
> Project: Apache NiFi
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Bryan Rosander
>Priority: Minor
>
> There are new valid elements in the Remote Process Group portion of the 
> [standard flow serializer 
> xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
>   These are currently not part of the 
> [xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].
> This means that if these elements are in the flow.xml, you get output like 
> the following (from MiNiFi but it's using the 1.1.0 NiFi core libraries:
> {code}
> 2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> 2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
> org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: 
> Invalid content was found starting with element 'transportProtocol'. One of '{
> inputPort, outputPort}' is expected.
> {code}
> The flow still seems to work so I think it's just a warning but still not 
> great to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3138) Need to add new RPG elements to FlowConfiguration.xsd

2016-12-01 Thread Bryan Rosander (JIRA)

Bryan Rosander created NIFI-3138:


 Summary: Need to add new RPG elements to FlowConfiguration.xsd
 Key: NIFI-3138
 URL: https://issues.apache.org/jira/browse/NIFI-3138
 Project: Apache NiFi
  Issue Type: Bug
Affects Versions: 1.1.0
Reporter: Bryan Rosander


There are new valid elements in the Remote Process Group portion of the 
[standard flow serializer 
xml|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/serialization/StandardFlowSerializer.java#L253].
  These are currently not part of the 
[xsd|https://github.com/apache/nifi/blob/7eca2037bd602ecd2b26281d91ac3af9bc72a3f5/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/resources/FlowConfiguration.xsd#L200].

This means that if these elements are in the flow.xml, you get output like the 
following (from MiNiFi but it's using the 1.1.0 NiFi core libraries:
{code}
2016-12-01 19:22:24,850 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,890 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,909 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,927 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,974 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
2016-12-01 19:22:24,992 ERROR [MiNiFi logging handler] 
org.apache.nifi.minifi.StdErr [Error] :274:26: cvc-complex-type.2.4.a: Invalid 
content was found starting with element 'transportProtocol'. One of '{
inputPort, outputPort}' is expected.
{code}

The flow still seems to work so I think it's just a warning but still not great 
to see in the logs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread ASF GitHub Bot (JIRA)


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

ASF GitHub Bot commented on NIFI-3137:
--

GitHub user andrewmlim opened a pull request:

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

NIFI-3137 Add documentation for User Policies window



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

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

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

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






> Add documentation for User Policies window
> --
>
> Key: NIFI-3137
> URL: https://issues.apache.org/jira/browse/NIFI-3137
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi pull request #1286: NIFI-3137 Add documentation for User Policies windo...

2016-12-01 Thread andrewmlim

GitHub user andrewmlim opened a pull request:

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

NIFI-3137 Add documentation for User Policies window



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

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

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

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






---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (NIFI-2017) Root Group Port Transmission Icon is inaccurate

2016-12-01 Thread ASF subversion and git services (JIRA)


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

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

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

NIFI-2017 Fixing failing test PermissionBasedStatusMergerSpec.groovy introduced 
in previous commit


> Root Group Port Transmission Icon is inaccurate
> ---
>
> Key: NIFI-2017
> URL: https://issues.apache.org/jira/browse/NIFI-2017
> Project: Apache NiFi
>  Issue Type: Bug
>  Components: Core UI
>Reporter: Matt Gilman
>Assignee: Mark Payne
>Priority: Minor
> Fix For: 1.2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread Andrew Lim (JIRA)


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

Andrew Lim reassigned NIFI-3137:


Assignee: Andrew Lim

> Add documentation for User Policies window
> --
>
> Key: NIFI-3137
> URL: https://issues.apache.org/jira/browse/NIFI-3137
> Project: Apache NiFi
>  Issue Type: Improvement
>  Components: Documentation & Website
>Affects Versions: 1.1.0
>Reporter: Andrew Lim
>Assignee: Andrew Lim
>Priority: Minor
>
> User policies window added in 
> https://issues.apache.org/jira/browse/NIFI-2926.  Should add documentation 
> that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3137) Add documentation for User Policies window

2016-12-01 Thread Andrew Lim (JIRA)

Andrew Lim created NIFI-3137:


 Summary: Add documentation for User Policies window
 Key: NIFI-3137
 URL: https://issues.apache.org/jira/browse/NIFI-3137
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Affects Versions: 1.1.0
Reporter: Andrew Lim
Priority: Minor


User policies window added in https://issues.apache.org/jira/browse/NIFI-2926.  
Should add documentation that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (NIFI-3136) Add documentation for User Policies window

2016-12-01 Thread Andrew Lim (JIRA)

Andrew Lim created NIFI-3136:


 Summary: Add documentation for User Policies window
 Key: NIFI-3136
 URL: https://issues.apache.org/jira/browse/NIFI-3136
 Project: Apache NiFi
  Issue Type: Improvement
  Components: Documentation & Website
Affects Versions: 1.1.0
Reporter: Andrew Lim
Priority: Minor


User policies window added in https://issues.apache.org/jira/browse/NIFI-2926.  
Should add documentation that covers this functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[GitHub] nifi issue #1275: Add support for LDAPS

2016-12-01 Thread alopresto

Github user alopresto commented on the issue:

https://github.com/apache/nifi/pull/1275
  
Reviewing...


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

47 matches

Mail list logo