[GitHub] nifi pull request #3183: NIFI-5826 Fix to escaped backslash
Github user ijokarumawak commented on a diff in the pull request: https://github.com/apache/nifi/pull/3183#discussion_r238943337 --- Diff: nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java --- @@ -39,4 +39,52 @@ public static String getFirstStringValue(final RecordPathSegment segment, final return stringValue; } + +/** + * This method handles backslash sequences after ANTLR parser converts all backslash into double ones + * with exception for \t, \r and \n. See + * org/apache/nifi/record/path/RecordPathParser.g --- End diff -- @bdesert Thanks for sharing the example. I tried it out but result was different. I believe the content (attribute value) itself won't processed by the Lexer, so changing Lexer wouldn't affect that EL usages. Please look at #3200 for detail. I shared flow template and results. I hope I have set up the flow as you mentioned, but please let me know if I misunderstood! Providing generic util method such as `unescapeBackslash` is fine. But I think using it to address NIFI-5826 is not a good idea. As it would make just another confusion around how these actually work. @ottobackwards Agreed to add more unit tests and keep discussion going for both approaches with more examples. I created #3200 for comparison. ---
[jira] [Commented] (NIFI-5826) UpdateRecord processor throwing PatternSyntaxException
[
https://issues.apache.org/jira/browse/NIFI-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709658#comment-16709658
]
ASF GitHub Bot commented on NIFI-5826:
--
Github user ijokarumawak commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3183#discussion_r238943337
--- Diff:
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java
---
@@ -39,4 +39,52 @@ public static String getFirstStringValue(final
RecordPathSegment segment, final
return stringValue;
}
+
+/**
+ * This method handles backslash sequences after ANTLR parser converts
all backslash into double ones
+ * with exception for \t, \r and \n. See
+ * org/apache/nifi/record/path/RecordPathParser.g
--- End diff --
@bdesert Thanks for sharing the example. I tried it out but result was
different. I believe the content (attribute value) itself won't processed by
the Lexer, so changing Lexer wouldn't affect that EL usages. Please look at
#3200 for detail. I shared flow template and results. I hope I have set up the
flow as you mentioned, but please let me know if I misunderstood!
Providing generic util method such as `unescapeBackslash` is fine. But I
think using it to address NIFI-5826 is not a good idea. As it would make just
another confusion around how these actually work.
@ottobackwards Agreed to add more unit tests and keep discussion going for
both approaches with more examples. I created #3200 for comparison.
> UpdateRecord processor throwing PatternSyntaxException
> --
>
> Key: NIFI-5826
> URL: https://issues.apache.org/jira/browse/NIFI-5826
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Environment: Nifi in docker container
>Reporter: ravi kargam
>Assignee: Ed Berezitsky
>Priority: Minor
> Attachments: NIFI-5826_PR-3183.patch,
> UpdateRecord_Config_Exception.JPG
>
>
> with replacement value strategy as Record Path Value,
> I am trying to replace square bracket symbol *[* with parenthesis symbol *(*
> in my employeeName column in my csvReader structure with below syntax
> replaceRegex(/employeeName, "[\[]", "(")
> Processor is throwing following exception.
> RecordPathException: java.util.regex.PatternSyntaxException: Unclosed
> character class near index 4 [\\[]
> It worked fine with other special characters such as \{, }, <, >, ;, _, "
> For double qoute ("), i had to use single escape character, for above listed
> other characters, worked fine without any escape character. Other folks in
> Nifi Slack tried \s, \d, \w, \.
> looks like non of them worked.
> replace function worked for replacing [ and ]characters. didn't test any
> other characters.
> Please address resolve the issue.
> Regards,
> Ravi
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #3200: NIFI-5826 WIP Fix back-slash escaping at Lexers
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/3200
NIFI-5826 WIP Fix back-slash escaping at Lexers
## Summary
Current Lexers convert a back-slash plus another character sequence (e.g.
'\[') to double back-slash plus the next character (e.g. '\\[').
But from detailed analysis (see below), it seems the conversion is wrong
and it should leave such characters as it is.
## Details
I debugged how Lexer works, and found that:
- The `ESC` fragment handles an escaped special character in String
representation. I.e. String `\t` will be converted to actual tab character.
- The string values user input from NiFi UI are passed to
`RecordPath.compile` method as it is. E.g. the input string
`replaceRegex(/name, '\[', '')` is passed to as is, then the single back-slash
is converted to double back-slash by the ESC fragment line 155.
- I believe the line 153-156 is aimed to preserve escaped characters as it
is, because such escape doesn't mean anything for the RecordPath/AttrExpLang
spec. And those should be unescaped later by underlying syntaxes such as RegEx.
- And current line 155 does it wrongly. It should append a single
back-slash..
- Other Lexers (AttributeExpressionLexer.g and HL7QueryLexer.g) have
the same issue.
- So, I think we should fix all Lexers instead of adding another conversion.
Here is the [Lexer
code](https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record-path/src/main/antlr3/org/apache/nifi/record/path/RecordPathLexer.g#L143)
for reference:
```
143 fragment
144 ESC
145 : '\\'
146 (
147 '"'{ setText("\""); }
148 | '\'' { setText("\'"); }
149 | 'r' { setText("\r"); }
150 | 'n' { setText("\n"); }
151 | 't' { setText("\t"); }
152 | '\\' { setText(""); }
153 | nextChar = ~('"' | '\'' | 'r' | 'n' | 't' | '\\')
154{
155 StringBuilder lBuf = new StringBuilder();
lBuf.append("").appendCodePoint(nextChar); setText(lBuf.toString());
156}
157)
158 ;
```
## NiFi template for test
Here is a NiFi flow template to test how before/after this change.
https://gist.github.com/ijokarumawak/b6bdca8074a4457bc4a425b90a6b17f0
In order to try the template, you need to build this PR as NiFi
1.9.0-SNAPSHOT, then download following 1.8.0 nars in your SNAPSHOT's lib dir,
so that both versions can be used in the flow.
-
https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-standard-nar/1.8.0/nifi-standard-nar-1.8.0.nar
-
https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-update-attribute-nar/1.8.0/nifi-update-attribute-nar-1.8.0.nar
## Test result
### UpdateAttribute test for backward compatibility
GenerateFlowFile generates FlowFiles with attribute `a` whose value is:
```
this is new line
and this is just a backslash \n
```
Result
1.8.0
1.9.0-SNAPSHOT
### UpdateRecord test illustrating the NIFI-5826 issue is addressed
GenerateFlowFile generates content:
```
key,value
on[e,1
[two,2
```
Result
1.8.0
Regex compilation error as reported
1.9.0-SNAPSHOT
The square brackets are converted successfully
---
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
[jira] [Commented] (NIFI-5826) UpdateRecord processor throwing PatternSyntaxException
[
https://issues.apache.org/jira/browse/NIFI-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709651#comment-16709651
]
ASF GitHub Bot commented on NIFI-5826:
--
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/3200
NIFI-5826 WIP Fix back-slash escaping at Lexers
## Summary
Current Lexers convert a back-slash plus another character sequence (e.g.
'\[') to double back-slash plus the next character (e.g. '\\[').
But from detailed analysis (see below), it seems the conversion is wrong
and it should leave such characters as it is.
## Details
I debugged how Lexer works, and found that:
- The `ESC` fragment handles an escaped special character in String
representation. I.e. String `\t` will be converted to actual tab character.
- The string values user input from NiFi UI are passed to
`RecordPath.compile` method as it is. E.g. the input string
`replaceRegex(/name, '\[', '')` is passed to as is, then the single back-slash
is converted to double back-slash by the ESC fragment line 155.
- I believe the line 153-156 is aimed to preserve escaped characters as it
is, because such escape doesn't mean anything for the RecordPath/AttrExpLang
spec. And those should be unescaped later by underlying syntaxes such as RegEx.
- And current line 155 does it wrongly. It should append a single
back-slash..
- Other Lexers (AttributeExpressionLexer.g and HL7QueryLexer.g) have
the same issue.
- So, I think we should fix all Lexers instead of adding another conversion.
Here is the [Lexer
code](https://github.com/apache/nifi/blob/master/nifi-commons/nifi-record-path/src/main/antlr3/org/apache/nifi/record/path/RecordPathLexer.g#L143)
for reference:
```
143 fragment
144 ESC
145 : '\\'
146 (
147 '"'{ setText("\""); }
148 | '\'' { setText("\'"); }
149 | 'r' { setText("\r"); }
150 | 'n' { setText("\n"); }
151 | 't' { setText("\t"); }
152 | '\\' { setText(""); }
153 | nextChar = ~('"' | '\'' | 'r' | 'n' | 't' | '\\')
154{
155 StringBuilder lBuf = new StringBuilder();
lBuf.append("").appendCodePoint(nextChar); setText(lBuf.toString());
156}
157)
158 ;
```
## NiFi template for test
Here is a NiFi flow template to test how before/after this change.
https://gist.github.com/ijokarumawak/b6bdca8074a4457bc4a425b90a6b17f0
In order to try the template, you need to build this PR as NiFi
1.9.0-SNAPSHOT, then download following 1.8.0 nars in your SNAPSHOT's lib dir,
so that both versions can be used in the flow.
-
https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-standard-nar/1.8.0/nifi-standard-nar-1.8.0.nar
-
https://repo.maven.apache.org/maven2/org/apache/nifi/nifi-update-attribute-nar/1.8.0/nifi-update-attribute-nar-1.8.0.nar
## Test result
### UpdateAttribute test for backward compatibility
GenerateFlowFile generates FlowFiles with attribute `a` whose value is:
```
this is new line
and this is just a backslash \n
```
Result
1.8.0
1.9.0-SNAPSHOT
### UpdateRecord test illustrating the NIFI-5826 issue is addressed
GenerateFlowFile generates content:
```
key,value
on[e,1
[two,2
```
Result
1.8.0
Regex compilation error as reported
1.9.0-SNAPSHOT
The square brackets are converted successfully
---
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
[jira] [Updated] (NIFI-5863) Invalid logging in AbstractFlowFileQueue.java
[
https://issues.apache.org/jira/browse/NIFI-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-5863:
Status: Patch Available (was: Open)
> Invalid logging in AbstractFlowFileQueue.java
> -
>
> Key: NIFI-5863
> URL: https://issues.apache.org/jira/browse/NIFI-5863
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.8.0
>Reporter: Truong Duc Kien
>Assignee: Koji Kawamura
>Priority: Minor
>
> The variable \{{resultCount}} is never updated, so the logging message always
> report 0 results.
> https://github.com/apache/nifi/blob/234ddb0fe1a36ad947c340114058d82c777d791f/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/AbstractFlowFileQueue.java#L219
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709591#comment-16709591 ] Koji Kawamura commented on NIFI-4621: - JFYI, you can update the same PR even after squishing commits, by adding '-f' option when you push to your remote git branch. > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi-minifi pull request #148: MINIFI-482 Provide support for multiple URIs.
GitHub user apiri opened a pull request: https://github.com/apache/nifi-minifi/pull/148 MINIFI-482 Provide support for multiple URIs. Thank you for submitting a contribution to Apache NiFi - MiNiFi. 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 MINIFI- 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-minifi 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 minifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly? ### 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/apiri/nifi-minifi MINIFI-482 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/148.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 #148 commit 98976bcbd538ece2f813c68fe3ce7d811628cae1 Author: Aldrin Piri Date: 2018-12-04T22:27:57Z MINIFI-482 Provide support for multiple URIs. ---
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709492#comment-16709492 ] Kislay Kumar commented on NIFI-4621: I have made a mistake of having multiple commits in the PR. I will squash the commits and raise PR again. ETA 9 PM AEDT. > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kislay Kumar reopened NIFI-4621: > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi issue #3199: NIFI-5863 Fixed AbstractFlowFileQueue logging
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/3199 Example log output: ``` 2018-12-05 10:22:57,822 DEBUG [List FlowFiles for Connection 7bf5b85d-0167-1000-0fd3-42a79872] o.a.n.c.queue.AbstractFlowFileQueue org.apache.nifi.controller.queue.AbstractFlowFileQueue$1@4e4dd5ce Finished listing FlowFiles for active queue with a total of 100 results out of 1000 FlowFiles ``` ---
[jira] [Commented] (NIFI-5863) Invalid logging in AbstractFlowFileQueue.java
[
https://issues.apache.org/jira/browse/NIFI-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709499#comment-16709499
]
ASF GitHub Bot commented on NIFI-5863:
--
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/3199
Example log output:
```
2018-12-05 10:22:57,822 DEBUG [List FlowFiles for Connection
7bf5b85d-0167-1000-0fd3-42a79872] o.a.n.c.queue.AbstractFlowFileQueue
org.apache.nifi.controller.queue.AbstractFlowFileQueue$1@4e4dd5ce Finished
listing FlowFiles for active queue with a total of 100 results out of 1000
FlowFiles
```
> Invalid logging in AbstractFlowFileQueue.java
> -
>
> Key: NIFI-5863
> URL: https://issues.apache.org/jira/browse/NIFI-5863
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.8.0
>Reporter: Truong Duc Kien
>Assignee: Koji Kawamura
>Priority: Minor
>
> The variable \{{resultCount}} is never updated, so the logging message always
> report 0 results.
> https://github.com/apache/nifi/blob/234ddb0fe1a36ad947c340114058d82c777d791f/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/AbstractFlowFileQueue.java#L219
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-5863) Invalid logging in AbstractFlowFileQueue.java
[
https://issues.apache.org/jira/browse/NIFI-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709495#comment-16709495
]
ASF GitHub Bot commented on NIFI-5863:
--
GitHub user ijokarumawak opened a pull request:
https://github.com/apache/nifi/pull/3199
NIFI-5863 Fixed AbstractFlowFileQueue logging
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/ijokarumawak/nifi NIFI-5863
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/3199.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 #3199
commit cef667cb3c19f742ab27a8041532a0df406089c5
Author: Koji Kawamura
Date: 2018-12-05T01:23:57Z
NIFI-5863 Fixed AbstractFlowFileQueue logging
> Invalid logging in AbstractFlowFileQueue.java
> -
>
> Key: NIFI-5863
> URL: https://issues.apache.org/jira/browse/NIFI-5863
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.8.0
>Reporter: Truong Duc Kien
>Assignee: Koji Kawamura
>Priority: Minor
>
> The variable \{{resultCount}} is never updated, so the logging message always
> report 0 results.
> https://github.com/apache/nifi/blob/234ddb0fe1a36ad947c340114058d82c777d791f/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/AbstractFlowFileQueue.java#L219
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709493#comment-16709493 ] ASF GitHub Bot commented on NIFI-4621: -- Github user kislayom closed the pull request at: https://github.com/apache/nifi/pull/3197 > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3199: NIFI-5863 Fixed AbstractFlowFileQueue logging
GitHub user ijokarumawak opened a pull request: https://github.com/apache/nifi/pull/3199 NIFI-5863 Fixed AbstractFlowFileQueue logging 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/ijokarumawak/nifi NIFI-5863 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3199.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 #3199 commit cef667cb3c19f742ab27a8041532a0df406089c5 Author: Koji Kawamura Date: 2018-12-05T01:23:57Z NIFI-5863 Fixed AbstractFlowFileQueue logging ---
[GitHub] nifi pull request #3197: NIFI-4621
Github user kislayom closed the pull request at: https://github.com/apache/nifi/pull/3197 ---
[jira] [Assigned] (NIFI-5863) Invalid logging in AbstractFlowFileQueue.java
[
https://issues.apache.org/jira/browse/NIFI-5863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura reassigned NIFI-5863:
---
Assignee: Koji Kawamura
> Invalid logging in AbstractFlowFileQueue.java
> -
>
> Key: NIFI-5863
> URL: https://issues.apache.org/jira/browse/NIFI-5863
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.8.0
>Reporter: Truong Duc Kien
>Assignee: Koji Kawamura
>Priority: Minor
>
> The variable \{{resultCount}} is never updated, so the logging message always
> report 0 results.
> https://github.com/apache/nifi/blob/234ddb0fe1a36ad947c340114058d82c777d791f/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/AbstractFlowFileQueue.java#L219
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kislay Kumar reassigned NIFI-4621: -- Assignee: Kislay Kumar (was: Peter Wicks) > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3195: NIFI-5862 MockRecordParser Has Bad Logic for failAf...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/3195 ---
[jira] [Commented] (NIFI-5862) MockRecordParser Has Bad Logic for failAfterN
[ https://issues.apache.org/jira/browse/NIFI-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709480#comment-16709480 ] ASF subversion and git services commented on NIFI-5862: --- Commit 6c1c9017e98b8467296bc90746dab73a60cb9c1b in nifi's branch refs/heads/master from [~patricker] [ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=6c1c901 ] NIFI-5862 MockRecordParser Has Bad Logic for failAfterN This closes #3195. Signed-off-by: Koji Kawamura > MockRecordParser Has Bad Logic for failAfterN > - > > Key: NIFI-5862 > URL: https://issues.apache.org/jira/browse/NIFI-5862 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Wicks >Assignee: Peter Wicks >Priority: Minor > Fix For: 1.9.0 > > > `MockRecordParser` has a function that allows it to throw an exception after > a certain number of records have been read. This feature is not working at > all, and instead the reader fails immediately without reading any records. > None of the test cases check for how many records were read, so you can only > see this in the console, for example on `TestSplitRecord.testReadFailure`: > As Is: `Intentional Unit Test Exception because 0 records have been read` > As Should Be: `Intentional Unit Test Exception because 2 records have been > read` > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5862) MockRecordParser Has Bad Logic for failAfterN
[ https://issues.apache.org/jira/browse/NIFI-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709481#comment-16709481 ] ASF GitHub Bot commented on NIFI-5862: -- Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/3195 > MockRecordParser Has Bad Logic for failAfterN > - > > Key: NIFI-5862 > URL: https://issues.apache.org/jira/browse/NIFI-5862 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Wicks >Assignee: Peter Wicks >Priority: Minor > Fix For: 1.9.0 > > > `MockRecordParser` has a function that allows it to throw an exception after > a certain number of records have been read. This feature is not working at > all, and instead the reader fails immediately without reading any records. > None of the test cases check for how many records were read, so you can only > see this in the console, for example on `TestSplitRecord.testReadFailure`: > As Is: `Intentional Unit Test Exception because 0 records have been read` > As Should Be: `Intentional Unit Test Exception because 2 records have been > read` > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (NIFI-5862) MockRecordParser Has Bad Logic for failAfterN
[ https://issues.apache.org/jira/browse/NIFI-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Koji Kawamura resolved NIFI-5862. - Resolution: Fixed Fix Version/s: 1.9.0 > MockRecordParser Has Bad Logic for failAfterN > - > > Key: NIFI-5862 > URL: https://issues.apache.org/jira/browse/NIFI-5862 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Wicks >Assignee: Peter Wicks >Priority: Minor > Fix For: 1.9.0 > > > `MockRecordParser` has a function that allows it to throw an exception after > a certain number of records have been read. This feature is not working at > all, and instead the reader fails immediately without reading any records. > None of the test cases check for how many records were read, so you can only > see this in the console, for example on `TestSplitRecord.testReadFailure`: > As Is: `Intentional Unit Test Exception because 0 records have been read` > As Should Be: `Intentional Unit Test Exception because 2 records have been > read` > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5862) MockRecordParser Has Bad Logic for failAfterN
[ https://issues.apache.org/jira/browse/NIFI-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709478#comment-16709478 ] ASF GitHub Bot commented on NIFI-5862: -- Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/3195 Thanks @patricker good catch! +1 merging to master. > MockRecordParser Has Bad Logic for failAfterN > - > > Key: NIFI-5862 > URL: https://issues.apache.org/jira/browse/NIFI-5862 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Wicks >Assignee: Peter Wicks >Priority: Minor > > `MockRecordParser` has a function that allows it to throw an exception after > a certain number of records have been read. This feature is not working at > all, and instead the reader fails immediately without reading any records. > None of the test cases check for how many records were read, so you can only > see this in the console, for example on `TestSplitRecord.testReadFailure`: > As Is: `Intentional Unit Test Exception because 0 records have been read` > As Should Be: `Intentional Unit Test Exception because 2 records have been > read` > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi issue #3195: NIFI-5862 MockRecordParser Has Bad Logic for failAfterN
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/3195 Thanks @patricker good catch! +1 merging to master. ---
[jira] [Commented] (NIFI-5838) Misconfigured Kite processors can block NiFi
[
https://issues.apache.org/jira/browse/NIFI-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709470#comment-16709470
]
ASF GitHub Bot commented on NIFI-5838:
--
Github user asfgit closed the pull request at:
https://github.com/apache/nifi/pull/3182
> Misconfigured Kite processors can block NiFi
>
>
> Key: NIFI-5838
> URL: https://issues.apache.org/jira/browse/NIFI-5838
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Critical
> Fix For: 1.9.0
>
>
> I faced the following situation today: no way to access the NiFi UI (it was
> just hanging forever or throwing timeouts), no change in case of NiFi
> restart, even with disabling the auto resume feature.
> By looking at the thread dump, I found a lot of:
> {noformat}
> "NiFi Web Server-142" Id=142 BLOCKED on
> org.apache.hadoop.ipc.Client$Connection@3843e7a6
> at org.apache.hadoop.ipc.Client$Connection.addCall(Client.java:463)
> at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:375)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1522)
> at org.apache.hadoop.ipc.Client.call(Client.java:1451)
> at org.apache.hadoop.ipc.Client.call(Client.java:1412)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy348.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getBlockLocations(ClientNamenodeProtocolTranslatorPB.java:255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:191)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy349.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.DFSClient.callGetBlockLocations(DFSClient.java:1226)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1213)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1201)
> at
> org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:306)
> at org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:272)
> - waiting on java.lang.Object@46d84263
> at org.apache.hadoop.hdfs.DFSInputStream.(DFSInputStream.java:264)
> at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1526)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:304)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:299)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:312)
> at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:769)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor.getSchema(AbstractKiteProcessor.java:132)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor$3.validate(AbstractKiteProcessor.java:172)
> at
> org.apache.nifi.components.PropertyDescriptor.validate(PropertyDescriptor.java:200)
> at
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:103)
> at
> org.apache.nifi.controller.AbstractConfiguredComponent.validate(AbstractConfiguredComponent.java:329)
> at
> org.apache.nifi.controller.StandardProcessorNode.isValid(StandardProcessorNode.java:968)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:227)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.getSiteToSiteDetails(StandardNiFiServiceFacade.java:2609)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
> at
>
[jira] [Updated] (NIFI-5838) Misconfigured Kite processors can block NiFi
[
https://issues.apache.org/jira/browse/NIFI-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koji Kawamura updated NIFI-5838:
Resolution: Fixed
Fix Version/s: 1.9.0
Status: Resolved (was: Patch Available)
> Misconfigured Kite processors can block NiFi
>
>
> Key: NIFI-5838
> URL: https://issues.apache.org/jira/browse/NIFI-5838
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Critical
> Fix For: 1.9.0
>
>
> I faced the following situation today: no way to access the NiFi UI (it was
> just hanging forever or throwing timeouts), no change in case of NiFi
> restart, even with disabling the auto resume feature.
> By looking at the thread dump, I found a lot of:
> {noformat}
> "NiFi Web Server-142" Id=142 BLOCKED on
> org.apache.hadoop.ipc.Client$Connection@3843e7a6
> at org.apache.hadoop.ipc.Client$Connection.addCall(Client.java:463)
> at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:375)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1522)
> at org.apache.hadoop.ipc.Client.call(Client.java:1451)
> at org.apache.hadoop.ipc.Client.call(Client.java:1412)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy348.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getBlockLocations(ClientNamenodeProtocolTranslatorPB.java:255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:191)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy349.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.DFSClient.callGetBlockLocations(DFSClient.java:1226)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1213)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1201)
> at
> org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:306)
> at org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:272)
> - waiting on java.lang.Object@46d84263
> at org.apache.hadoop.hdfs.DFSInputStream.(DFSInputStream.java:264)
> at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1526)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:304)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:299)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:312)
> at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:769)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor.getSchema(AbstractKiteProcessor.java:132)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor$3.validate(AbstractKiteProcessor.java:172)
> at
> org.apache.nifi.components.PropertyDescriptor.validate(PropertyDescriptor.java:200)
> at
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:103)
> at
> org.apache.nifi.controller.AbstractConfiguredComponent.validate(AbstractConfiguredComponent.java:329)
> at
> org.apache.nifi.controller.StandardProcessorNode.isValid(StandardProcessorNode.java:968)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:227)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.getSiteToSiteDetails(StandardNiFiServiceFacade.java:2609)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
> at
> org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204)
> at
> org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:720)
> at
>
[GitHub] nifi pull request #3182: NIFI-5838 - Improve the schema validation method in...
Github user asfgit closed the pull request at: https://github.com/apache/nifi/pull/3182 ---
[jira] [Commented] (NIFI-5838) Misconfigured Kite processors can block NiFi
[
https://issues.apache.org/jira/browse/NIFI-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709469#comment-16709469
]
ASF subversion and git services commented on NIFI-5838:
---
Commit 986a2a484285a342e20494107abe52ff98ad2880 in nifi's branch
refs/heads/master from [~pvillard]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=986a2a4 ]
NIFI-5838 - Improve the schema validation method in Kite processors
review
Add empty check
This closes #3182.
Signed-off-by: Koji Kawamura
> Misconfigured Kite processors can block NiFi
>
>
> Key: NIFI-5838
> URL: https://issues.apache.org/jira/browse/NIFI-5838
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Critical
>
> I faced the following situation today: no way to access the NiFi UI (it was
> just hanging forever or throwing timeouts), no change in case of NiFi
> restart, even with disabling the auto resume feature.
> By looking at the thread dump, I found a lot of:
> {noformat}
> "NiFi Web Server-142" Id=142 BLOCKED on
> org.apache.hadoop.ipc.Client$Connection@3843e7a6
> at org.apache.hadoop.ipc.Client$Connection.addCall(Client.java:463)
> at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:375)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1522)
> at org.apache.hadoop.ipc.Client.call(Client.java:1451)
> at org.apache.hadoop.ipc.Client.call(Client.java:1412)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy348.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getBlockLocations(ClientNamenodeProtocolTranslatorPB.java:255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:191)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy349.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.DFSClient.callGetBlockLocations(DFSClient.java:1226)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1213)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1201)
> at
> org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:306)
> at org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:272)
> - waiting on java.lang.Object@46d84263
> at org.apache.hadoop.hdfs.DFSInputStream.(DFSInputStream.java:264)
> at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1526)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:304)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:299)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:312)
> at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:769)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor.getSchema(AbstractKiteProcessor.java:132)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor$3.validate(AbstractKiteProcessor.java:172)
> at
> org.apache.nifi.components.PropertyDescriptor.validate(PropertyDescriptor.java:200)
> at
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:103)
> at
> org.apache.nifi.controller.AbstractConfiguredComponent.validate(AbstractConfiguredComponent.java:329)
> at
> org.apache.nifi.controller.StandardProcessorNode.isValid(StandardProcessorNode.java:968)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:227)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.getSiteToSiteDetails(StandardNiFiServiceFacade.java:2609)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade$$FastClassBySpringCGLIB$$358780e0.invoke()
> at
>
[jira] [Commented] (NIFI-5838) Misconfigured Kite processors can block NiFi
[
https://issues.apache.org/jira/browse/NIFI-5838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709458#comment-16709458
]
ASF GitHub Bot commented on NIFI-5838:
--
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/3182
Thanks @pvillard31 for confirming that. I'm +1 and going to merge this.
Please update [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
to note about this behavioral change. A section title like "Migrating from
1.x.x to 1.9.0 (under development, not released yet, subject to be changed)"
would be nice.
> Misconfigured Kite processors can block NiFi
>
>
> Key: NIFI-5838
> URL: https://issues.apache.org/jira/browse/NIFI-5838
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Critical
>
> I faced the following situation today: no way to access the NiFi UI (it was
> just hanging forever or throwing timeouts), no change in case of NiFi
> restart, even with disabling the auto resume feature.
> By looking at the thread dump, I found a lot of:
> {noformat}
> "NiFi Web Server-142" Id=142 BLOCKED on
> org.apache.hadoop.ipc.Client$Connection@3843e7a6
> at org.apache.hadoop.ipc.Client$Connection.addCall(Client.java:463)
> at org.apache.hadoop.ipc.Client$Connection.access$2800(Client.java:375)
> at org.apache.hadoop.ipc.Client.getConnection(Client.java:1522)
> at org.apache.hadoop.ipc.Client.call(Client.java:1451)
> at org.apache.hadoop.ipc.Client.call(Client.java:1412)
> at
> org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:229)
> at com.sun.proxy.$Proxy348.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB.getBlockLocations(ClientNamenodeProtocolTranslatorPB.java:255)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invokeMethod(RetryInvocationHandler.java:191)
> at
> org.apache.hadoop.io.retry.RetryInvocationHandler.invoke(RetryInvocationHandler.java:102)
> at com.sun.proxy.$Proxy349.getBlockLocations(Unknown Source)
> at
> org.apache.hadoop.hdfs.DFSClient.callGetBlockLocations(DFSClient.java:1226)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1213)
> at org.apache.hadoop.hdfs.DFSClient.getLocatedBlocks(DFSClient.java:1201)
> at
> org.apache.hadoop.hdfs.DFSInputStream.fetchLocatedBlocksAndGetLastBlockLength(DFSInputStream.java:306)
> at org.apache.hadoop.hdfs.DFSInputStream.openInfo(DFSInputStream.java:272)
> - waiting on java.lang.Object@46d84263
> at org.apache.hadoop.hdfs.DFSInputStream.(DFSInputStream.java:264)
> at org.apache.hadoop.hdfs.DFSClient.open(DFSClient.java:1526)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:304)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem$3.doCall(DistributedFileSystem.java:299)
> at
> org.apache.hadoop.fs.FileSystemLinkResolver.resolve(FileSystemLinkResolver.java:81)
> at
> org.apache.hadoop.hdfs.DistributedFileSystem.open(DistributedFileSystem.java:312)
> at org.apache.hadoop.fs.FileSystem.open(FileSystem.java:769)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor.getSchema(AbstractKiteProcessor.java:132)
> at
> org.apache.nifi.processors.kite.AbstractKiteProcessor$3.validate(AbstractKiteProcessor.java:172)
> at
> org.apache.nifi.components.PropertyDescriptor.validate(PropertyDescriptor.java:200)
> at
> org.apache.nifi.components.AbstractConfigurableComponent.validate(AbstractConfigurableComponent.java:103)
> at
> org.apache.nifi.controller.AbstractConfiguredComponent.validate(AbstractConfiguredComponent.java:329)
> at
> org.apache.nifi.controller.StandardProcessorNode.isValid(StandardProcessorNode.java:968)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:227)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.groups.StandardProcessGroup.getCounts(StandardProcessGroup.java:261)
> at
> org.apache.nifi.web.StandardNiFiServiceFacade.getSiteToSiteDetails(StandardNiFiServiceFacade.java:2609)
> at
>
[GitHub] nifi issue #3182: NIFI-5838 - Improve the schema validation method in Kite p...
Github user ijokarumawak commented on the issue: https://github.com/apache/nifi/pull/3182 Thanks @pvillard31 for confirming that. I'm +1 and going to merge this. Please update [Migration Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance) to note about this behavioral change. A section title like "Migrating from 1.x.x to 1.9.0 (under development, not released yet, subject to be changed)" would be nice. ---
[jira] [Updated] (NIFI-5869) JMS Connection Fails After JMS servers Change behind JNDI
[ https://issues.apache.org/jira/browse/NIFI-5869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ed Berezitsky updated NIFI-5869: Description: JMS Connection Fails After JMS servers Change behind JNDI. Reproduce: # Define and enable JNDI Controller Service # Create a flow with ConsumeJMS or PublishJMS processors with controller service defined in #1. # Consume and publish at least one message to ensure the connectivity can be established. # Change JNDI configuration for the same connection factory to point to new JMS servers. # Stop JMS service on previous servers # Observe failure in ConsumeJMS/PublishJMS (Caused by: javax.jms.JMSException: Failed to connect to any server at: tcp://jms_server1:12345) Work Around: # Disable JNDI Controller Service # Enable JNDI Controller Service and dependent processors. Possible Issue/Fix: * AbstractJMSProcessor has a method "buildTargetResource", in which connection factory is instantiated and then cached in workerPool in onTrigger . * Issue: Once cached, it will be reused forever. * Fix: on connectivity failure there should be an attempt to rebuild the worker. was: JMS Connection Fails After JMS servers Change behind JNDI. Reproduce: # Define and enable JNDI Controller Service # Create a flow with ConsumeJMS or PublishJMS processors with controller service defined in #1. # Consume and publish at least one message to ensure the connectivity can be established. # Change JNDI configuration for the same connection factory to point to new JMS servers. # Stop JMS service on previous servers # Observe failure in ConsumeJMS/PublishJMS (Caused by: javax.jms.JMSException: Failed to connect to any server at: tcp://jms_server1:12345) Work Around: # Disable JNDI Controller Service # Enable JNDI Controller Service and dependent processors. Possible Issue/Fix: * AbstractJMSProcessor has a method "buildTargetResource", in which connection factory in instantiated and then cached in workerPool in onTrigger . * Issues: Once cached, it will be reused forever. * Fix: on connectivity failure there should be an attempt to rebuild the worker. > JMS Connection Fails After JMS servers Change behind JNDI > - > > Key: NIFI-5869 > URL: https://issues.apache.org/jira/browse/NIFI-5869 > Project: Apache NiFi > Issue Type: Bug > Components: Extensions >Affects Versions: 1.8.0 >Reporter: Ed Berezitsky >Assignee: Ed Berezitsky >Priority: Major > Fix For: 1.8.0 > > Attachments: JNDI_JMS_Exception.txt > > > JMS Connection Fails After JMS servers Change behind JNDI. > Reproduce: > # Define and enable JNDI Controller Service > # Create a flow with ConsumeJMS or PublishJMS processors with controller > service defined in #1. > # Consume and publish at least one message to ensure the connectivity can be > established. > # Change JNDI configuration for the same connection factory to point to new > JMS servers. > # Stop JMS service on previous servers > # Observe failure in ConsumeJMS/PublishJMS (Caused by: > javax.jms.JMSException: Failed to connect to any server at: > tcp://jms_server1:12345) > > Work Around: > # Disable JNDI Controller Service > # Enable JNDI Controller Service and dependent processors. > > Possible Issue/Fix: > * AbstractJMSProcessor has a method "buildTargetResource", in which > connection factory is instantiated and then cached in workerPool in onTrigger > . > * Issue: Once cached, it will be reused forever. > * Fix: on connectivity failure there should be an attempt to rebuild the > worker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5869) JMS Connection Fails After JMS servers Change behind JNDI
Ed Berezitsky created NIFI-5869: --- Summary: JMS Connection Fails After JMS servers Change behind JNDI Key: NIFI-5869 URL: https://issues.apache.org/jira/browse/NIFI-5869 Project: Apache NiFi Issue Type: Bug Components: Extensions Affects Versions: 1.8.0 Reporter: Ed Berezitsky Assignee: Ed Berezitsky Fix For: 1.8.0 Attachments: JNDI_JMS_Exception.txt JMS Connection Fails After JMS servers Change behind JNDI. Reproduce: # Define and enable JNDI Controller Service # Create a flow with ConsumeJMS or PublishJMS processors with controller service defined in #1. # Consume and publish at least one message to ensure the connectivity can be established. # Change JNDI configuration for the same connection factory to point to new JMS servers. # Stop JMS service on previous servers # Observe failure in ConsumeJMS/PublishJMS (Caused by: javax.jms.JMSException: Failed to connect to any server at: tcp://jms_server1:12345) Work Around: # Disable JNDI Controller Service # Enable JNDI Controller Service and dependent processors. Possible Issue/Fix: * AbstractJMSProcessor has a method "buildTargetResource", in which connection factory in instantiated and then cached in workerPool in onTrigger . * Issues: Once cached, it will be reused forever. * Fix: on connectivity failure there should be an attempt to rebuild the worker. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5868) Instrument robust timing information for ListFile
Mark Payne created NIFI-5868: Summary: Instrument robust timing information for ListFile Key: NIFI-5868 URL: https://issues.apache.org/jira/browse/NIFI-5868 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Mark Payne Assignee: Mark Payne ListFile is used in many different contexts. We often see users with a specific use case, though, which is to run ListFile on a Primary Node in a cluster, in order to obtain a file listing of an NFS-mounted share. This works well in most cases, but whenever problems do arise, it is very difficult to understand what the problem is. It would be very helpful to have information such as: * Is there a problem accessing a specific file on the NFS mount? * Is there a problem obtaining a listing from the NFS mount? * Is progress being made at all? * How long is a listing taking right now? * How long does a listing typically take? * Is this problem related to NiFi or to the operating system / infrastructure? It would be helpful to track information about each disk access that is occurring, as well as the overall listing progress and issue warnings if we see clear problems arise. We can do this by timing how long each disk access takes, what file was being accessed, and what operating was being performed. If we capture this data in a rolling window, we can assess the data to determine if the listing is now taking longer than it did previously and alert to this fact. Or alert if performing a specific disk operation is taking a long time. Gathering this information will likely be fairly heap intensive, so it is best to make the functionality optional. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5867) Add EL function to get thread name
[
https://issues.apache.org/jira/browse/NIFI-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709282#comment-16709282
]
ASF GitHub Bot commented on NIFI-5867:
--
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3198#discussion_r238848651
--- Diff:
nifi-commons/nifi-expression-language/src/main/java/org/apache/nifi/attribute/expression/language/evaluation/functions/ThreadEvaluator.java
---
@@ -0,0 +1,45 @@
+/*
+ * 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.attribute.expression.language.evaluation.functions;
+
+import java.util.Map;
+
+import org.apache.nifi.attribute.expression.language.evaluation.Evaluator;
+import
org.apache.nifi.attribute.expression.language.evaluation.QueryResult;
+import
org.apache.nifi.attribute.expression.language.evaluation.StringEvaluator;
+import
org.apache.nifi.attribute.expression.language.evaluation.StringQueryResult;
+
+public class ThreadEvaluator extends StringEvaluator {
+
+private final StringQueryResult thread;
+
+public ThreadEvaluator() {
+// See org.apache.nifi.engine.FlowEngine
+thread = new StringQueryResult(Thread.currentThread().getName());
--- End diff --
I think this needs to happen in the #evaluate method. As-is, a call to
${thread()} will result in returning the name of whatever thread created this
Evaluator, and this may not be the same thread in which it's invoked.
> Add EL function to get thread name
> --
>
> Key: NIFI-5867
> URL: https://issues.apache.org/jira/browse/NIFI-5867
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Extensions
>Reporter: Pierre Villard
>Assignee: Pierre Villard
>Priority: Major
>
> Add an Expression Language function to get the thread name doing the
> expression evaluation. This can be useful in case a processor is configured
> with multiple concurrent tasks and requires some data uniqueness.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #3198: NIFI-5867 - add thread() EL function to get thread ...
Github user markap14 commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3198#discussion_r238848651
--- Diff:
nifi-commons/nifi-expression-language/src/main/java/org/apache/nifi/attribute/expression/language/evaluation/functions/ThreadEvaluator.java
---
@@ -0,0 +1,45 @@
+/*
+ * 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.attribute.expression.language.evaluation.functions;
+
+import java.util.Map;
+
+import org.apache.nifi.attribute.expression.language.evaluation.Evaluator;
+import
org.apache.nifi.attribute.expression.language.evaluation.QueryResult;
+import
org.apache.nifi.attribute.expression.language.evaluation.StringEvaluator;
+import
org.apache.nifi.attribute.expression.language.evaluation.StringQueryResult;
+
+public class ThreadEvaluator extends StringEvaluator {
+
+private final StringQueryResult thread;
+
+public ThreadEvaluator() {
+// See org.apache.nifi.engine.FlowEngine
+thread = new StringQueryResult(Thread.currentThread().getName());
--- End diff --
I think this needs to happen in the #evaluate method. As-is, a call to
${thread()} will result in returning the name of whatever thread created this
Evaluator, and this may not be the same thread in which it's invoked.
---
[jira] [Updated] (NIFI-5867) Add EL function to get thread name
[ https://issues.apache.org/jira/browse/NIFI-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard updated NIFI-5867: - Status: Patch Available (was: Open) > Add EL function to get thread name > -- > > Key: NIFI-5867 > URL: https://issues.apache.org/jira/browse/NIFI-5867 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > > Add an Expression Language function to get the thread name doing the > expression evaluation. This can be useful in case a processor is configured > with multiple concurrent tasks and requires some data uniqueness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5867) Add EL function to get thread name
[ https://issues.apache.org/jira/browse/NIFI-5867?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709272#comment-16709272 ] ASF GitHub Bot commented on NIFI-5867: -- GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/3198 NIFI-5867 - add thread() EL function to get thread name 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/pvillard31/nifi thread-id Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3198.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 #3198 commit aa48caacac303b6d418796e3025f9756fc7f0458 Author: Pierre Villard Date: 2018-12-04T21:28:33Z NIFI-5867 - add thread() EL function to get thread name > Add EL function to get thread name > -- > > Key: NIFI-5867 > URL: https://issues.apache.org/jira/browse/NIFI-5867 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: Pierre Villard >Assignee: Pierre Villard >Priority: Major > > Add an Expression Language function to get the thread name doing the > expression evaluation. This can be useful in case a processor is configured > with multiple concurrent tasks and requires some data uniqueness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3198: NIFI-5867 - add thread() EL function to get thread ...
GitHub user pvillard31 opened a pull request: https://github.com/apache/nifi/pull/3198 NIFI-5867 - add thread() EL function to get thread name 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/pvillard31/nifi thread-id Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3198.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 #3198 commit aa48caacac303b6d418796e3025f9756fc7f0458 Author: Pierre Villard Date: 2018-12-04T21:28:33Z NIFI-5867 - add thread() EL function to get thread name ---
[jira] [Created] (NIFI-5867) Add EL function to get thread name
Pierre Villard created NIFI-5867: Summary: Add EL function to get thread name Key: NIFI-5867 URL: https://issues.apache.org/jira/browse/NIFI-5867 Project: Apache NiFi Issue Type: New Feature Components: Extensions Reporter: Pierre Villard Assignee: Pierre Villard Add an Expression Language function to get the thread name doing the expression evaluation. This can be useful in case a processor is configured with multiple concurrent tasks and requires some data uniqueness. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Comment: was deleted (was: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: login-identity-providers.xml) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: users.xml) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: nifi.properties) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Issue Comment Deleted] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Comment: was deleted (was: I don't use this one : nifi01.admin.local I use nifi01.mintopsblog.local and it's already in /etc/Hosts !!) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Description: (was: I have this Error : org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: authorizers.xml) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: login-identity-providers.xml, nifi.properties, users.xml > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: authorizations.xml) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: login-identity-providers.xml, nifi.properties, users.xml > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5830) RedisConnectionPoolService does not work with Standalone Redis using non-localhost deployment
[
https://issues.apache.org/jira/browse/NIFI-5830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16709213#comment-16709213
]
ASF GitHub Bot commented on NIFI-5830:
--
Github user javajefe commented on the issue:
https://github.com/apache/nifi/pull/3176
Done!
However, I see Travis-CI build failed and I can't believe that's because of
my PR (the problem is in org.apache.nifi.dbcp.DBCPServiceTest and it looks like
an integration test rather than unit test, anyway there is no relation between
DBCPService and RedisUtils)
> RedisConnectionPoolService does not work with Standalone Redis using
> non-localhost deployment
> -
>
> Key: NIFI-5830
> URL: https://issues.apache.org/jira/browse/NIFI-5830
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.8.0
> Environment: Ubuntu 16 LTS, NiFi 1.8.0
>Reporter: Alexander Bukarev
>Priority: Major
>
> The controller service {{RedisConnectionPoolService}} does not work with
> Standalone Redis which is deployed on a host other than {{localhost}} (or if
> Redis uses the port other than {{6379}}). So the only way to use
> {{RedisConnectionPoolService}} is to deploy Redis on {{localhost}} and run it
> with default port {{6379}}.
> *Steps*:
> Let's assume our Redis is deployed on host *redis* (not {{localhost}}) and it
> listens port 6379 (I use docker for that)
> # Create a {{PutDistributedMapCache}} processor
> # Configure the processor with {{RedisDistributedMapCacheClientService}}
> # Create a new controller service: {{RedisConnectionPoolService}}
> #* Choose *Standalone* Redis Mode
> #* Use *redis:6379* as a Connection String
> # Connect some incoming flow to the {{PutDistributedMapCache}} processor
> (I've used {{GetFile}} as a producer) and run the whole flow. Allow
> {{GetFile}} to consume some file (if you use {{GetFile}} ro reproduce) and
> wait some time till the {{PutDistributedMapCache}} will be schedulled.
> Result:
> The processor is failed to run. And we can see the error in logs:
> {panel}2018-11-17 06:06:47,572 WARN [Timer-Driven Process Thread-2]
> o.a.n.controller.tasks.ConnectableTask Administratively Yielding PutDistribu
> tedMapCache[id=2041c81f-0167-1000-c82f-d7da2155dfb4] due to uncaught
> Exception: org.springframework.data.redis.RedisConnectionFailureExce
> ption: Cannot get Jedis connection; nested exception is
> redis.clients.jedis.exceptions.JedisConnectionException: Could not get a
> resource
> from the pool
> org.springframework.data.redis.RedisConnectionFailureException: Cannot get
> Jedis connection; nested exception is
> redis.clients.jedis.exceptions.JedisConnectionException: Could not get a
> resource from the pool
> at
> org.springframework.data.redis.connection.jedis.JedisConnectionFactory.fetchJedisConnector(JedisConnectionFactory.java:281)
> at
> org.springframework.data.redis.connection.jedis.JedisConnectionFactory.getConnection(JedisConnectionFactory.java:464)
> at
> org.apache.nifi.redis.service.RedisConnectionPoolService.getConnection(RedisConnectionPoolService.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:84)
> at com.sun.proxy.$Proxy128.getConnection(Unknown Source)
> at
> org.apache.nifi.redis.service.RedisDistributedMapCacheClientService.withConnection(RedisDistributedMapCacheClientService.java:343)
> at
> org.apache.nifi.redis.service.RedisDistributedMapCacheClientService.put(RedisDistributedMapCacheClientService.java:189)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.apache.nifi.controller.service.StandardControllerServiceInvocationHandler.invoke(StandardControllerServiceInvocationHandler.java:84)
> at com.sun.proxy.$Proxy124.put(Unknown Source)
> at
> org.apache.nifi.processors.standard.PutDistributedMapCache.onTrigger(PutDistributedMapCache.java:202){panel}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi issue #3176: NIFI-5830 RedisConnectionPoolService does not work with St...
Github user javajefe commented on the issue: https://github.com/apache/nifi/pull/3176 Done! However, I see Travis-CI build failed and I can't believe that's because of my PR (the problem is in org.apache.nifi.dbcp.DBCPServiceTest and it looks like an integration test rather than unit test, anyway there is no relation between DBCPService and RedisUtils) ---
[jira] [Updated] (NIFI-5866) Cluster gets out of sync: "X is not the most up-to-date revision."
[ https://issues.apache.org/jira/browse/NIFI-5866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Gresock updated NIFI-5866: - Attachment: Error.png > Cluster gets out of sync: "X is not the most up-to-date revision." > -- > > Key: NIFI-5866 > URL: https://issues.apache.org/jira/browse/NIFI-5866 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.6.0 > Environment: CentOS 6.9, NiFi 1.6.0 cluster of 4, running on AWS EC2 > VMs. >Reporter: Joseph Gresock >Priority: Major > Attachments: Error.png > > > Since upgrading to 1.6.0, I have started to see this error sometimes when I > try to modify a component (start, stop, configure, move, etc.): > > Node X is unable to fulfill this request due to: [12, , uuid>] is not the most up-to-date revision. This component appears to have > been modified. > > The only way I have found to resolve this is to disconnect and then delete > the node from the cluster, then try again, repeating the process until the > flow can be modified. Afterwards, I have to stop nifi on the disconnected > nodes, delete their flow.xml.gz, and let them rejoin the cluster with a fresh > copy of the flow. > > This sometimes happens multiple times per day. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (NIFI-5866) Cluster gets out of sync: "X is not the most up-to-date revision."
Joseph Gresock created NIFI-5866: Summary: Cluster gets out of sync: "X is not the most up-to-date revision." Key: NIFI-5866 URL: https://issues.apache.org/jira/browse/NIFI-5866 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.6.0 Environment: CentOS 6.9, NiFi 1.6.0 cluster of 4, running on AWS EC2 VMs. Reporter: Joseph Gresock Since upgrading to 1.6.0, I have started to see this error sometimes when I try to modify a component (start, stop, configure, move, etc.): Node X is unable to fulfill this request due to: [12, , ] is not the most up-to-date revision. This component appears to have been modified. The only way I have found to resolve this is to disconnect and then delete the node from the cluster, then try again, repeating the process until the flow can be modified. Afterwards, I have to stop nifi on the disconnected nodes, delete their flow.xml.gz, and let them rejoin the cluster with a fresh copy of the flow. This sometimes happens multiple times per day. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi-minifi pull request #147: MINIFI-483: Adding Ubuntu 16/18 as supported ...
GitHub user jzonthemtn opened a pull request: https://github.com/apache/nifi-minifi/pull/147 MINIFI-483: Adding Ubuntu 16/18 as supported on guide. Thank you for submitting a contribution to Apache NiFi - MiNiFi. 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: - [ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi-minifi 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 minifi-assembly? - [ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under minifi-assembly? ### 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/jzonthemtn/nifi-minifi MINIFI-483 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi-minifi/pull/147.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 #147 commit 7ca902dbbbf8d6fd3b3cb84a2555f4c94734e04d Author: jzonthemtn Date: 2018-12-04T16:40:12Z MINIFI-483: Adding Ubuntu 16/18 as supported on guide. ---
[jira] [Commented] (NIFI-3229) When a queue contains only Penalized FlowFile's the next processor Tasks/Time statistics becomes extremely large
[ https://issues.apache.org/jira/browse/NIFI-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708944#comment-16708944 ] Nicholas Carenza commented on NIFI-3229: What's next for this? > When a queue contains only Penalized FlowFile's the next processor Tasks/Time > statistics becomes extremely large > > > Key: NIFI-3229 > URL: https://issues.apache.org/jira/browse/NIFI-3229 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Dmitry Lukyanov >Assignee: Peter Wicks >Priority: Minor > Attachments: flow.xml.gz, nifi-stats.png, nifi-stats2.png > > > fetchfile on `not.found` produces penalized flow file > in this case i'm expecting the next processor will do one task execution when > flow file penalize time over. > but according to stats it executes approximately 1-6 times. > i understand that it could be a feature but stats became really unclear... > maybe there should be two columns? > `All Task/Times` and `Committed Task/Times` -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-5826) UpdateRecord processor throwing PatternSyntaxException
[
https://issues.apache.org/jira/browse/NIFI-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708743#comment-16708743
]
ASF GitHub Bot commented on NIFI-5826:
--
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3183#discussion_r238675752
--- Diff:
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java
---
@@ -39,4 +39,52 @@ public static String getFirstStringValue(final
RecordPathSegment segment, final
return stringValue;
}
+
+/**
+ * This method handles backslash sequences after ANTLR parser converts
all backslash into double ones
+ * with exception for \t, \r and \n. See
+ * org/apache/nifi/record/path/RecordPathParser.g
--- End diff --
Such discussion would solicit input from other experienced contributors as
well.
> UpdateRecord processor throwing PatternSyntaxException
> --
>
> Key: NIFI-5826
> URL: https://issues.apache.org/jira/browse/NIFI-5826
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Environment: Nifi in docker container
>Reporter: ravi kargam
>Assignee: Ed Berezitsky
>Priority: Minor
> Attachments: NIFI-5826_PR-3183.patch,
> UpdateRecord_Config_Exception.JPG
>
>
> with replacement value strategy as Record Path Value,
> I am trying to replace square bracket symbol *[* with parenthesis symbol *(*
> in my employeeName column in my csvReader structure with below syntax
> replaceRegex(/employeeName, "[\[]", "(")
> Processor is throwing following exception.
> RecordPathException: java.util.regex.PatternSyntaxException: Unclosed
> character class near index 4 [\\[]
> It worked fine with other special characters such as \{, }, <, >, ;, _, "
> For double qoute ("), i had to use single escape character, for above listed
> other characters, worked fine without any escape character. Other folks in
> Nifi Slack tried \s, \d, \w, \.
> looks like non of them worked.
> replace function worked for replacing [ and ]characters. didn't test any
> other characters.
> Please address resolve the issue.
> Regards,
> Ravi
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #3183: NIFI-5826 Fix to escaped backslash
Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/nifi/pull/3183#discussion_r238675406 --- Diff: nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java --- @@ -39,4 +39,52 @@ public static String getFirstStringValue(final RecordPathSegment segment, final return stringValue; } + +/** + * This method handles backslash sequences after ANTLR parser converts all backslash into double ones + * with exception for \t, \r and \n. See + * org/apache/nifi/record/path/RecordPathParser.g --- End diff -- What would help, is one or more clear, failing unit tests against the current code that illustrate the problem. We have regex escape routines in more than one place, some for places without grammars ( replace text). Where we _do_ have a grammar, the correct thing, or the preferred thing in a vacuum would be to have the grammar handle this. It is centralized and more maintainable. We may want to evaluate the regression as a community, based on the fix and the implications wrt maintainability and correctness. I would almost say that we would want to have discussion and review of both approaches. That would be my preference. ---
[GitHub] nifi pull request #3183: NIFI-5826 Fix to escaped backslash
Github user ottobackwards commented on a diff in the pull request: https://github.com/apache/nifi/pull/3183#discussion_r238675752 --- Diff: nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java --- @@ -39,4 +39,52 @@ public static String getFirstStringValue(final RecordPathSegment segment, final return stringValue; } + +/** + * This method handles backslash sequences after ANTLR parser converts all backslash into double ones + * with exception for \t, \r and \n. See + * org/apache/nifi/record/path/RecordPathParser.g --- End diff -- Such discussion would solicit input from other experienced contributors as well. ---
[jira] [Commented] (NIFI-5826) UpdateRecord processor throwing PatternSyntaxException
[
https://issues.apache.org/jira/browse/NIFI-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708742#comment-16708742
]
ASF GitHub Bot commented on NIFI-5826:
--
Github user ottobackwards commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3183#discussion_r238675406
--- Diff:
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java
---
@@ -39,4 +39,52 @@ public static String getFirstStringValue(final
RecordPathSegment segment, final
return stringValue;
}
+
+/**
+ * This method handles backslash sequences after ANTLR parser converts
all backslash into double ones
+ * with exception for \t, \r and \n. See
+ * org/apache/nifi/record/path/RecordPathParser.g
--- End diff --
What would help, is one or more clear, failing unit tests against the
current code that illustrate the problem.
We have regex escape routines in more than one place, some for places
without grammars ( replace text). Where we _do_ have a grammar, the correct
thing, or the preferred thing in a vacuum would be to have the grammar handle
this. It is centralized and more maintainable. We may want to evaluate the
regression as a community, based on the fix and the implications wrt
maintainability and correctness.
I would almost say that we would want to have discussion and review of both
approaches.
That would be my preference.
> UpdateRecord processor throwing PatternSyntaxException
> --
>
> Key: NIFI-5826
> URL: https://issues.apache.org/jira/browse/NIFI-5826
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Environment: Nifi in docker container
>Reporter: ravi kargam
>Assignee: Ed Berezitsky
>Priority: Minor
> Attachments: NIFI-5826_PR-3183.patch,
> UpdateRecord_Config_Exception.JPG
>
>
> with replacement value strategy as Record Path Value,
> I am trying to replace square bracket symbol *[* with parenthesis symbol *(*
> in my employeeName column in my csvReader structure with below syntax
> replaceRegex(/employeeName, "[\[]", "(")
> Processor is throwing following exception.
> RecordPathException: java.util.regex.PatternSyntaxException: Unclosed
> character class near index 4 [\\[]
> It worked fine with other special characters such as \{, }, <, >, ;, _, "
> For double qoute ("), i had to use single escape character, for above listed
> other characters, worked fine without any escape character. Other folks in
> Nifi Slack tried \s, \d, \w, \.
> looks like non of them worked.
> replace function worked for replacing [ and ]characters. didn't test any
> other characters.
> Please address resolve the issue.
> Regards,
> Ravi
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708678#comment-16708678 ] Kislay Kumar edited comment on NIFI-4621 at 12/4/18 1:35 PM: - Code changes complete, please review. [https://github.com/apache/nifi/pull/3197] was (Author: kislayom): Code changes please review. https://github.com/apache/nifi/pull/3197 > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Peter Wicks >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kislay Kumar reassigned NIFI-4621: -- Assignee: Peter Wicks (was: Kislay Kumar) > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Peter Wicks >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kislay Kumar resolved NIFI-4621. Resolution: Fixed Fix Version/s: 1.9.0 Code changes please review. https://github.com/apache/nifi/pull/3197 > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > Fix For: 1.9.0 > > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708677#comment-16708677 ] ASF GitHub Bot commented on NIFI-4621: -- GitHub user kislayom opened a pull request: https://github.com/apache/nifi/pull/3197 NIFI-4621 NIFI-4621 changes in processor ListSFTP and ListFTP to also have input connection and expression language for properties. 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? - [ ] 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/kislayom/nifi NIFI-4621 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3197.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 #3197 commit 0512754739cf63785aebfc53a89bb75d37bacbed Author: Kislay Kumar Date: 2018-12-04T12:03:56Z NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from other processors, also validated the explression language is working for properties of both the processors. commit 9da3a8700244b4fdc06c634805bbc0b25369623a Author: Kislay Kumar Date: 2018-12-04T13:05:34Z NIFI-4621 changes in processor ListSFTP and ListFTP to also have input connection and expression language for properties > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3197: NIFI-4621
GitHub user kislayom opened a pull request: https://github.com/apache/nifi/pull/3197 NIFI-4621 NIFI-4621 changes in processor ListSFTP and ListFTP to also have input connection and expression language for properties. 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? - [ ] 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/kislayom/nifi NIFI-4621 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3197.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 #3197 commit 0512754739cf63785aebfc53a89bb75d37bacbed Author: Kislay Kumar Date: 2018-12-04T12:03:56Z NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from other processors, also validated the explression language is working for properties of both the processors. commit 9da3a8700244b4fdc06c634805bbc0b25369623a Author: Kislay Kumar Date: 2018-12-04T13:05:34Z NIFI-4621 changes in processor ListSFTP and ListFTP to also have input connection and expression language for properties ---
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708646#comment-16708646 ] ASF GitHub Bot commented on NIFI-4621: -- Github user kislayom closed the pull request at: https://github.com/apache/nifi/pull/3196 > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3196: NIFI-4621 Enable ListSFTP and ListFTP processor to ...
Github user kislayom closed the pull request at: https://github.com/apache/nifi/pull/3196 ---
[jira] [Commented] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708644#comment-16708644 ] ASF GitHub Bot commented on NIFI-4621: -- GitHub user kislayom opened a pull request: https://github.com/apache/nifi/pull/3196 NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection … Modifed ListSftp and ListFtp processors so they can accept connection from other processors, also validated the expression language is working for properties of both the processors. This is for NIFI-4621. 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/kislayom/nifi NIFI-4621 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3196.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 #3196 commit 0512754739cf63785aebfc53a89bb75d37bacbed Author: Kislay Kumar Date: 2018-12-04T12:03:56Z NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from other processors, also validated the explression language is working for properties of both the processors. > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] nifi pull request #3196: NIFI-4621 Enable ListSFTP and ListFTP processor to ...
GitHub user kislayom opened a pull request: https://github.com/apache/nifi/pull/3196 NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection ⦠Modifed ListSftp and ListFtp processors so they can accept connection from other processors, also validated the expression language is working for properties of both the processors. This is for NIFI-4621. 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/kislayom/nifi NIFI-4621 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/nifi/pull/3196.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 #3196 commit 0512754739cf63785aebfc53a89bb75d37bacbed Author: Kislay Kumar Date: 2018-12-04T12:03:56Z NIFI-4621 Enable ListSFTP and ListFTP processor to accept connection from other processors, also validated the explression language is working for properties of both the processors. ---
[jira] [Commented] (NIFI-5826) UpdateRecord processor throwing PatternSyntaxException
[
https://issues.apache.org/jira/browse/NIFI-5826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708637#comment-16708637
]
ASF GitHub Bot commented on NIFI-5826:
--
Github user bdesert commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3183#discussion_r238642945
--- Diff:
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java
---
@@ -39,4 +39,52 @@ public static String getFirstStringValue(final
RecordPathSegment segment, final
return stringValue;
}
+
+/**
+ * This method handles backslash sequences after ANTLR parser converts
all backslash into double ones
+ * with exception for \t, \r and \n. See
+ * org/apache/nifi/record/path/RecordPathParser.g
--- End diff --
@ijokarumawak ,
I understand what you are talking about, that was my first idea as well.
the problem is coming with regression on WORKING functionality, like EL.
If we change Lexer in all three cases, we will have a problem of backward
compatibility.
As an example: define GFF with attribute "a1" having value (with actual new
line):
```
"this is new line
and this is just a backslash \n"
```
(doesn't matter with quotes or w/o).
next: UpdateAttribute with:
`a1: "${a:replaceAll('\\n','_')}"`
and
`a2: "${a:replaceAll('\n','_')}"`
(note single and double backslash)
In both cases the only character that will be replaced will be actual new
line, resulting in:
`a1=a2="this is new line_and this is just a backslash \n"
`
If we change Lexer for EL, this will be changed and will behave differently
and will result in:
`a1 = "his is new line`
and this is just a backslash _"
`a2 = "his is new line_and this is just a backslash \n"`
Of course, we can do "right" way for RecordPath regex-based functions, but
then we will have different user experience with regex in RecordPath and EL,
which I think should be avoided.
Regarding Java method "unescapeBackslash". As a name suggests, this
function it to treat string values having "backslash" in their values. I do
agree that for the test cases we have, some parts of the code are dead, but
since this is public method in utility class, it can have generic functionality
to support wider varieties of the use cases.
Would appreciate your feedback!
> UpdateRecord processor throwing PatternSyntaxException
> --
>
> Key: NIFI-5826
> URL: https://issues.apache.org/jira/browse/NIFI-5826
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
>Affects Versions: 1.5.0, 1.6.0, 1.7.0, 1.8.0, 1.7.1
> Environment: Nifi in docker container
>Reporter: ravi kargam
>Assignee: Ed Berezitsky
>Priority: Minor
> Attachments: NIFI-5826_PR-3183.patch,
> UpdateRecord_Config_Exception.JPG
>
>
> with replacement value strategy as Record Path Value,
> I am trying to replace square bracket symbol *[* with parenthesis symbol *(*
> in my employeeName column in my csvReader structure with below syntax
> replaceRegex(/employeeName, "[\[]", "(")
> Processor is throwing following exception.
> RecordPathException: java.util.regex.PatternSyntaxException: Unclosed
> character class near index 4 [\\[]
> It worked fine with other special characters such as \{, }, <, >, ;, _, "
> For double qoute ("), i had to use single escape character, for above listed
> other characters, worked fine without any escape character. Other folks in
> Nifi Slack tried \s, \d, \w, \.
> looks like non of them worked.
> replace function worked for replacing [ and ]characters. didn't test any
> other characters.
> Please address resolve the issue.
> Regards,
> Ravi
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi pull request #3183: NIFI-5826 Fix to escaped backslash
Github user bdesert commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3183#discussion_r238642945
--- Diff:
nifi-commons/nifi-record-path/src/main/java/org/apache/nifi/record/path/util/RecordPathUtils.java
---
@@ -39,4 +39,52 @@ public static String getFirstStringValue(final
RecordPathSegment segment, final
return stringValue;
}
+
+/**
+ * This method handles backslash sequences after ANTLR parser converts
all backslash into double ones
+ * with exception for \t, \r and \n. See
+ * org/apache/nifi/record/path/RecordPathParser.g
--- End diff --
@ijokarumawak ,
I understand what you are talking about, that was my first idea as well.
the problem is coming with regression on WORKING functionality, like EL.
If we change Lexer in all three cases, we will have a problem of backward
compatibility.
As an example: define GFF with attribute "a1" having value (with actual new
line):
```
"this is new line
and this is just a backslash \n"
```
(doesn't matter with quotes or w/o).
next: UpdateAttribute with:
`a1: "${a:replaceAll('\\n','_')}"`
and
`a2: "${a:replaceAll('\n','_')}"`
(note single and double backslash)
In both cases the only character that will be replaced will be actual new
line, resulting in:
`a1=a2="this is new line_and this is just a backslash \n"
`
If we change Lexer for EL, this will be changed and will behave differently
and will result in:
`a1 = "his is new line`
and this is just a backslash _"
`a2 = "his is new line_and this is just a backslash \n"`
Of course, we can do "right" way for RecordPath regex-based functions, but
then we will have different user experience with regex in RecordPath and EL,
which I think should be avoided.
Regarding Java method "unescapeBackslash". As a name suggests, this
function it to treat string values having "backslash" in their values. I do
agree that for the test cases we have, some parts of the code are dead, but
since this is public method in utility class, it can have generic functionality
to support wider varieties of the use cases.
Would appreciate your feedback!
---
[jira] [Comment Edited] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16706078#comment-16706078 ] Kislay Kumar edited comment on NIFI-4621 at 12/4/18 11:56 AM: -- [~patricker] : I should be able to commit in 3 days. Currently I am assessing impact on ListFTP because both ListFTP and ListSFTP implements similar functionality. Would you suggest I implement similar changes for ListFTP as well. Personally I am inclined to modify ListFTP also. was (Author: kislayom): [~patricker] : I should be able to commit in 3 days. Currently I am assessing impact on ListFTP because both ListFTP and ListSFTP extends ListFileTransfer. Would you suggest I implement similar changes for ListFTP as well. Personally I am inclined to modify ListFTP also. > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (NIFI-4621) Allow inputs to ListSFTP and ListFTP
[ https://issues.apache.org/jira/browse/NIFI-4621?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kislay Kumar updated NIFI-4621: --- Summary: Allow inputs to ListSFTP and ListFTP (was: Allow inputs to ListSFTP) > Allow inputs to ListSFTP and ListFTP > > > Key: NIFI-4621 > URL: https://issues.apache.org/jira/browse/NIFI-4621 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.4.0 >Reporter: Soumya Shanta Ghosh >Assignee: Kislay Kumar >Priority: Critical > > ListSFTP supports listing of the supplied directory (Remote Path) > out-of-the-box on the supplied "Hostname" using the 'Username" and 'Password" > / "Private Key Passphrase". > The password can change at a regular interval (depending on organization > policy) or the Hostname or the Remote Path can change based on some other > requirement. > This is a case to allow ListSFTP to leverage the use of Nifi Expression > language so that the values of Hostname, Password and/or Remote Path can be > set based on the attributes of an incoming flow file. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINIFICPP-404) HTTP Proxy Support for HTTP Site to Site
[
https://issues.apache.org/jira/browse/MINIFICPP-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708591#comment-16708591
]
ASF GitHub Bot commented on MINIFICPP-404:
--
Github user arpadboda commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/454#discussion_r238631364
--- Diff: libminifi/src/core/yaml/YamlConfiguration.cpp ---
@@ -325,6 +325,12 @@ void
YamlConfiguration::parseRemoteProcessGroupYaml(YAML::Node *rpgNode, core::P
}
}
}
+ } else if (transport_protocol == "RAW") {
+group->setTransportProtocol(transport_protocol);
+ } else {
+std::stringstream stream;
+stream << "Invalid transport protocol " << transport_protocol;
+throw minifi::Exception(ExceptionType::SITE2SITE_EXCEPTION,
stream.str().c_str());
--- End diff --
This is fine, however makes me wonder why don't we have string param ctr.
for minifi::Exception as we convert to the const char* to string anyway in the
current ctr.
> HTTP Proxy Support for HTTP Site to Site
>
>
> Key: MINIFICPP-404
> URL: https://issues.apache.org/jira/browse/MINIFICPP-404
> Project: NiFi MiNiFi C++
> Issue Type: Improvement
>Affects Versions: 0.6.0
>Reporter: bqiu
>Assignee: Mr TheSegfault
>Priority: Minor
> Fix For: 0.6.0
>
>
> HTTP Proxy Support for HTTP Site to Site
> http://nifi.apache.org/docs/nifi-docs/html/user-guide.html#configure-site-to-site-client-nifi-instance.
> support for this in YAML config via
> https://github.com/apache/nifi-minifi/blob/master/minifi-docs/src/main/markdown/System_Admin_Guide.md#remote-process-groups-1.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] nifi-minifi-cpp pull request #454: MINIFICPP-404: Correct invalid assumption...
Github user arpadboda commented on a diff in the pull request:
https://github.com/apache/nifi-minifi-cpp/pull/454#discussion_r238631364
--- Diff: libminifi/src/core/yaml/YamlConfiguration.cpp ---
@@ -325,6 +325,12 @@ void
YamlConfiguration::parseRemoteProcessGroupYaml(YAML::Node *rpgNode, core::P
}
}
}
+ } else if (transport_protocol == "RAW") {
+group->setTransportProtocol(transport_protocol);
+ } else {
+std::stringstream stream;
+stream << "Invalid transport protocol " << transport_protocol;
+throw minifi::Exception(ExceptionType::SITE2SITE_EXCEPTION,
stream.str().c_str());
--- End diff --
This is fine, however makes me wonder why don't we have string param ctr.
for minifi::Exception as we convert to the const char* to string anyway in the
current ctr.
---
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[
https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708569#comment-16708569
]
Pierre Villard commented on NIFI-5865:
--
{noformat}Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'authorizer': FactoryBean threw exception on
object creation; nested exception is
org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - No Such
Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error
code 32 - No Such Object]; remaining name 'DC=abc,DC=local'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3179){noformat}
What you're setting in your authorizers.xml file does not match what you have
in your LDAP/AD.
> Secure Nifi LDAP
>
>
> Key: NIFI-5865
> URL: https://issues.apache.org/jira/browse/NIFI-5865
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.8.0
>Reporter: Firdaous hebbal
>Priority: Major
> Attachments: authorizations.xml, authorizers.xml,
> login-identity-providers.xml, nifi.properties, users.xml
>
>
> I have this Error :
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
> Unsatisfied dependency expressed through method
> 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
> org.springframework.beans.factory.BeanExpressionException: Expression parsing
> failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.BeanExpressionException:
> Expression parsing failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708528#comment-16708528 ] Pierre Villard commented on NIFI-5865: -- I'm just reading the logs you shared in the JIRA. If you changed the host in your authorizers.xml file, please share the new logs when you start NiFi. > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708533#comment-16708533 ] Firdaous hebbal commented on NIFI-5865: --- org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708526#comment-16708526 ] Firdaous hebbal commented on NIFI-5865: --- I don't use this one : nifi01.admin.local I use nifi01.mintopsblog.local and it's already in /etc/Hosts !! > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException:
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: (was: authorizers.xml) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: authorizers.xml > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name
[jira] [Issue Comment Deleted] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Comment: was deleted (was: in /etc/Hosts : 172.22.2.60 nifi01.mintopsblog.local) > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by:
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708485#comment-16708485 ] Firdaous hebbal commented on NIFI-5865: --- in /etc/Hosts : 172.22.2.60 nifi01.mintopsblog.local > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by:
[jira] [Commented] (NIFI-5865) Secure Nifi LDAP
[
https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16708442#comment-16708442
]
Pierre Villard commented on NIFI-5865:
--
You have:
{{Root exception is java.net.UnknownHostException: nifi01.admin.local}}
Sounds like the host is not resolvable. Can you double check this part?
> Secure Nifi LDAP
>
>
> Key: NIFI-5865
> URL: https://issues.apache.org/jira/browse/NIFI-5865
> Project: Apache NiFi
> Issue Type: Bug
>Affects Versions: 1.8.0
>Reporter: Firdaous hebbal
>Priority: Major
> Attachments: authorizations.xml, authorizers.xml,
> login-identity-providers.xml, nifi.properties, users.xml
>
>
> I have this Error :
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration':
> Unsatisfied dependency expressed through method
> 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is
> org.springframework.beans.factory.BeanExpressionException: Expression parsing
> failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.BeanExpressionException:
> Expression parsing failed; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException:
> Error creating bean with name
> 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency
> expressed through method 'setJwtAuthenticationProvider' parameter 0; nested
> exception is org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception
> is java.net.UnknownHostException: nifi01.admin.local]
> Caused by: org.springframework.beans.factory.BeanCreationException: Error
> creating bean with name 'jwtAuthenticationProvider' defined in class path
> resource [nifi-web-security-context.xml]: Cannot resolve reference to bean
> 'authorizer' while setting constructor argument; nested exception is
> org.springframework.beans.factory.BeanCreationException: Error creating bean
> with name 'authorizer': FactoryBean threw exception on object creation;
> nested exception is org.springframework.ldap.CommunicationException:
> nifi01.admin.local:389; nested exception is
> javax.naming.CommunicationException: nifi01.admin.local:389 [Root
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Affects Version/s: 1.8.0 > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.8.0 >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name
[jira] [Created] (NIFI-5865) Secure Nifi LDAP
Firdaous hebbal created NIFI-5865: - Summary: Secure Nifi LDAP Key: NIFI-5865 URL: https://issues.apache.org/jira/browse/NIFI-5865 Project: Apache NiFi Issue Type: Bug Reporter: Firdaous hebbal I have this Error : org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': Unsatisfied dependency expressed through method 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanExpressionException: Expression parsing failed; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency expressed through method 'setJwtAuthenticationProvider' parameter 0; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'jwtAuthenticationProvider' defined in class path resource [nifi-web-security-context.xml]: Cannot resolve reference to bean 'authorizer' while setting constructor argument; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.springframework.ldap.CommunicationException: nifi01.admin.local:389; nested exception is javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception is java.net.UnknownHostException: nifi01.admin.local] org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name
[jira] [Updated] (NIFI-5865) Secure Nifi LDAP
[ https://issues.apache.org/jira/browse/NIFI-5865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Firdaous hebbal updated NIFI-5865: -- Attachment: users.xml nifi.properties login-identity-providers.xml authorizers.xml authorizations.xml > Secure Nifi LDAP > > > Key: NIFI-5865 > URL: https://issues.apache.org/jira/browse/NIFI-5865 > Project: Apache NiFi > Issue Type: Bug >Reporter: Firdaous hebbal >Priority: Major > Attachments: authorizations.xml, authorizers.xml, > login-identity-providers.xml, nifi.properties, users.xml > > > I have this Error : > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.springframework.security.config.annotation.web.configuration.WebSecurityConfiguration': > Unsatisfied dependency expressed through method > 'setFilterChainProxySecurityConfigurer' parameter 1; nested exception is > org.springframework.beans.factory.BeanExpressionException: Expression parsing > failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanExpressionException: > Expression parsing failed; nested exception is > org.springframework.beans.factory.UnsatisfiedDependencyException: Error > creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.UnsatisfiedDependencyException: > Error creating bean with name > 'org.apache.nifi.web.NiFiWebApiSecurityConfiguration': Unsatisfied dependency > expressed through method 'setJwtAuthenticationProvider' parameter 0; nested > exception is org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException: nifi01.admin.local] > Caused by: org.springframework.beans.factory.BeanCreationException: Error > creating bean with name 'jwtAuthenticationProvider' defined in class path > resource [nifi-web-security-context.xml]: Cannot resolve reference to bean > 'authorizer' while setting constructor argument; nested exception is > org.springframework.beans.factory.BeanCreationException: Error creating bean > with name 'authorizer': FactoryBean threw exception on object creation; > nested exception is org.springframework.ldap.CommunicationException: > nifi01.admin.local:389; nested exception is > javax.naming.CommunicationException: nifi01.admin.local:389 [Root exception > is java.net.UnknownHostException:
[jira] [Created] (NIFI-5864) Incorrect drainedSize calculation in SwappablePriorityQueue
Truong Duc Kien created NIFI-5864:
-
Summary: Incorrect drainedSize calculation in
SwappablePriorityQueue
Key: NIFI-5864
URL: https://issues.apache.org/jira/browse/NIFI-5864
Project: Apache NiFi
Issue Type: Bug
Affects Versions: 1.8.0
Reporter: Truong Duc Kien
When the size of {{expiredRecords}} is equal to
{{MAX_EXPIRED_RECORDS_PER_ITERATION}}, the loop break early and {{drainSized}}
will not include the last record.
https://github.com/apache/nifi/blob/5561c29ed3b8c635f499582e983a5147cb06e306/nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-framework-core/src/main/java/org/apache/nifi/controller/queue/SwappablePriorityQueue.java#L650
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
