[jira] [Resolved] (NIFI-12495) Update the NiFi website to a new design
[ https://issues.apache.org/jira/browse/NIFI-12495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12495. - Assignee: James Elliott Resolution: Fixed > Update the NiFi website to a new design > --- > > Key: NIFI-12495 > URL: https://issues.apache.org/jira/browse/NIFI-12495 > Project: Apache NiFi > Issue Type: Improvement > Components: Documentation & Website >Reporter: James Elliott >Assignee: James Elliott >Priority: Minor > Labels: docuentation, newbie > Time Spent: 2h > Remaining Estimate: 0h > > Continuation of work started by [~exceptionfactory] to update the design of > the NiFi website. > * Replace Foundation with UIkit > * Remove fontawesome > * Simplify navigation between NiFi and MiNiFi subproject > * Major styling updates -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12495 Initial commit of new design [nifi-site]
exceptionfactory commented on PR #78: URL: https://github.com/apache/nifi-site/pull/78#issuecomment-1865444945 Merged to main-staging branch in https://github.com/apache/nifi-site/commit/f0c2a4babe93c5202b0027aea37974e1814758b7 The staging website is available at https://nifi.staged.apache.org -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12495 Initial commit of new design [nifi-site]
exceptionfactory closed pull request #78: NIFI-12495 Initial commit of new design URL: https://github.com/apache/nifi-site/pull/78 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799245#comment-17799245
]
David Handermann commented on NIFI-12513:
-
Thanks for the reminder and reference [~dstiegli1].
Can you provide an example of what the Regular Expression would like look?
There is the potential for edge cases, but at least providing an example here
would help evaluate the potential complexity.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] NIFI-12485: Lineage Graph [nifi]
mcgilman commented on PR #8173: URL: https://github.com/apache/nifi/pull/8173#issuecomment-1865420475 Thanks for the review @rfellows! I've addressed the items you've mentioned and fixed the rendering issues as well. Please have a look at the latest commit. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799239#comment-17799239
]
Daniel Stieglitz commented on NIFI-12513:
-
[~exceptionfactory] As I demonstrated above when broken into its parts the
constructor with seven arguments does not behave like URI.create(String). This
same issue is what I believe we solved in NIFI-10754 using the NIFI Expression
Language.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:09 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoded) as
the Javadoc uses the word "quoted".
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:08 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799237#comment-17799237
]
David Handermann commented on NIFI-12513:
-
According to the documentation for
[java.net.URI|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]
the constructor builds a string and then passes it to the {{URI(String)}}
constructor, which is the same behavior as calling {{URI.create(String)}}.
{quote}
The resulting URI string is then parsed as if by invoking the URI(String)
constructor and then invoking the parseServerAuthority() method upon the
result; this may cause a URISyntaxException to be thrown.
{quote}
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:06 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:07 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??
8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:07 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??
8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:03 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:01 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799235#comment-17799235
]
Daniel Stieglitz commented on NIFI-12513:
-
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799221#comment-17799221
]
David Handermann commented on NIFI-12513:
-
[~dstiegli1] On further review, parsing the component parts and passing them to
alternative constructors does not look like it would resolve the fundamental
problem. Are you suggested that some other encoding could be perform on the
path or query elements after separating them?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tan Luu updated NIFI-12402: --- Labels: patch-available (was: ) Status: Patch Available (was: Open) > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.24.0 >Reporter: Tan Luu >Priority: Minor > Labels: patch-available > Time Spent: 50m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tan Luu updated NIFI-12402: --- Affects Version/s: 1.24.0 (was: 1.23.2) > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.24.0 >Reporter: Tan Luu >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12485: Lineage Graph [nifi]
mcgilman commented on code in PR #8173:
URL: https://github.com/apache/nifi/pull/8173#discussion_r1433243825
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/provenance/ui/provenance-event-listing/provenance-event-table/provenance-event-table.component.html:
##
@@ -15,142 +15,184 @@
~ limitations under the License.
-->
-
-
-Displaying {{ filteredCount }} of {{
totalCount }}
-
-
-Oldest event available: {{
oldestEventAvailable }}
-
-
-{{ resultsMessage }}
-Clear
Search
+
+
+
+Displaying {{ filteredCount }} of {{
totalCount }}
Review Comment:
Good call. Will update.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12485: Lineage Graph [nifi]
mcgilman commented on code in PR #8173:
URL: https://github.com/apache/nifi/pull/8173#discussion_r1433235981
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/provenance/ui/provenance-event-listing/provenance-event-table/provenance-event-table.component.ts:
##
@@ -77,16 +86,69 @@ export class ProvenanceEventTable implements AfterViewInit {
if (filterTerm?.length > 0) {
const filterColumn =
this.filterForm.get('filterColumn')?.value;
this.applyFilter(filterTerm, filterColumn);
+} else {
+this.resetPaginator();
}
}
}
@Input() oldestEventAvailable!: string;
+@Input() timeOffset!: number;
@Input() resultsMessage!: string;
@Input() hasRequest!: boolean;
+@Input() loading!: boolean;
+@Input() loadedTimestamp!: string;
+@Input() set lineage$(lineage$: Observable) {
+this.provenanceLineage$ = lineage$.pipe(
+tap((lineage) => {
+let minMillis: number = -1;
+let maxMillis: number = -1;
+
+lineage?.results.nodes.forEach((node) => {
+// ensure this event has an event time
+if (minMillis < 0 || minMillis > node.millis) {
+minMillis = node.millis;
+// minTimestamp = node.timestamp;
Review Comment:
Yup!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[jira] [Commented] (NIFI-11570) Processors have difficulty restoring dynamic properties when leaving ghost mode
[ https://issues.apache.org/jira/browse/NIFI-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799193#comment-17799193 ] David Handermann commented on NIFI-11570: - Thanks for the additional discussion [~Nissim Shiman] and [~bbende]. Summarizing some direct conversation with [~Nissim Shiman], one option could be using the propertyDescriptors, but only populating sensitive dynamic property names and setting the sensitive flag. This would keep the size of flow.json scoped down, but potentially provide a way to persist the sensitive dynamic properties explicitly without having to change the model itself. I'm not sure offhand about the potential tradeoffs of such an approach. Tagging [~markap14] for additional perspective as this is an important implementation to get right, and it is better to evaluate the options before getting to a pull request that could involve significant changes in direction. > Processors have difficulty restoring dynamic properties when leaving ghost > mode > --- > > Key: NIFI-11570 > URL: https://issues.apache.org/jira/browse/NIFI-11570 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.19.1 >Reporter: Nissim Shiman >Assignee: Nissim Shiman >Priority: Major > > When a processor with non sensitive dynamic properties is started in ghost > mode due to its underlying nar being missing, it will have a difficult time > being restored even when its nar has been replaced. > The dynamic properties will be identified as being sensitive and not able to > be accessed. > So for example, if a dynamic property added to GenerateFlowFile and > nifi-standard-nar is removed from lib and nifi is restarted, GenerateFlowFile > will come up in ghosted mode (as expected). > When nifi-standard-nar is replaced and nifi is restarted, GenerateFlowFile > will be restored, but its dynamic property will not be accessable. > This was originally filed as a second part of NIFI-11109, but after looking > more into the underlying causes/symptoms, realized that these are two > different issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11570) Processors have difficulty restoring dynamic properties when leaving ghost mode
[ https://issues.apache.org/jira/browse/NIFI-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799187#comment-17799187 ] Bryan Bende commented on NIFI-11570: I think using the propertyDescriptors would be a way to solve it, but I think we purposely don't populate them in the flow.json because it would drastically increase the size of the file and most of it would be repetitive, meaning if there are 10 instances of ProcessorX and it has no dynamic properties, then all 10 of those processors will write out the same propertyDescriptors in flow.json. > Processors have difficulty restoring dynamic properties when leaving ghost > mode > --- > > Key: NIFI-11570 > URL: https://issues.apache.org/jira/browse/NIFI-11570 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.19.1 >Reporter: Nissim Shiman >Assignee: Nissim Shiman >Priority: Major > > When a processor with non sensitive dynamic properties is started in ghost > mode due to its underlying nar being missing, it will have a difficult time > being restored even when its nar has been replaced. > The dynamic properties will be identified as being sensitive and not able to > be accessed. > So for example, if a dynamic property added to GenerateFlowFile and > nifi-standard-nar is removed from lib and nifi is restarted, GenerateFlowFile > will come up in ghosted mode (as expected). > When nifi-standard-nar is replaced and nifi is restarted, GenerateFlowFile > will be restored, but its dynamic property will not be accessable. > This was originally filed as a second part of NIFI-11109, but after looking > more into the underlying causes/symptoms, realized that these are two > different issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12485: Lineage Graph [nifi]
rfellows commented on code in PR #8173:
URL: https://github.com/apache/nifi/pull/8173#discussion_r1433174489
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/provenance/state/lineage/lineage.effects.ts:
##
@@ -0,0 +1,178 @@
+/*
+ * 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.
+ */
+
+import { Injectable } from '@angular/core';
+import { Actions, createEffect, ofType } from '@ngrx/effects';
+import * as LineageActions from './lineage.actions';
+import * as ProvenanceActions from
'../provenance-event-listing/provenance-event-listing.actions';
+import {
+asyncScheduler,
+catchError,
+from,
+interval,
+map,
+NEVER,
+of,
+switchMap,
+take,
+takeUntil,
+tap,
+withLatestFrom
+} from 'rxjs';
+import { MatDialog } from '@angular/material/dialog';
+import { Store } from '@ngrx/store';
+import { NiFiState } from '../../../../state';
+import { ProvenanceService } from '../../service/provenance.service';
+import { Lineage } from './index';
+import { selectClusterNodeId } from
'../provenance-event-listing/provenance-event-listing.selectors';
+import { selectLineageId } from './lineage.selectors';
+
+@Injectable()
+export class LineageEffects {
+constructor(
+private actions$: Actions,
+private store: Store,
+private provenanceService: ProvenanceService,
+private dialog: MatDialog
+) {}
+
+submitProvenanceQuery$ = createEffect(() =>
+this.actions$.pipe(
+ofType(LineageActions.submitLineageQuery),
+map((action) => action.request),
+switchMap((request) =>
+from(this.provenanceService.submitLineageQuery(request)).pipe(
+map((response) =>
+LineageActions.submitLineageQuerySuccess({
+response: {
+lineage: response.lineage
+}
+})
+),
+catchError((error) => {
+this.store.dispatch(
+ProvenanceActions.showOkDialog({
+title: 'Error',
+message: error.error
+})
+);
+
+return of(
+LineageActions.lineageApiError({
+error: error.error
+})
+);
+})
+)
+)
+)
+);
+
+submitProvenanceQuerySuccess$ = createEffect(() =>
+this.actions$.pipe(
+ofType(LineageActions.submitLineageQuerySuccess),
+map((action) => action.response),
+switchMap((response) => {
+const query: Lineage = response.lineage;
+if (query.finished) {
+this.dialog.closeAll();
+return of(LineageActions.deleteLineageQuery());
+} else {
+return of(LineageActions.startPollingLineageQuery());
+}
+})
+)
+);
+
+startPollingProvenanceQuery$ = createEffect(() =>
Review Comment:
rename to be more contextual
```suggestion
startPollingLineageQuery$ = createEffect(() =>
```
##
nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/src/app/pages/provenance/state/lineage/lineage.effects.ts:
##
@@ -0,0 +1,178 @@
+/*
+ * 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 d
Re: [PR] NIFI-12530: Support CREATE TABLE in Oracle database adapters [nifi]
EndzeitBegins commented on PR #8175: URL: https://github.com/apache/nifi/pull/8175#issuecomment-1865155224 Thank you for working on this @mattyb149. 👍🏻 I just glanced over the code and have two remarks. Is there a reason, there is no test added for the `OracleDatabaseAdapter` implementation? Does it make sense to populate the columns into the `StringBuilder` directly, instead of putting them into a `List` and only then joining them into the `StringBuilder`. I was under the impression that the `StringBuilder` is especially designed for these kinds of iterative `String` creations. However, Java is not my primary language, so I might be in the wrong here. 🤷🏻♂️ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799173#comment-17799173 ] Daniel Stieglitz edited comment on NIFI-12402 at 12/20/23 8:48 PM: --- [~nathluu] Change the status above from 'Open' to 'Patch Available' by pressing 'Submit Patch' was (Author: JIRAUSER294662): [~nathluu] Change the statu above.s from 'Open' to 'Patch Available' by pressing 'Submit Patch' > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.23.2 >Reporter: Tan Luu >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12402) MonitorActivity generates inactivity indicator after it is started and threshold duration exceeds without actual activities
[ https://issues.apache.org/jira/browse/NIFI-12402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799173#comment-17799173 ] Daniel Stieglitz commented on NIFI-12402: - [~nathluu] Change the statu above.s from 'Open' to 'Patch Available' by pressing 'Submit Patch' > MonitorActivity generates inactivity indicator after it is started and > threshold duration exceeds without actual activities > --- > > Key: NIFI-12402 > URL: https://issues.apache.org/jira/browse/NIFI-12402 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Affects Versions: 1.23.2 >Reporter: Tan Luu >Priority: Minor > Time Spent: 50m > Remaining Estimate: 0h > > Even though there is no activity, a start or restart of MonitorActivity > processor produces an inactive flowfile after "Threshold Duration". This > behavior creates a false positive notification cause there was no actual > activity. The expected behavior is to only send an inactive indicator if > there is activity after the processor is started. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12402 add option to user can avoid an inactive indicator is crea… [nifi]
dan-s1 commented on PR #8063: URL: https://github.com/apache/nifi/pull/8063#issuecomment-1865110606 LGTM +1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Updated] (NIFI-12530) Support CREATE TABLE for Oracle databases
[ https://issues.apache.org/jira/browse/NIFI-12530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-12530: Status: Patch Available (was: In Progress) > Support CREATE TABLE for Oracle databases > - > > Key: NIFI-12530 > URL: https://issues.apache.org/jira/browse/NIFI-12530 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > The UpdateDatabaseTable processor has the capability to create a target table > if it does not exist in the target database. However the database adapter > used must support it, and the Oracle database adapters do not. Even though it > would likely be a PL/SQL function, this is done "under the hood" and so could > be supported by Oracle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12530: Support CREATE TABLE in Oracle database adapters [nifi]
mattyb149 opened a new pull request, #8175: URL: https://github.com/apache/nifi/pull/8175 # Summary [NIFI-12530](https://issues.apache.org/jira/browse/NIFI-12530) This PR adds support for CREATE TABLE (via UpdateDatabaseRecord) for the two existing Oracle database adapters. # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [x] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [x] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [x] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [x] Pull Request based on current revision of the `main` branch - [x] Pull Request refers to a feature branch with one commit containing changes # Verification Please indicate the verification steps performed prior to pull request creation. ### Build - [x] Build completed using `mvn clean install -P contrib-check` - [x] JDK 21 ### Licensing - [ ] New dependencies are compatible with the [Apache License 2.0](https://apache.org/licenses/LICENSE-2.0) according to the [License Policy](https://www.apache.org/legal/resolved.html) - [ ] New dependencies are documented in applicable `LICENSE` and `NOTICE` files ### Documentation - [ ] Documentation formatting appears as expected in rendered files -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Created] (NIFI-12530) Support CREATE TABLE for Oracle databases
Matt Burgess created NIFI-12530: --- Summary: Support CREATE TABLE for Oracle databases Key: NIFI-12530 URL: https://issues.apache.org/jira/browse/NIFI-12530 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Matt Burgess Assignee: Matt Burgess Fix For: 1.25.0, 2.0.0 The UpdateDatabaseTable processor has the capability to create a target table if it does not exist in the target database. However the database adapter used must support it, and the Oracle database adapters do not. Even though it would likely be a PL/SQL function, this is done "under the hood" and so could be supported by Oracle. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-4071) ConvertJSONToSQL does not support Hive
[
https://issues.apache.org/jira/browse/NIFI-4071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Burgess resolved NIFI-4071.
Resolution: Implemented
> ConvertJSONToSQL does not support Hive
> --
>
> Key: NIFI-4071
> URL: https://issues.apache.org/jira/browse/NIFI-4071
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
>Reporter: Matt Burgess
>Priority: Minor
>
> Currently, the ConvertJSONToSQL processor does not support Hive as the target
> database, either using a HiveConnectionPool or a DBCPConnectionPool
> configured with a Hive driver. At the very least:
> 1) A SQLException occurs when determining the auto-increment value. This is
> due to a Hive bug (HIVE-13528
> [https://issues.apache.org/jira/browse/HIVE-13528]) where the column is not
> named according to the spec
> ([http://docs.oracle.com/javase/8/docs/api/java/sql/DatabaseMetaData.html#getColumns-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]).
> 2) Column names are returned with the table name prepended (using a dot
> separator)
> 3) There may be other JDBC API calls that are not supported by the Hive JDBC
> driver.
> #1 could be solved by checking for "IS_AUTOINCREMENT" then failing over to
> "IS_AUTO_INCREMENT". #2 could be solved with a lastIndexOf("."), as is done
> in _org.apache.nifi.util.hive.HiveJdbcCommon#createSchema(java.sql.ResultSet,
> java.lang.String)_. #3 would take some investigation into the other JDBC API
> calls being made.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-7086) oracle db read is slow (for me its bug)
[ https://issues.apache.org/jira/browse/NIFI-7086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess resolved NIFI-7086. Resolution: Not A Problem > oracle db read is slow (for me its bug) > --- > > Key: NIFI-7086 > URL: https://issues.apache.org/jira/browse/NIFI-7086 > Project: Apache NiFi > Issue Type: Improvement > Environment: nifi 1.8.0 >Reporter: naveen kumar saharan >Priority: Minor > > I am not able to fetch oracle db for 1 billion record table. It is taking too > much time(17 hours). > I tried creating queries based on dates using executesql -> > generatetablefetch -> executesql to parallel execution > small tables also performs slow as compared to python database table fetch > program around 20 times slower. This is very disapppointing. > querydatabasetable runs only on primary node with , if i increase thread it > give duplicate data. > Then what is the use of concurrent thread? > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] [NIFI-12504] Remaining views on Summary page [nifi]
mcgilman commented on PR #8174: URL: https://github.com/apache/nifi/pull/8174#issuecomment-1865036921 Will review... -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-11570) Processors have difficulty restoring dynamic properties when leaving ghost mode
[ https://issues.apache.org/jira/browse/NIFI-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799130#comment-17799130 ] Nissim Shiman commented on NIFI-11570: -- Circling back to this... This will involve changes to flow.json so I am hoping to have more people comment before comitting to an approach. Thank you very much [~bbende] for your approach (linked above) of storing the set of sensitiveDynamicPropertyNames in flow.json. I ran this problem by a senior engineer, who suggested that using the (currently existing, but empty) propertyDescriptor object in flow.json is a good approach as well. This may end of touching many files, so I would very much appreciate more feedback on this (more approaches or comments to the above two ideas) > Processors have difficulty restoring dynamic properties when leaving ghost > mode > --- > > Key: NIFI-11570 > URL: https://issues.apache.org/jira/browse/NIFI-11570 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.19.1 >Reporter: Nissim Shiman >Assignee: Nissim Shiman >Priority: Major > > When a processor with non sensitive dynamic properties is started in ghost > mode due to its underlying nar being missing, it will have a difficult time > being restored even when its nar has been replaced. > The dynamic properties will be identified as being sensitive and not able to > be accessed. > So for example, if a dynamic property added to GenerateFlowFile and > nifi-standard-nar is removed from lib and nifi is restarted, GenerateFlowFile > will come up in ghosted mode (as expected). > When nifi-standard-nar is replaced and nifi is restarted, GenerateFlowFile > will be restored, but its dynamic property will not be accessable. > This was originally filed as a second part of NIFI-11109, but after looking > more into the underlying causes/symptoms, realized that these are two > different issues. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12504) Remaining Summary Pages (tabs)
[ https://issues.apache.org/jira/browse/NIFI-12504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Fellows updated NIFI-12504: --- Status: Patch Available (was: In Progress) > Remaining Summary Pages (tabs) > -- > > Key: NIFI-12504 > URL: https://issues.apache.org/jira/browse/NIFI-12504 > Project: Apache NiFi > Issue Type: Sub-task >Reporter: Rob Fellows >Assignee: Rob Fellows >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > The initial effort was getting quite large, so this story was meant to > capture the remaining work: > * input ports > * output ports > * remote process groups > * process groups > * connections > * support for cluster-specific ui elements -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12495 Initial commit of new design [nifi-site]
james-elliott commented on code in PR #78:
URL: https://github.com/apache/nifi-site/pull/78#discussion_r1432962094
##
themes/nifi/layouts/partials/footer.html:
##
@@ -0,0 +1,38 @@
+
+
+
+
+
+
+
+
+https://apache.org";>
+
+
+
+
+
+ Copyright © {{ now.Year }} {{ .Site.Copyright }} under the terms
of the https://www.apache.org/licenses/LICENSE-2.0.html";>Apache
License, Version 2.0
+ Apache NiFi, NiFi, and the NiFi logo are trademarks of https://apache.org/";>The Apache Software Foundation
+
+
+
+Project
Review Comment:
This one just needs to have the CSS scoped to the downloads page content.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12495 Initial commit of new design [nifi-site]
james-elliott commented on code in PR #78:
URL: https://github.com/apache/nifi-site/pull/78#discussion_r1432956052
##
content/download/_index.md:
##
@@ -0,0 +1,106 @@
+---
+title: "Download"
+---
+
+# Download
+
+Previous releases are available in [release
archives](https://archive.apache.org/dist/nifi/). Archive downloads are
+subject to rate limiting.
+
+OpenPGP [Project Keys](https://downloads.apache.org/nifi/KEYS) can be used for
+[download verification](https://www.apache.org/info/verification.html).
+
+
+ NiFi
+ MiNiFi
+ Registry
+ FDS
+
+
+
+
+
+## Apache NiFi
+
+### Apache NiFi {{< param currentProjectVersion >}} https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}}">Release Notes
+
+- Released: {{< param currentProjectVersionReleased >}}
+- [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
+
+ Sources
+{{< download-links label="Download Source" project="nifi"
extension="-source-release.zip">}}
+ Binaries
+{{< download-links label="Download Standard" project="nifi"
extension="-bin.zip">}}
+{{< download-links label="Download Stateless" project="nifi"
extension="-bin.zip" qualifier="stateless">}}
+{{< download-links label="Download Kafka" project="nifi" extension=".zip"
qualifier="kafka-connector-assembly">}}
+{{< download-links label="Download Toolkit" project="nifi"
extension="-bin.zip" qualifier="toolkit">}}
+### Apache NiFi {{< param previousProjectVersion >}} https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param previousProjectVersion >}}">Release Notes
+
+- Released: {{< param previousProjectVersionReleased >}}
+- [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
+
+ Sources
+{{< download-links version="previous" label="Download Source" project="nifi"
extension="-source-release.zip">}}
+
+ Binaries
+{{< download-links version="previous" label="Download Standard" project="nifi"
extension="-bin.zip">}}
+{{< download-links version="previous" label="Download Stateless"
project="nifi" extension="-bin.zip" qualifier="stateless">}}
+{{< download-links version="previous" label="Download Kafka" project="nifi"
extension=".zip" qualifier="kafka-connector-assembly">}}
+{{< download-links version="previous" label="Download Toolkit" project="nifi"
extension="-bin.zip" qualifier="toolkit">}}
+
+
+
+## MiNiFi
+
+### MiNiFi Java {{< param currentProjectVersion >}} [Release
Notes](https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}})
+
+- Released: {{< param currentProjectVersionReleased >}}
+ Sources
+ {{< download-links label="MiNiFi Sources" extension=source-release.zip >}}
+ Binaries
+ {{< download-links label="MiNiFi" project=minifi extension=-bin.zip >}}
+ {{< download-links label="MiNiFi Toolkit" project=minifi qualifier=toolkit
extension=-bin.zip >}}
+ {{< download-links label="Command and Control" project=minifi qualifier=c2
extension=-bin.zip >}}
Review Comment:
`Download` was very inconsistently used, so I'll remove it from the button
labels.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Re: [PR] NIFI-12485: Lineage Graph [nifi]
rfellows commented on PR #8173: URL: https://github.com/apache/nifi/pull/8173#issuecomment-1864724892 Will review. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:51 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:51 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:50 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:46 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of user-info.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:39 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of user-info.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query&list=recentchanges&format=json&rcprop=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] MINIFICPP-2273 Update minifi documentation [nifi-site]
exceptionfactory commented on PR #79: URL: https://github.com/apache/nifi-site/pull/79#issuecomment-1864677009 Thanks for the update @martinzink! I may have missed this earlier, but similar to the about pages, it seems better to keep one MiNiFi Download page, with separate sections for C++ and Java, similar to how it is now. This is the general pattern being considered now in the redesigned approach. Having fewer pages should be easier to maintain, and easier to navigate for someone looking to download sources or binaries. What do you think? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] MINIFICPP-2273 Update minifi documentation [nifi-site]
martinzink commented on code in PR #79: URL: https://github.com/apache/nifi-site/pull/79#discussion_r1432848742 ## source/minifi/minifi-java-about.md: ## @@ -0,0 +1,4 @@ +### MiNiFi Java Review Comment: It looks like I accidentally deleted the wrong file before, (removed the download.md and not the about.md) fixed in https://github.com/apache/nifi-site/pull/79/commits/48dba49cc028800271ae1eb86f0d90db726ac089 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] MINIFICPP-2273 Update minifi documentation [nifi-site]
exceptionfactory commented on code in PR #79: URL: https://github.com/apache/nifi-site/pull/79#discussion_r1432790682 ## source/minifi/minifi-java-about.md: ## @@ -0,0 +1,4 @@ +### MiNiFi Java Review Comment: It looks like this file can be deleted. ## layouts/partials/minifi-topbar.html: ## @@ -16,30 +16,32 @@ -Documentation +MiNiFi Java -Getting Started -MiNiFi Java Quick Start Guide -Administrator's Guide -Converter Toolkit -FAQ -https://cwiki.apache.org/confluence/display/MiNiFi";>Wiki +Quick Start +Converter Toolkit +Administrator's Guide +Download -Downloads +MiNiFi C++ -Download MiNiFi Components -https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes";>MiNiFi Java Release Notes -https://cwiki.apache.org/confluence/display/MINIFI/Release+Notes#ReleaseNotes-MiNiFi(C++)">MiNiFi C++ Release Notes +https://github.com/apache/nifi-minifi-cpp?tab=readme-ov-file#installing-as-a-service";>Installation +https://github.com/apache/nifi-minifi-cpp/blob/main/CONFIGURE.md";>Configuration +https://github.com/apache/nifi-minifi-cpp/blob/main/PROCESSORS.md";>Supported Processors Review Comment: Recommend shortening this to just `Processors` as the label. ```suggestion https://github.com/apache/nifi-minifi-cpp/blob/main/PROCESSORS.md";>Processors ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] NIFI-12495 Initial commit of new design [nifi-site]
exceptionfactory commented on code in PR #78:
URL: https://github.com/apache/nifi-site/pull/78#discussion_r1432749427
##
content/download/_index.md:
##
@@ -0,0 +1,106 @@
+---
+title: "Download"
+---
+
+# Download
+
+Previous releases are available in [release
archives](https://archive.apache.org/dist/nifi/). Archive downloads are
+subject to rate limiting.
+
+OpenPGP [Project Keys](https://downloads.apache.org/nifi/KEYS) can be used for
+[download verification](https://www.apache.org/info/verification.html).
+
+
+ NiFi
+ MiNiFi
+ Registry
+ FDS
+
+
+
+
+
+## Apache NiFi
+
+### Apache NiFi {{< param currentProjectVersion >}} https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}}">Release Notes
+
+- Released: {{< param currentProjectVersionReleased >}}
+- [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
+
+ Sources
+{{< download-links label="Download Source" project="nifi"
extension="-source-release.zip">}}
+ Binaries
+{{< download-links label="Download Standard" project="nifi"
extension="-bin.zip">}}
+{{< download-links label="Download Stateless" project="nifi"
extension="-bin.zip" qualifier="stateless">}}
+{{< download-links label="Download Kafka" project="nifi" extension=".zip"
qualifier="kafka-connector-assembly">}}
+{{< download-links label="Download Toolkit" project="nifi"
extension="-bin.zip" qualifier="toolkit">}}
+### Apache NiFi {{< param previousProjectVersion >}} https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param previousProjectVersion >}}">Release Notes
+
+- Released: {{< param previousProjectVersionReleased >}}
+- [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
+
+ Sources
+{{< download-links version="previous" label="Download Source" project="nifi"
extension="-source-release.zip">}}
+
+ Binaries
+{{< download-links version="previous" label="Download Standard" project="nifi"
extension="-bin.zip">}}
+{{< download-links version="previous" label="Download Stateless"
project="nifi" extension="-bin.zip" qualifier="stateless">}}
+{{< download-links version="previous" label="Download Kafka" project="nifi"
extension=".zip" qualifier="kafka-connector-assembly">}}
Review Comment:
```suggestion
{{< download-links version="previous" label="Download Kafka Connector"
project="nifi" extension=".zip" qualifier="kafka-connector-assembly">}}
```
##
content/download/_index.md:
##
@@ -0,0 +1,106 @@
+---
+title: "Download"
+---
+
+# Download
+
+Previous releases are available in [release
archives](https://archive.apache.org/dist/nifi/). Archive downloads are
+subject to rate limiting.
+
+OpenPGP [Project Keys](https://downloads.apache.org/nifi/KEYS) can be used for
+[download verification](https://www.apache.org/info/verification.html).
+
+
+ NiFi
+ MiNiFi
+ Registry
+ FDS
+
+
+
+
+
+## Apache NiFi
+
+### Apache NiFi {{< param currentProjectVersion >}} https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}}">Release Notes
+
+- Released: {{< param currentProjectVersionReleased >}}
+- [Migration
Guidance](https://cwiki.apache.org/confluence/display/NIFI/Migration+Guidance)
+
+ Sources
+{{< download-links label="Download Source" project="nifi"
extension="-source-release.zip">}}
+ Binaries
+{{< download-links label="Download Standard" project="nifi"
extension="-bin.zip">}}
+{{< download-links label="Download Stateless" project="nifi"
extension="-bin.zip" qualifier="stateless">}}
+{{< download-links label="Download Kafka" project="nifi" extension=".zip"
qualifier="kafka-connector-assembly">}}
Review Comment:
The should be changed to `Kafka Connector` for clarity:
```suggestion
{{< download-links label="Download Kafka Connector" project="nifi"
extension=".zip" qualifier="kafka-connector-assembly">}}
```
##
content/projects/registry.md:
##
@@ -27,12 +31,11 @@ Apache NiFi [Project
Keys](https://downloads.apache.org/nifi/KEYS) can be used t
Please allow up to 24 hours for mirrors to synchronize following the release
of a new version.
-### {{< param currentProjectVersion >}}
-- [Release
Notes](https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}})
-- Sources
- - {{< download-links label="Apache NiFi Sources"
extension=source-release.zip >}}
-- Binaries
- - {{< download-links label="Apache NiFi Registry" qualifier="registry"
extension=bin.zip >}}
+### Registry {{< param currentProjectVersion >}} [Release
Notes](https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version{{<
param currentProjectVersion >}})
+ Sources
+{{< download-links label="Apache NiFi Sources" extension=-source-release.zip
>}}
+ Binaries
+{{< download-links labe
[jira] [Updated] (NIFI-12400) Remaining items to migrate UI to currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-12400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12400: --- Description: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12504) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable (NIFI-12529) ** Disable (NIFI-12529) ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Routing error handling * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. * Prompt user to save Parameter Context when Edit form is dirty [1] [https://github.com/apache/nifi/pull/8053] was: The purpose of this Jira is to track all remaining items following the initial commit [1] for NIFI-11481. The description will be kept up to date with remaining features, tasks, and improvements. As each items is worked, a new sub task Jira will be created and referenced in this description. * Support Parameters in Properties with Allowable Values (NIFI-12401) * Summary (NIFI-12437) ** Remaining work not addressed in initial Jira: *** input ports (NIFI-12504) *** output ports (NIFI-12504) *** remote process groups (NIFI-12504) *** process groups (NIFI-12504) *** connections (NIFI-12504) *** System Diagnostics (NIFI-12505) *** support for cluster-specific ui elements (NIFI-12504) * Counters (NIFI-12415) * Bulletin Board * Provenance (NIFI-12445) ** Event Listing (NIFI-12445) ** Search (NIFI-12445) ** Event Dialog (NIFI-12445) ** Lineage (NIFI-12485) ** Replay from context menu (NIFI-12445) * Flow Analysis Rules * Registry Clients (NIFI-12486) * Import from Registry * Parameter Providers * Cluster * Flow Configuration History * Node Status History * Users * Policies * Help * About * Show Upstream/Downstream * Align * List Queue * Empty [all] Queue * View Content * View State * Change Version * PG Version ** Start ** Commit ** Force Commit ** Show changes ** Revert changes ** Change Flow version ** Stop * Configure PG (NIFI-12417) * Process Group Services (NIFI-12425) ** Listing (NIFI-12425) ** Create (NIFI-12425) ** Configure (NIFI-12425) ** Delete (NIFI-12425) ** Enable ** Disable ** Improve layout and breadcrumbs * Configure Processor ** Service Link (NIFI-12425) ** Create inline Service (NIFI-12425) ** Parameter Link (NIFI-12502) ** Convert to Parameter (NIFI-12502) * Download Flow * Create RPG * Configure RPG * RPG Remote Ports * RPG Go To * Color * Move to Front * Copy/Paste * Run unit tests are part of standard build * Update all API calls to consider disconnect node confirmation * Update API calls to use uiOnly flag * Routing error handling * Prevent navigate to Service when configuration form is dirty * Introduce header in new pages to unify with canvas and offer better navigation. * Prompt user to save Parameter Context when Edit form is dirty [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework >
[jira] [Created] (NIFI-12529) Enable/Disable Controller Service
Matt Gilman created NIFI-12529: -- Summary: Enable/Disable Controller Service Key: NIFI-12529 URL: https://issues.apache.org/jira/browse/NIFI-12529 Project: Apache NiFi Issue Type: Sub-task Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Add support to enable and disable controller services. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12528) Funnels bug
Giovanni created NIFI-12528: --- Summary: Funnels bug Key: NIFI-12528 URL: https://issues.apache.org/jira/browse/NIFI-12528 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.23.2 Environment: NiFi cluster Reporter: Giovanni Attachments: image001.png I've notice a bug in our working cluster of 4 nodes. When two funnels are connected, with no other connections as themselves, like in attached image, is not possible to delete them. After trying to modify one of their connections, the Node where the action is performed crashes, and will not turn on unless the entire cluster restarts. -- This message was sent by Atlassian Jira (v8.20.10#820010)
