[jira] [Updated] (NIFI-12419) Only build the nifi-web-frontend module if the include-new-ui is active
[
https://issues.apache.org/jira/browse/NIFI-12419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Gilman updated NIFI-12419:
---
Fix Version/s: 2.0.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Only build the nifi-web-frontend module if the include-new-ui is active
> ---
>
> Key: NIFI-12419
> URL: https://issues.apache.org/jira/browse/NIFI-12419
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
>Reporter: Rob Fellows
>Assignee: Rob Fellows
>Priority: Major
> Fix For: 2.0.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The new ui maven module is included by default when a normal build is
> executed. This should only be included in the build if the
> {noformat}include-new-ui{noformat} profile is active.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12419) Only build the nifi-web-frontend module if the include-new-ui is active
[
https://issues.apache.org/jira/browse/NIFI-12419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790329#comment-17790329
]
ASF subversion and git services commented on NIFI-12419:
Commit 4bba7e6188d7cdff122ef851a46ce44e533e940b in nifi's branch
refs/heads/main from Rob Fellows
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=4bba7e6188 ]
[NIFI-12419] - Only include the new UI module when building if the
'include-new-ui' profile is active. (#8069)
* [NIFI-12419] - Only include the new UI module when building if the
'include-new-ui' profile is active. Also update the ci-workflow.yaml to
activate that profile.
* add the profile activation to the Maven Build command
This closes #8069
> Only build the nifi-web-frontend module if the include-new-ui is active
> ---
>
> Key: NIFI-12419
> URL: https://issues.apache.org/jira/browse/NIFI-12419
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
>Reporter: Rob Fellows
>Assignee: Rob Fellows
>Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> The new ui maven module is included by default when a normal build is
> executed. This should only be included in the build if the
> {noformat}include-new-ui{noformat} profile is active.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] [NIFI-12419] - Only include the new UI module when building if the 'include-new-ui' profile is active. [nifi]
mcgilman merged PR #8069: URL: https://github.com/apache/nifi/pull/8069 -- 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-12419] - Only include the new UI module when building if the 'include-new-ui' profile is active. [nifi]
mcgilman commented on PR #8069: URL: https://github.com/apache/nifi/pull/8069#issuecomment-1828826196 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] [Updated] (NIFI-12404) YamlTreeReader does not support Yaml aliases
[
https://issues.apache.org/jira/browse/NIFI-12404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12404:
Status: Patch Available (was: Open)
> YamlTreeReader does not support Yaml aliases
>
>
> Key: NIFI-12404
> URL: https://issues.apache.org/jira/browse/NIFI-12404
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Utilizing the Jackson library to parse YAML allowed for reuse of much of the
> code used by the JsonTreeReader. A side effect though is Jackson does not
> support the resolution of Yaml aliases. An example would be the following
> Yaml where the ship-to value references the anchor defined in the bill-to
> section.
>
> {code:java}
> bill-to:
> street: |
> 123 Tornado Alley
> Suite 16
> city: East Centerville
> state: KS
> ship-to: *id001
> {code}
>
> The above Yaml is transformed to the following JSON when using ConvertRecord
> configured with the YamlTreeReader and the JsonRecordSetWriter:
> {code:java}
> [ {
> "bill-to" : {
> "street" : "123 Tornado Alley\nSuite 16\n",
> "city" : "East Centerville",
> "state" : "KS"
> },
> "ship-to" : "id001"
> } ]{code}
>
> Note how the "ship-to" does not contain the same value as "bill-to" but
> rather a string with the name of the alias.
> This is a known bug in Jackson as seen
> [here|https://github.com/FasterXML/jackson-dataformats-text/issues/98]
> The aim of this ticket is to add to the YamlTreeReader documentation the fact
> that Yaml aliases are not resolved.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12404 Added documentation indicating this controller service does not resolve YAML aliases. [nifi]
dan-s1 opened a new pull request, #8070: URL: https://github.com/apache/nifi/pull/8070 # Summary [NIFI-12404](https://issues.apache.org/jira/browse/NIFI-12404) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] 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] [Updated] (NIFI-12419) Only build the nifi-web-frontend module if the include-new-ui is active
[
https://issues.apache.org/jira/browse/NIFI-12419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Fellows updated NIFI-12419:
---
Status: Patch Available (was: In Progress)
> Only build the nifi-web-frontend module if the include-new-ui is active
> ---
>
> Key: NIFI-12419
> URL: https://issues.apache.org/jira/browse/NIFI-12419
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Core UI
>Reporter: Rob Fellows
>Assignee: Rob Fellows
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The new ui maven module is included by default when a normal build is
> executed. This should only be included in the build if the
> {noformat}include-new-ui{noformat} profile is active.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] [NIFI-12419] - Only include the new UI module when building if the 'include-new-ui' profile is active. [nifi]
rfellows opened a new pull request, #8069: URL: https://github.com/apache/nifi/pull/8069 * Also updated the ci-workflow.yaml to activate that profile. # Summary [NIFI-0](https://issues.apache.org/jira/browse/NIFI-0) # 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-12419) Only build the nifi-web-frontend module if the include-new-ui is active
Rob Fellows created NIFI-12419:
--
Summary: Only build the nifi-web-frontend module if the
include-new-ui is active
Key: NIFI-12419
URL: https://issues.apache.org/jira/browse/NIFI-12419
Project: Apache NiFi
Issue Type: Sub-task
Components: Core UI
Reporter: Rob Fellows
Assignee: Rob Fellows
The new ui maven module is included by default when a normal build is executed.
This should only be included in the build if the
{noformat}include-new-ui{noformat} profile is active.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
Re: [PR] MINIFICPP-2217 - Implement jolt processor shift operation [nifi-minifi-cpp]
fgerlits commented on code in PR #1692:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1692#discussion_r1403618933
##
libminifi/test/Utils.h:
##
@@ -48,23 +48,45 @@ using namespace std::literals::chrono_literals;
namespace org::apache::nifi::minifi::test::utils {
+struct JsonContext {
+ const JsonContext* parent{nullptr};
+ std::string_view member;
+
+ std::string path() const {
+if (!parent) {
+ return "/";
+}
+return minifi::utils::StringUtils::join_pack(parent->path(), member, "/");
+ }
+};
+
+#define REQUIRE_WARN(cond, msg) if (!(cond)) {WARN(msg); REQUIRE(cond);}
+
// carries out a loose match on objects, i.e. it doesn't matter if the
// actual object has extra fields than expected
-void matchJSON(const rapidjson::Value& actual, const rapidjson::Value&
expected) {
+void matchJSON(const JsonContext& ctx, const rapidjson::Value& actual, const
rapidjson::Value& expected, bool strict = false) {
if (expected.IsObject()) {
-REQUIRE(actual.IsObject());
+REQUIRE_WARN(actual.IsObject(), fmt::format("Expected object at {}",
ctx.path()));
for (const auto& expected_member : expected.GetObject()) {
- REQUIRE(actual.HasMember(expected_member.name));
- matchJSON(actual[expected_member.name], expected_member.value);
+ std::string_view name{expected_member.name.GetString(),
expected_member.name.GetStringLength()};
+ REQUIRE_WARN(actual.HasMember(expected_member.name),
fmt::format("Expected member '{}' at {}", name, ctx.path()));
+ matchJSON(JsonContext{.parent = , .member = name},
actual[expected_member.name], expected_member.value, strict);
+}
+if (strict) {
+ for (const auto& actual_member : actual.GetObject()) {
+std::string_view name{actual_member.name.GetString(),
actual_member.name.GetStringLength()};
+REQUIRE_WARN(expected.HasMember(actual_member.name), fmt::format("Did
not expect member '{}' at {}", name, ctx.path()));
+matchJSON(JsonContext{.parent = , .member = name},
actual_member.value, expected[actual_member.name], strict);
Review Comment:
I don't think line 79 is needed, since we have already compared all common
children in the first loop.
##
libminifi/test/Utils.h:
##
@@ -48,23 +48,45 @@ using namespace std::literals::chrono_literals;
namespace org::apache::nifi::minifi::test::utils {
+struct JsonContext {
+ const JsonContext* parent{nullptr};
+ std::string_view member;
+
+ std::string path() const {
+if (!parent) {
+ return "/";
+}
+return minifi::utils::StringUtils::join_pack(parent->path(), member, "/");
+ }
+};
+
+#define REQUIRE_WARN(cond, msg) if (!(cond)) {WARN(msg); REQUIRE(cond);}
+
// carries out a loose match on objects, i.e. it doesn't matter if the
// actual object has extra fields than expected
-void matchJSON(const rapidjson::Value& actual, const rapidjson::Value&
expected) {
+void matchJSON(const JsonContext& ctx, const rapidjson::Value& actual, const
rapidjson::Value& expected, bool strict = false) {
if (expected.IsObject()) {
-REQUIRE(actual.IsObject());
+REQUIRE_WARN(actual.IsObject(), fmt::format("Expected object at {}",
ctx.path()));
for (const auto& expected_member : expected.GetObject()) {
- REQUIRE(actual.HasMember(expected_member.name));
- matchJSON(actual[expected_member.name], expected_member.value);
+ std::string_view name{expected_member.name.GetString(),
expected_member.name.GetStringLength()};
+ REQUIRE_WARN(actual.HasMember(expected_member.name),
fmt::format("Expected member '{}' at {}", name, ctx.path()));
+ matchJSON(JsonContext{.parent = , .member = name},
actual[expected_member.name], expected_member.value, strict);
+}
+if (strict) {
+ for (const auto& actual_member : actual.GetObject()) {
+std::string_view name{actual_member.name.GetString(),
actual_member.name.GetStringLength()};
+REQUIRE_WARN(expected.HasMember(actual_member.name), fmt::format("Did
not expect member '{}' at {}", name, ctx.path()));
+matchJSON(JsonContext{.parent = , .member = name},
actual_member.value, expected[actual_member.name], strict);
+ }
}
} else if (expected.IsArray()) {
-REQUIRE(actual.IsArray());
-REQUIRE(actual.Size() == expected.Size());
+REQUIRE_WARN(actual.IsArray(), fmt::format("Expected array at {}",
ctx.path()));
+REQUIRE_WARN(actual.Size() == expected.Size(), fmt::format("Expected array
of length {}, got {} at", expected.Size(), actual.Size(), ctx.path()));
Review Comment:
missing `{}` at the end of the format string
##
libminifi/test/Utils.h:
##
@@ -48,23 +48,45 @@ using namespace std::literals::chrono_literals;
namespace org::apache::nifi::minifi::test::utils {
+struct JsonContext {
+ const JsonContext* parent{nullptr};
+ std::string_view member;
Review Comment:
Having a `string_view` member is unsafe, although the uses below look OK. I
[jira] [Commented] (NIFI-12418) Identity Provider Groups Missing in Refreshed Bearer Token
[ https://issues.apache.org/jira/browse/NIFI-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790251#comment-17790251 ] David Handermann commented on NIFI-12418: - Reference dev mailing list thread: https://lists.apache.org/thread/54tpom04nv526ql8zv91n7ll1wc24sdh > Identity Provider Groups Missing in Refreshed Bearer Token > -- > > Key: NIFI-12418 > URL: https://issues.apache.org/jira/browse/NIFI-12418 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework, Security >Affects Versions: 2.0.0-M1, 1.24.0 >Reporter: David Handermann >Assignee: David Handermann >Priority: Minor > > The OIDC Bearer Token Refresh Filter is responsible for renewing application > Bearer Tokens when NiFi is integrated with an OpenID Connect Identity > Provider that supports the Refresh Token Grant Type. > NiFi 1.23.0 introduced changes for handling group membership information > supplied from an Identity Provider, passing the groups in the application > Bearer Token instead of persisting the groups in the local database > repository. > As a result of these handling changes, the Identity Provider group membership > information is not retained when the OIDC Bearer Token Refresh Filter > generates a new token. In deployments where the configured User Group > Provider does not provide the group information, this behavior can result in > authorization failures after refreshing the token. > The Bearer Token Refresh Filter should be corrected to retrieve group > membership information from the new Identity Provider token. -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on PR #8049: URL: https://github.com/apache/nifi/pull/8049#issuecomment-1828509202 Not quite sure why the CI pipeline failed. :( I didn't have any problems running locally with Linux / JDK 21. At a first glance the error does not relate to any of the changes that are part of the PR. Maybe this is related to build problems reported by others on the dev mailing list which seemingly were introduced by #8053? However, other pipeline runs seem to work just fine. -- 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-12418) Identity Provider Groups Missing in Refreshed Bearer Token
David Handermann created NIFI-12418: --- Summary: Identity Provider Groups Missing in Refreshed Bearer Token Key: NIFI-12418 URL: https://issues.apache.org/jira/browse/NIFI-12418 Project: Apache NiFi Issue Type: Bug Components: Core Framework, Security Affects Versions: 1.24.0, 2.0.0-M1 Reporter: David Handermann Assignee: David Handermann The OIDC Bearer Token Refresh Filter is responsible for renewing application Bearer Tokens when NiFi is integrated with an OpenID Connect Identity Provider that supports the Refresh Token Grant Type. NiFi 1.23.0 introduced changes for handling group membership information supplied from an Identity Provider, passing the groups in the application Bearer Token instead of persisting the groups in the local database repository. As a result of these handling changes, the Identity Provider group membership information is not retained when the OIDC Bearer Token Refresh Filter generates a new token. In deployments where the configured User Group Provider does not provide the group information, this behavior can result in authorization failures after refreshing the token. The Bearer Token Refresh Filter should be corrected to retrieve group membership information from the new Identity Provider token. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11481) Migrate the Nifi UI to a currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-11481: --- Fix Version/s: 2.0.0 (was: 2.latest) > Migrate the Nifi UI to a currently supported/active framework > - > > Key: NIFI-11481 > URL: https://issues.apache.org/jira/browse/NIFI-11481 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Dondi Imperial >Assignee: Matt Gilman >Priority: Major > Fix For: 2.0.0 > > Time Spent: 2.5h > Remaining Estimate: 0h > > AngularJS support [officially ended as of January > 2020|https://blog.angular.io/finding-a-path-forward-with-angularjs-7e186fdd4429]. > This can be problematic in environments with strict compliance requirements. > Perhaps the Nifi UI should be refactored or upgraded to Angular (non-JS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (NIFI-12030) Make property pop-up window expandable
[ https://issues.apache.org/jira/browse/NIFI-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys closed NIFI-12030. --- > Make property pop-up window expandable > -- > > Key: NIFI-12030 > URL: https://issues.apache.org/jira/browse/NIFI-12030 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > When you click on a property that contains a list of values, the pop-up > selection window is a fixed width. Sometimes the property values are longer > than the window can display, and so the text is truncated. This can be a > problem, particularly with controller services, as the controller names can > be quiet long. Sometimes several instances of the controller exists, and text > is appended to the end of the controller name to differentiate the instances, > but when trying to select one, it is impossible to see the end of the text. > Would like to have this pop-up expandable in geometry at least in width, so > it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12030) Make property pop-up window expandable
[ https://issues.apache.org/jira/browse/NIFI-12030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anna Nys resolved NIFI-12030. - Resolution: Won't Fix Original requester is fine with the hover-over option of seeing truncated drop-down options. > Make property pop-up window expandable > -- > > Key: NIFI-12030 > URL: https://issues.apache.org/jira/browse/NIFI-12030 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Anna Nys >Assignee: Anna Nys >Priority: Minor > Time Spent: 1h > Remaining Estimate: 0h > > When you click on a property that contains a list of values, the pop-up > selection window is a fixed width. Sometimes the property values are longer > than the window can display, and so the text is truncated. This can be a > problem, particularly with controller services, as the controller names can > be quiet long. Sometimes several instances of the controller exists, and text > is appended to the end of the controller name to differentiate the instances, > but when trying to select one, it is impossible to see the end of the text. > Would like to have this pop-up expandable in geometry at least in width, so > it can be expanded to see all of the text. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12417) Process Group Configuration
[ https://issues.apache.org/jira/browse/NIFI-12417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12417: --- Parent: NIFI-12400 Issue Type: Sub-task (was: New Feature) > Process Group Configuration > --- > > Key: NIFI-12417 > URL: https://issues.apache.org/jira/browse/NIFI-12417 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > Allow Process Groups to be configured. This should include managing > controller services scoped to the current Process Group. With Service > Management in place, we can also update Processor configuration to allow for > referencing Services, creating new Services inline, and going to a referenced > Service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12417) Process Group Configuration
Matt Gilman created NIFI-12417: -- Summary: Process Group Configuration Key: NIFI-12417 URL: https://issues.apache.org/jira/browse/NIFI-12417 Project: Apache NiFi Issue Type: New Feature Components: Core UI Reporter: Matt Gilman Assignee: Matt Gilman Allow Process Groups to be configured. This should include managing controller services scoped to the current Process Group. With Service Management in place, we can also update Processor configuration to allow for referencing Services, creating new Services inline, and going to a referenced Service. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 * Counters (NIFI-12415) * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * 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) * Configure Processor ** Service Link (NIFI-12417) ** Create inline Service (NIFI-12417) ** Parameter Link ** Convert to Parameter * 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 [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 * Counters (NIFI-12415) * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * 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 * Configure Processor ** Service Link ** Create inline Service ** Parameter Link ** Convert to Parameter * 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 [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > 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 > * Counters (NIFI-12415) > * Bulletin Board > * Provenance > ** Replay from context menu > * Flow Analysis Rules > * Registry Clients > * 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) > * Configure Processor > ** Service Link (NIFI-12417) > ** Create inline Service (NIFI-12417) > ** Parameter Link > ** Convert to Parameter > * 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 > [1] [https://github.com/apache/nifi/pull/8053] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-12414) Update org.apache.commons.lang3.version to 3.14.0
[ https://issues.apache.org/jira/browse/NIFI-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre Villard resolved NIFI-12414. --- Fix Version/s: 1.25.0 2.0.0 Resolution: Fixed > Update org.apache.commons.lang3.version to 3.14.0 > - > > Key: NIFI-12414 > URL: https://issues.apache.org/jira/browse/NIFI-12414 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.latest, 1.24.0, 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Time Spent: 20m > Remaining Estimate: 0h > > Update org.apache.commons.lang3.version to 3.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (NIFI-11481) Migrate the Nifi UI to a currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman resolved NIFI-11481. Fix Version/s: 2.latest Resolution: Fixed Resolving this Jira as the initial commit is in. There are still follow-up items to complete as detailed in NIFI-12400. > Migrate the Nifi UI to a currently supported/active framework > - > > Key: NIFI-11481 > URL: https://issues.apache.org/jira/browse/NIFI-11481 > Project: Apache NiFi > Issue Type: Wish > Components: Core UI >Reporter: Dondi Imperial >Assignee: Matt Gilman >Priority: Major > Fix For: 2.latest > > Time Spent: 2.5h > Remaining Estimate: 0h > > AngularJS support [officially ended as of January > 2020|https://blog.angular.io/finding-a-path-forward-with-angularjs-7e186fdd4429]. > This can be problematic in environments with strict compliance requirements. > Perhaps the Nifi UI should be refactored or upgraded to Angular (non-JS). -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12401) Support Parameters in Properties with Allowable Values
[ https://issues.apache.org/jira/browse/NIFI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Gilman updated NIFI-12401: --- Status: Patch Available (was: In Progress) > Support Parameters in Properties with Allowable Values > -- > > Key: NIFI-12401 > URL: https://issues.apache.org/jira/browse/NIFI-12401 > Project: Apache NiFi > Issue Type: Sub-task > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update the combo editor to support referencing existing parameters. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12414) Update org.apache.commons.lang3.version to 3.14.0
[ https://issues.apache.org/jira/browse/NIFI-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790216#comment-17790216 ] ASF subversion and git services commented on NIFI-12414: Commit fce0c3012b4c23b8e484ae8791cceaba016294de in nifi's branch refs/heads/support/nifi-1.x from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=fce0c3012b ] NIFI-12414 Update org.apache.commons.lang3.version to 3.14.0 Signed-off-by: Pierre Villard This closes #8066. > Update org.apache.commons.lang3.version to 3.14.0 > - > > Key: NIFI-12414 > URL: https://issues.apache.org/jira/browse/NIFI-12414 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.latest, 1.24.0, 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 20m > Remaining Estimate: 0h > > Update org.apache.commons.lang3.version to 3.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12414) Update org.apache.commons.lang3.version to 3.14.0
[ https://issues.apache.org/jira/browse/NIFI-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790214#comment-17790214 ] ASF subversion and git services commented on NIFI-12414: Commit 1268acb864913700e2ded3e342db8ac51294879b in nifi's branch refs/heads/main from mr1716 [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1268acb864 ] NIFI-12414 Update org.apache.commons.lang3.version to 3.14.0 Signed-off-by: Pierre Villard This closes #8066. > Update org.apache.commons.lang3.version to 3.14.0 > - > > Key: NIFI-12414 > URL: https://issues.apache.org/jira/browse/NIFI-12414 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.latest, 1.24.0, 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Update org.apache.commons.lang3.version to 3.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12414 Update org.apache.commons.lang3.version to 3.14.0 [nifi]
asfgit closed pull request #8066: NIFI-12414 Update org.apache.commons.lang3.version to 3.14.0 URL: https://github.com/apache/nifi/pull/8066 -- 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-12386 Adds processor FilterAttribute [nifi]
exceptionfactory commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1406589450
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttributes.java:
##
@@ -0,0 +1,275 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
+@UseCase(
+description = "Retain all FlowFile attributes matching a regular
expression",
+configuration = """
+Set "Filter mode" to "Retain".
+Set "Attribute matching strategy" to "Use regular expression".
+Specify the "Regular expression to filter attributes", e.g.
"my-property|a-prefix[.].*".
+"""
+)
+@UseCase(
+description = "Remove only a specified set of FlowFile attributes",
+configuration = """
+Set "Filter mode" to "Remove".
+Set "Attribute matching strategy" to "Enumerate attributes".
+Specify the set of "Set of attributes to filter" using the
delimiter comma ',', e.g. "my-property,other,filename".
+"""
+)
+public class FilterAttributes extends AbstractProcessor {
Review Comment:
Thanks for making the adjustments!
--
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-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790209#comment-17790209 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/27/23 6:35 PM: --- [~iiojj2] Can you please share with me the actual Excel you have attached as an image? Also please share with me the configuration you had for QueryRecord so I can better diagnose why this would not be working. As for the java.lang.IllegalStateException please create a ticket with an example of the type of of file ingested where you see that exception. You can assign me the ticket. Thanks! was (Author: JIRAUSER294662): [~iiojj2] Can you please share with me the actual Excel you have attached as an image? Also please share with me the configuration you had for QueryRecord so I can better diagnose why this would not be working. Thanks! As for the java.lang.IllegalStateException please create a ticket with an example of the type of of file ingested where you see that exception. You can assign me the ticket. Thanks! > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790209#comment-17790209 ] Daniel Stieglitz commented on NIFI-11167: - [~iiojj2] Can you please share with me the actual Excel you have attached as an image? Also please share with me the configuration you had for QueryRecord so I can better diagnose why this would not be working. Thanks! As for the java.lang.IllegalStateException please create a ticket with an example of the type of of file ingested where you see that exception. You can assign me the ticket. Thanks! > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (NIFI-11167) Add Excel Record Reader
[ https://issues.apache.org/jira/browse/NIFI-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790209#comment-17790209 ] Daniel Stieglitz edited comment on NIFI-11167 at 11/27/23 6:34 PM: --- [~iiojj2] Can you please share with me the actual Excel you have attached as an image? Also please share with me the configuration you had for QueryRecord so I can better diagnose why this would not be working. Thanks! As for the java.lang.IllegalStateException please create a ticket with an example of the type of of file ingested where you see that exception. You can assign me the ticket. Thanks! was (Author: JIRAUSER294662): [~iiojj2] Can you please share with me the actual Excel you have attached as an image? Also please share with me the configuration you had for QueryRecord so I can better diagnose why this would not be working. Thanks! As for the java.lang.IllegalStateException please create a ticket with an example of the type of of file ingested where you see that exception. You can assign me the ticket. Thanks! > Add Excel Record Reader > --- > > Key: NIFI-11167 > URL: https://issues.apache.org/jira/browse/NIFI-11167 > Project: Apache NiFi > Issue Type: New Feature > Components: Extensions >Reporter: David Handermann >Assignee: Daniel Stieglitz >Priority: Minor > Fix For: 2.0.0-M1, 1.23.0 > > Attachments: screenshot-1.png > > Time Spent: 10h 10m > Remaining Estimate: 0h > > A new Excel Record Reader should be implemented to support reading XSLX > spreadsheet rows as NiFi Records. This Reader will enable integration with > various record-oriented components, obviating the need for the narrowly > focused ConvertExcelToCSVProcessor. The initial version of the Excel Reader > should not support the legacy binary XLS format. > The ExcelReader should use a library that supports reading from a stream of > rows to avoid consuming large amounts of heap memory during processing. > The ExcelReader should support configurable properties to read selected > sheets. With Excel supporting typed field values, some amount of field type > mapping will be required. Additional input filtering properties should not be > implemented as existing Processors like QueryRecord support a wide variety of > filtering and projection use cases. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12401: Allow combo editor to reference parameters [nifi]
mcgilman opened a new pull request, #8068: URL: https://github.com/apache/nifi/pull/8068 NIFI-12401: - Allow combo editor to reference parameters. -- 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-12386 Adds processor FilterAttribute [nifi]
EndzeitBegins commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1406462919
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttributes.java:
##
@@ -0,0 +1,275 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
+@UseCase(
+description = "Retain all FlowFile attributes matching a regular
expression",
+configuration = """
+Set "Filter mode" to "Retain".
+Set "Attribute matching strategy" to "Use regular expression".
+Specify the "Regular expression to filter attributes", e.g.
"my-property|a-prefix[.].*".
+"""
+)
+@UseCase(
+description = "Remove only a specified set of FlowFile attributes",
+configuration = """
+Set "Filter mode" to "Remove".
+Set "Attribute matching strategy" to "Enumerate attributes".
+Specify the set of "Set of attributes to filter" using the
delimiter comma ',', e.g. "my-property,other,filename".
+"""
+)
+public class FilterAttributes extends AbstractProcessor {
Review Comment:
I changed the name in code, PR and Jira accordingly. Thanks for the hint.
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttributes.java:
##
@@ -0,0 +1,275 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
[jira] [Updated] (NIFI-12416) ExcelReader additionalDetails not visible in the generated documentation
[
https://issues.apache.org/jira/browse/NIFI-12416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12416:
Description:
This seems to be another remnant of NIFI-12392.In this case the documentation
for ExcelReader is not in the location of the code. Currently its location is
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but its location should be
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
in order for it to be seen in the documentation.
was:
This seems to be another remnant of NIFI-12392.In this case the documentation
for ExcelReader is not in the location of the code. Currently its location is
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but its location should be
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> ExcelReader additionalDetails not visible in the generated documentation
>
>
> Key: NIFI-12416
> URL: https://issues.apache.org/jira/browse/NIFI-12416
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This seems to be another remnant of NIFI-12392.In this case the documentation
> for ExcelReader is not in the location of the code. Currently its location is
> {code:java}
> nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> but its location should be
> {code:java}
> nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> in order for it to be seen in the documentation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (NIFI-12362) Conduct Apache NiFi 1.24.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann resolved NIFI-12362. - Resolution: Fixed > Conduct Apache NiFi 1.24.0 Release > -- > > Key: NIFI-12362 > URL: https://issues.apache.org/jira/browse/NIFI-12362 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: Pierre Villard >Priority: Major > Fix For: 1.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12416) ExcelReader additionalDetails not visible in the generated documentation
[
https://issues.apache.org/jira/browse/NIFI-12416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12416:
Description:
This seems to be another remnant of NIFI-12392.In this case the documentation
for ExcelReader is not in the location of the code. Currently its location is
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but its location should be
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
was:
This seems to be another remnant of NIFI-12392. In this case the documentation
for ExcelReader is not in the location of the code. Currently its location is
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but its location should be
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> ExcelReader additionalDetails not visible in the generated documentation
>
>
> Key: NIFI-12416
> URL: https://issues.apache.org/jira/browse/NIFI-12416
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This seems to be another remnant of NIFI-12392.In this case the documentation
> for ExcelReader is not in the location of the code. Currently its location is
> {code:java}
> nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> but its location should be
> {code:java}
> nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12411) PublishAMQP: Put header values from attributes by matching Regex
[ https://issues.apache.org/jira/browse/NIFI-12411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Handermann updated NIFI-12411: Fix Version/s: (was: 1.24.0) (was: 1.25.0) (was: 2.0.0) > PublishAMQP: Put header values from attributes by matching Regex > > > Key: NIFI-12411 > URL: https://issues.apache.org/jira/browse/NIFI-12411 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.23.2 >Reporter: Umar Hussain >Assignee: Umar Hussain >Priority: Major > > The focus of this ticket is to extend the PublishAMQP processor so that it > can take FlowFile attributes by matching a Regex and then put these > attributes as `headers` map in AMQP message. > Default behavior of the processor stays the same as version `1.23.2` i.e. it > will by default read headers from `amq$headers` attribute and put them in the > AMQP message. > For Regex based match of attributes, a new property is needed which can > switch between reading from `amq$headers` or put attributes matching the > Regex, or it can read from both sources. > In case headers can be read from both sources, an additional property is > needed to set precedence of the source so that if a key is found in both > sources, which will be set in output. > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12416) ExcelReader additionalDetails not visible in the generated documentation
[
https://issues.apache.org/jira/browse/NIFI-12416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12416:
Status: Patch Available (was: Open)
> ExcelReader additionalDetails not visible in the generated documentation
>
>
> Key: NIFI-12416
> URL: https://issues.apache.org/jira/browse/NIFI-12416
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This seems to be another remnant of NIFI-12392. In this case the
> documentation for ExcelReader is not in the location of the code. Currently
> its location is
> {code:java}
> nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> but its location should be
> {code:java}
> nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] NIFI-12416 Relocated the additionalDetails.html to the appropriate bundle in order for it to be seen when generating the documentation. [nifi]
dan-s1 opened a new pull request, #8067: URL: https://github.com/apache/nifi/pull/8067 # Summary [NIFI-12416](https://issues.apache.org/jira/browse/NIFI-12416) # Tracking Please complete the following tracking steps prior to pull request creation. ### Issue Tracking - [ ] [Apache NiFi Jira](https://issues.apache.org/jira/browse/NIFI) issue created ### Pull Request Tracking - [ ] Pull Request title starts with Apache NiFi Jira issue number, such as `NIFI-0` - [ ] Pull Request commit message starts with Apache NiFi Jira issue number, as such `NIFI-0` ### Pull Request Formatting - [ ] Pull Request based on current revision of the `main` branch - [ ] 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] 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] [Updated] (NIFI-12416) ExcelReader additionalDetails not visible in the generated documentation
[
https://issues.apache.org/jira/browse/NIFI-12416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-12416:
Description:
This seems to be another remnant of NIFI-12392. In this case the documentation
for ExcelReader is not in the location of the code. Currently its location is
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but its location should be
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
was:
This seems to be another remnant of NIFI-12392. In this case the documentation
for ExcelReader is not in the location of the code. Currently it is located in
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but it should be located
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> ExcelReader additionalDetails not visible in the generated documentation
>
>
> Key: NIFI-12416
> URL: https://issues.apache.org/jira/browse/NIFI-12416
> Project: Apache NiFi
> Issue Type: Bug
>Reporter: Daniel Stieglitz
>Assignee: Daniel Stieglitz
>Priority: Minor
>
> This seems to be another remnant of NIFI-12392. In this case the
> documentation for ExcelReader is not in the location of the code. Currently
> its location is
> {code:java}
> nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
> but its location should be
> {code:java}
> nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12416) ExcelReader additionalDetails not visible in the generated documentation
Daniel Stieglitz created NIFI-12416:
---
Summary: ExcelReader additionalDetails not visible in the
generated documentation
Key: NIFI-12416
URL: https://issues.apache.org/jira/browse/NIFI-12416
Project: Apache NiFi
Issue Type: Bug
Reporter: Daniel Stieglitz
Assignee: Daniel Stieglitz
This seems to be another remnant of NIFI-12392. In this case the documentation
for ExcelReader is not in the location of the code. Currently it is located in
{code:java}
nifi-nar-bundles/nifi-standard-services/nifi-record-serialization-services-bundle/nifi-record-serialization-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
but it should be located
{code:java}
nifi-nar-bundles/nifi-poi-bundle/nifi-poi-services/src/main/resources/docs/org.apache.nifi.excel.ExcelReader/additionalDetails.html{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-11481) Migrate the Nifi UI to a currently supported/active framework
[ https://issues.apache.org/jira/browse/NIFI-11481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790138#comment-17790138 ] ASF subversion and git services commented on NIFI-11481: Commit b3b6d72924a3a13fefe6ed11732e49fe7f964e46 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b3b6d72924 ] NIFI-11481: Initial migration to Angular 16 (#8053) * NIFI-11481: - Initial project creation. * NIFI-11481: - Install material. - Rename project from nifi-web-frontend to nifi. * NIFI-11481: - Install roboto through package.json. * NIFI-11481: - Add Tailwind. * NIFI-11481: - Basic layout. * NIFI-11481: - Introducing ngrx for storing flow. * NIFI-11481: - Introducing d3. - Adding svg. - Adding defs. - Funnel Manager. * NIFI-11481: - Introducing d3. - Adding svg. - Adding defs. - Funnel Manager. - Adding draggable. - Adding editable. - Adding selectable. - Adding flowfont. - Adding Canvas View. - Adding Transform in Store. - Adding selected in Store. - Adding transition in Store. - Funnel Manager directly subscribes to store. * NIFI-11481: - Adding backend calls. - Refactoring update positions to be for a single component. * NIFI-11481: - Process Group Manager. - Adding font-awesome. - Updating canvas/graph component visibility. - Adding prettier/eslint. * NIFI-11481: - Adding support to enter a process group. * NIFI-11481: - Formatting source. * NIFI-11481: - Label Manager. - Added generic update component. * NIFI-11481: - Processor Manager. * NIFI-11481: - Port Manager. * NIFI-11481: - Remote Process Group Manager. * NIFI-11481: - Adding draggable icons to the toolbar. * NIFI-11481: - Formatting. * NIFI-11481: - Draggable Toolbar. - Create Label, Funnel. * NIFI-11481: - Connection Manager. - Connectable Behavior. * NIFI-11481: - Draggable behavior with back end call for both components and connections. * NIFI-11481: - Selection box. * NIFI-11481: - Port creation. - Port configuration. - Quick Select. * NIFI-11481: - Canvas Tooltips. * NIFI-11481: - Context menu. * NIFI-11481: - Router State. - Reorganization. - Deep linking. * NIFI-11481: - Adding support for Delete. * NIFI-11481: - Flow status bar. * NIFI-11481: - Adding Current User State. - Current user polling. - Fixing Flow Status layout bug. * NIFI-11481: - Process Group Polling. * NIFI-11481: - Process Group Breadcrumbs. * NIFI-11481: - Global Menu. * NIFI-11481: - Search. * NIFI-11481: - Add support for centering components on the canvas. * NIFI-11481: - Add support for persisting and restoring the users view of the current PG. * NIFI-11481: - Fixing centering behavior. - Fixing user view restoration. - Bulk selection auto fit. * NIFI-11481: - Incorporating the new UI into the NiFi build with a build profile that is not active by default. - The new UI is deployed to a different context path than the current UI and works side by side. * NIFI-11481: - Center component from context menu. - Enter process group from context menu. * NIFI-11481: - Adding support to log in. - LoginFilter, LogoutFilter. - Moved the handling of 'include-new-ui' profile to make building with and within more straight forward. - Splash screen while guard executing. - Http request interceptor to show loading on the canvas. - Http request interceptor to handle 401 responses. * NIFI-11481: - Extension Creation Component. - Filter, Usage Restrictions, and selected type. * NIFI-11481: - Stopping polling when unable to connect to server. * NIFI-11481: - Settings - General. * NIFI-11481: - Settings - Management Controller Services. * NIFI-11481: - NiFi Tooltip directive. - Usage Restriction Tip. - Comments Tip. - Validation Errors Tip. - Bulletins Tip. * NIFI-11481: - Settings - Reporting Tasks. * NIFI-11481: - Avoiding unnecessary web requests in route guards. * NIFI-11481: - Edit Controller Service Dialog. - View Property Table. - Update component density. * NIFI-11481: - Supports Controller Service API tooltip and dialog content. * NIFI-11481: - Property table - NF Editor. - Property table - Combo Editor. * NIFI-11481: - Making property table a control value accessor. - Wiring up saving Controller Services from Edit Dialog. - Handling Delete Property. - Handling New Property. - Updating how form submission is triggered throughout to address issue with incidental form submit events. * NIFI-11481: - Moving Settings into pages. * NIFI-11481: - Moving Canvas into pages. * NIFI-11481: - Moving Login into pages. * NIFI-11481: - Adding routing to the Controller Service listing and Reporting Task listing. - Updating Canvas routing to follow similar pattern. * NIFI-11481: - Controller Service references. * NIFI-11481: - Create inline Controller Service. - Edit Controller Service route. - Go To Controller Service from Property Table. - Switching to Event Emitter in New Property dialog. * NIFI-11481: -
[jira] [Commented] (NIFI-12401) Support Parameters in Properties with Allowable Values
[ https://issues.apache.org/jira/browse/NIFI-12401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790139#comment-17790139 ] ASF subversion and git services commented on NIFI-12401: Commit b3b6d72924a3a13fefe6ed11732e49fe7f964e46 in nifi's branch refs/heads/main from Matt Gilman [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=b3b6d72924 ] NIFI-11481: Initial migration to Angular 16 (#8053) * NIFI-11481: - Initial project creation. * NIFI-11481: - Install material. - Rename project from nifi-web-frontend to nifi. * NIFI-11481: - Install roboto through package.json. * NIFI-11481: - Add Tailwind. * NIFI-11481: - Basic layout. * NIFI-11481: - Introducing ngrx for storing flow. * NIFI-11481: - Introducing d3. - Adding svg. - Adding defs. - Funnel Manager. * NIFI-11481: - Introducing d3. - Adding svg. - Adding defs. - Funnel Manager. - Adding draggable. - Adding editable. - Adding selectable. - Adding flowfont. - Adding Canvas View. - Adding Transform in Store. - Adding selected in Store. - Adding transition in Store. - Funnel Manager directly subscribes to store. * NIFI-11481: - Adding backend calls. - Refactoring update positions to be for a single component. * NIFI-11481: - Process Group Manager. - Adding font-awesome. - Updating canvas/graph component visibility. - Adding prettier/eslint. * NIFI-11481: - Adding support to enter a process group. * NIFI-11481: - Formatting source. * NIFI-11481: - Label Manager. - Added generic update component. * NIFI-11481: - Processor Manager. * NIFI-11481: - Port Manager. * NIFI-11481: - Remote Process Group Manager. * NIFI-11481: - Adding draggable icons to the toolbar. * NIFI-11481: - Formatting. * NIFI-11481: - Draggable Toolbar. - Create Label, Funnel. * NIFI-11481: - Connection Manager. - Connectable Behavior. * NIFI-11481: - Draggable behavior with back end call for both components and connections. * NIFI-11481: - Selection box. * NIFI-11481: - Port creation. - Port configuration. - Quick Select. * NIFI-11481: - Canvas Tooltips. * NIFI-11481: - Context menu. * NIFI-11481: - Router State. - Reorganization. - Deep linking. * NIFI-11481: - Adding support for Delete. * NIFI-11481: - Flow status bar. * NIFI-11481: - Adding Current User State. - Current user polling. - Fixing Flow Status layout bug. * NIFI-11481: - Process Group Polling. * NIFI-11481: - Process Group Breadcrumbs. * NIFI-11481: - Global Menu. * NIFI-11481: - Search. * NIFI-11481: - Add support for centering components on the canvas. * NIFI-11481: - Add support for persisting and restoring the users view of the current PG. * NIFI-11481: - Fixing centering behavior. - Fixing user view restoration. - Bulk selection auto fit. * NIFI-11481: - Incorporating the new UI into the NiFi build with a build profile that is not active by default. - The new UI is deployed to a different context path than the current UI and works side by side. * NIFI-11481: - Center component from context menu. - Enter process group from context menu. * NIFI-11481: - Adding support to log in. - LoginFilter, LogoutFilter. - Moved the handling of 'include-new-ui' profile to make building with and within more straight forward. - Splash screen while guard executing. - Http request interceptor to show loading on the canvas. - Http request interceptor to handle 401 responses. * NIFI-11481: - Extension Creation Component. - Filter, Usage Restrictions, and selected type. * NIFI-11481: - Stopping polling when unable to connect to server. * NIFI-11481: - Settings - General. * NIFI-11481: - Settings - Management Controller Services. * NIFI-11481: - NiFi Tooltip directive. - Usage Restriction Tip. - Comments Tip. - Validation Errors Tip. - Bulletins Tip. * NIFI-11481: - Settings - Reporting Tasks. * NIFI-11481: - Avoiding unnecessary web requests in route guards. * NIFI-11481: - Edit Controller Service Dialog. - View Property Table. - Update component density. * NIFI-11481: - Supports Controller Service API tooltip and dialog content. * NIFI-11481: - Property table - NF Editor. - Property table - Combo Editor. * NIFI-11481: - Making property table a control value accessor. - Wiring up saving Controller Services from Edit Dialog. - Handling Delete Property. - Handling New Property. - Updating how form submission is triggered throughout to address issue with incidental form submit events. * NIFI-11481: - Moving Settings into pages. * NIFI-11481: - Moving Canvas into pages. * NIFI-11481: - Moving Login into pages. * NIFI-11481: - Adding routing to the Controller Service listing and Reporting Task listing. - Updating Canvas routing to follow similar pattern. * NIFI-11481: - Controller Service references. * NIFI-11481: - Create inline Controller Service. - Edit Controller Service route. - Go To Controller Service from Property Table. - Switching to Event Emitter in New Property dialog. * NIFI-11481: -
Re: [PR] NIFI-11481: Initial migration to Angular 16 [nifi]
rfellows merged PR #8053: URL: https://github.com/apache/nifi/pull/8053 -- 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] (MINIFICPP-2267) Add openssl dylib to package on intel macos
Adam Debreceni created MINIFICPP-2267: - Summary: Add openssl dylib to package on intel macos Key: MINIFICPP-2267 URL: https://issues.apache.org/jira/browse/MINIFICPP-2267 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Adam Debreceni Assignee: Adam Debreceni -- This message was sent by Atlassian Jira (v8.20.10#820010)
[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 ] Rob Fellows 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 * Counters (NIFI-12415) * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * 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 * Configure Processor ** Service Link ** Create inline Service ** Parameter Link ** Convert to Parameter * 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 [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 * Counters * Bulletin Board * Provenance ** Replay from context menu * Flow Analysis Rules * Registry Clients * 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 * Configure Processor ** Service Link ** Create inline Service ** Parameter Link ** Convert to Parameter * 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 [1] [https://github.com/apache/nifi/pull/8053] > Remaining items to migrate UI to currently supported/active framework > - > > Key: NIFI-12400 > URL: https://issues.apache.org/jira/browse/NIFI-12400 > Project: Apache NiFi > Issue Type: Improvement > Components: Core UI >Reporter: Matt Gilman >Assignee: Matt Gilman >Priority: Major > > 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 > * Counters (NIFI-12415) > * Bulletin Board > * Provenance > ** Replay from context menu > * Flow Analysis Rules > * Registry Clients > * 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 > * Configure Processor > ** Service Link > ** Create inline Service > ** Parameter Link > ** Convert to Parameter > * 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 > [1] [https://github.com/apache/nifi/pull/8053] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12415) Counters
Rob Fellows created NIFI-12415: -- Summary: Counters Key: NIFI-12415 URL: https://issues.apache.org/jira/browse/NIFI-12415 Project: Apache NiFi Issue Type: Sub-task Reporter: Rob Fellows Assignee: Rob Fellows Add Counters page. Add Counters menu option. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12386) Add a FilterAttribute processor
[
https://issues.apache.org/jira/browse/NIFI-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
endzeit updated NIFI-12386:
---
Summary: Add a FilterAttribute processor (was: Add a FilterAttributes
processor)
> Add a FilterAttribute processor
> ---
>
> Key: NIFI-12386
> URL: https://issues.apache.org/jira/browse/NIFI-12386
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Core Framework
>Reporter: endzeit
>Assignee: endzeit
>Priority: Major
> Time Spent: 10.5h
> Remaining Estimate: 0h
>
> Flows in Apache NiFi can get quite sophisticated, consisting of a long chains
> of both {{ProcessGroup}} and {{Processor}} components.
> Oftentimes {{Processor}} components, including those in the NiFi standard
> bundle, enrich an incoming {{FlowFile}} with additional FlowFile attributes.
> This can lead to a fair amount of different FlowFile attributes accumulating
> over the FlowFile's lifecycle.
> In order to prevent subsequent {{ProcessGroup}} / {{Processor}} components to
> accidentally rely on implementation details of preceding components, a good
> practice is to:
> # define which FlowFile attributes should exist at selected points in the
> {{Flow}}
> # reduce the attributes of the FlowFile at the selected point to those
> defined
> This can be achieved by using the
> [UpdateAttribute|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.23.2/org.apache.nifi.processors.attributes.UpdateAttribute/index.html]
> processor of the standard processor bundle.
> However, the {{UpdateAttribute}} processor allows only for a regular
> expression to define a set of attributes to remove. Instead, the outlined
> practice above desires to explicitly state a set of attributes to keep. One
> can do so with a regular expression as well, but writing the reverse lookup
> to achieve this is not the easiest endeavor to put it mildly.
> This issue proposes a new processor {{FilterAttributes}} to be added to the
> library of {{{}nifi-standard-processors{}}}, which can be configured with a
> set of attributes and removes all attributes of an incoming FlowFile other
> than the ones configured.
> The processor should
> * have a required, non-blank property "Attributes to keep", which takes a
> list of attribute names separated by delimiter, e.g. comma (,).
> ** trailing whitespace around attribute names should be ignored
> ** leading or trailing delimiters should be ignored
> * have a required, non-blank property "Delimiter", which is used to delimit
> the individual attribute names, with a default value of "," (comma).
> * have a single relationship "success" to which all FlowFiles are routed,
> similar to {{UpdateAttribute}}
> * have an
> [InputRequirement|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/InputRequirement.html]
> of
> [INPUT_REQUIRED|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/InputRequirement.Requirement.html]
> *
> [@SupportsBatching|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/SupportsBatching.html]
> * be
> [@SideEffectFree|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/SideEffectFree.html]
> Some possible extension might be:
> * have a required property "Core attributes", with allowable values of "Keep
> UUID only", "Keep all", with a default of "Keep UUID only"
> ** an additional allowable value e.g. "Specify behaviour" may be added,
> which allows for more customization
> * have a required property "Mode", with allowable values of "Retain" and
> "Remove", with a default of "Retain"
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (NIFI-12386) Add a FilterAttribute processor
[
https://issues.apache.org/jira/browse/NIFI-12386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
endzeit updated NIFI-12386:
---
Description:
Flows in Apache NiFi can get quite sophisticated, consisting of a long chains
of both {{ProcessGroup}} and {{Processor}} components.
Oftentimes {{Processor}} components, including those in the NiFi standard
bundle, enrich an incoming {{FlowFile}} with additional FlowFile attributes.
This can lead to a fair amount of different FlowFile attributes accumulating
over the FlowFile's lifecycle.
In order to prevent subsequent {{ProcessGroup}} / {{Processor}} components to
accidentally rely on implementation details of preceding components, a good
practice is to:
# define which FlowFile attributes should exist at selected points in the
{{Flow}}
# reduce the attributes of the FlowFile at the selected point to those defined
This can be achieved by using the
[UpdateAttribute|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.23.2/org.apache.nifi.processors.attributes.UpdateAttribute/index.html]
processor of the standard processor bundle.
However, the {{UpdateAttribute}} processor allows only for a regular expression
to define a set of attributes to remove. Instead, the outlined practice above
desires to explicitly state a set of attributes to keep. One can do so with a
regular expression as well, but writing the reverse lookup to achieve this is
not the easiest endeavor to put it mildly.
This issue proposes a new processor {{FilterAttribute}} to be added to the
library of {{{}nifi-standard-processors{}}}, which can be configured with a set
of attributes and removes all attributes of an incoming FlowFile other than the
ones configured.
The processor should
* have a required, non-blank property "Attributes to keep", which takes a list
of attribute names separated by delimiter, e.g. comma (,).
** trailing whitespace around attribute names should be ignored
** leading or trailing delimiters should be ignored
* have a required, non-blank property "Delimiter", which is used to delimit
the individual attribute names, with a default value of "," (comma).
* have a single relationship "success" to which all FlowFiles are routed,
similar to {{UpdateAttribute}}
* have an
[InputRequirement|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/InputRequirement.html]
of
[INPUT_REQUIRED|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/InputRequirement.Requirement.html]
*
[@SupportsBatching|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/SupportsBatching.html]
* be
[@SideEffectFree|https://www.javadoc.io/doc/org.apache.nifi/nifi-api/latest/org/apache/nifi/annotation/behavior/SideEffectFree.html]
Some possible extension might be:
* have a required property "Core attributes", with allowable values of "Keep
UUID only", "Keep all", with a default of "Keep UUID only"
** an additional allowable value e.g. "Specify behaviour" may be added, which
allows for more customization
* have a required property "Mode", with allowable values of "Retain" and
"Remove", with a default of "Retain"
was:
Flows in Apache NiFi can get quite sophisticated, consisting of a long chains
of both {{ProcessGroup}} and {{Processor}} components.
Oftentimes {{Processor}} components, including those in the NiFi standard
bundle, enrich an incoming {{FlowFile}} with additional FlowFile attributes.
This can lead to a fair amount of different FlowFile attributes accumulating
over the FlowFile's lifecycle.
In order to prevent subsequent {{ProcessGroup}} / {{Processor}} components to
accidentally rely on implementation details of preceding components, a good
practice is to:
# define which FlowFile attributes should exist at selected points in the
{{Flow}}
# reduce the attributes of the FlowFile at the selected point to those defined
This can be achieved by using the
[UpdateAttribute|https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-update-attribute-nar/1.23.2/org.apache.nifi.processors.attributes.UpdateAttribute/index.html]
processor of the standard processor bundle.
However, the {{UpdateAttribute}} processor allows only for a regular expression
to define a set of attributes to remove. Instead, the outlined practice above
desires to explicitly state a set of attributes to keep. One can do so with a
regular expression as well, but writing the reverse lookup to achieve this is
not the easiest endeavor to put it mildly.
This issue proposes a new processor {{FilterAttributes}} to be added to the
library of {{{}nifi-standard-processors{}}}, which can be configured with a set
of attributes and removes all attributes of an incoming FlowFile other than the
ones configured.
The processor should
* have a required,
Re: [PR] NIFI-12386 Adds processor FilterAttributes [nifi]
exceptionfactory commented on code in PR #8049:
URL: https://github.com/apache/nifi/pull/8049#discussion_r1406223826
##
nifi-nar-bundles/nifi-standard-bundle/nifi-standard-processors/src/main/java/org/apache/nifi/processors/standard/FilterAttributes.java:
##
@@ -0,0 +1,275 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.nifi.processors.standard;
+
+import org.apache.nifi.annotation.behavior.DefaultRunDuration;
+import org.apache.nifi.annotation.behavior.InputRequirement;
+import org.apache.nifi.annotation.behavior.SideEffectFree;
+import org.apache.nifi.annotation.behavior.SupportsBatching;
+import org.apache.nifi.annotation.documentation.CapabilityDescription;
+import org.apache.nifi.annotation.documentation.Tags;
+import org.apache.nifi.annotation.documentation.UseCase;
+import org.apache.nifi.annotation.lifecycle.OnScheduled;
+import org.apache.nifi.components.AllowableValue;
+import org.apache.nifi.components.PropertyDescriptor;
+import org.apache.nifi.expression.ExpressionLanguageScope;
+import org.apache.nifi.flowfile.FlowFile;
+import org.apache.nifi.processor.AbstractProcessor;
+import org.apache.nifi.processor.ProcessContext;
+import org.apache.nifi.processor.ProcessSession;
+import org.apache.nifi.processor.Relationship;
+import org.apache.nifi.processor.exception.ProcessException;
+import org.apache.nifi.processor.util.StandardValidators;
+
+import java.util.Arrays;
+import java.util.Collections;
+import java.util.HashSet;
+import java.util.List;
+import java.util.Set;
+import java.util.function.Predicate;
+import java.util.regex.Pattern;
+import java.util.stream.Collectors;
+
+@SideEffectFree
+@SupportsBatching(defaultDuration = DefaultRunDuration.TWENTY_FIVE_MILLIS)
+@InputRequirement(InputRequirement.Requirement.INPUT_REQUIRED)
+@Tags({"attributes", "modification", "filter", "retain", "remove", "delete",
"regex", "regular expression", "Attribute Expression Language"})
+@CapabilityDescription("Filters the Attributes of a FlowFile according to a
specified strategy")
+@UseCase(
+description = "Retain all FlowFile attributes matching a regular
expression",
+configuration = """
+Set "Filter mode" to "Retain".
+Set "Attribute matching strategy" to "Use regular expression".
+Specify the "Regular expression to filter attributes", e.g.
"my-property|a-prefix[.].*".
+"""
+)
+@UseCase(
+description = "Remove only a specified set of FlowFile attributes",
+configuration = """
+Set "Filter mode" to "Remove".
+Set "Attribute matching strategy" to "Enumerate attributes".
+Specify the set of "Set of attributes to filter" using the
delimiter comma ',', e.g. "my-property,other,filename".
+"""
+)
+public class FilterAttributes extends AbstractProcessor {
Review Comment:
One note on naming, Processors generally avoid plurals in the class name, so
for this to go forward, the name should be `FilterAttribute`.
--
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
[PR] NIFI-12414 Update org.apache.commons.lang3.version to 3.14.0 [nifi]
mr1716 opened a new pull request, #8066: URL: https://github.com/apache/nifi/pull/8066 # Summary [NIFI-12414](https://issues.apache.org/jira/browse/NIFI-12414) # 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-12414) 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 - [ ] Build completed using `mvn clean install -P contrib-check` - [ ] 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-12414) Update org.apache.commons.lang3.version to 3.14.0
Mike R created NIFI-12414: - Summary: Update org.apache.commons.lang3.version to 3.14.0 Key: NIFI-12414 URL: https://issues.apache.org/jira/browse/NIFI-12414 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.23.2, 2.latest, 1.24.0 Reporter: Mike R Update org.apache.commons.lang3.version to 3.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12414) Update org.apache.commons.lang3.version to 3.14.0
[ https://issues.apache.org/jira/browse/NIFI-12414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike R reassigned NIFI-12414: - Assignee: Mike R > Update org.apache.commons.lang3.version to 3.14.0 > - > > Key: NIFI-12414 > URL: https://issues.apache.org/jira/browse/NIFI-12414 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 2.latest, 1.24.0, 1.23.2 >Reporter: Mike R >Assignee: Mike R >Priority: Major > > Update org.apache.commons.lang3.version to 3.14.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-11481: Initial migration to Angular 16 [nifi]
rfellows commented on code in PR #8053: URL: https://github.com/apache/nifi/pull/8053#discussion_r1406142353 ## nifi-nar-bundles/nifi-framework-bundle/nifi-framework/nifi-web/nifi-web-frontend/src/main/nifi/package.json: ## @@ -6,7 +6,7 @@ "start": "ng serve", "build": "ng build", "watch": "ng build --watch --configuration development", -"test": "ng test", +"test": "ng test --karma-config=karma.conf.js", Review Comment: @mcgilman, Currently, running `npm run test` just hangs and doesn't complete. We have a few options: * update this script to: `"test": "ng test --karma-config=karma.conf.js --watch=false",` * add another script: `"test-no-watch": "ng test --karma-config=karma.conf.js --watch=false",` * update the karma.conf.js to specify this is a `singleRun` test by adding `singleRun: true` * add another karma configuration for the singleRun of tests. -- 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-12362) Conduct Apache NiFi 1.24.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790040#comment-17790040 ] ASF subversion and git services commented on NIFI-12362: Commit 7fedb49a9ac4e27448d8354f16c16ed6f7784c8f in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=7fedb49a9a ] NIFI-12362-RC5 prepare for next development iteration > Conduct Apache NiFi 1.24.0 Release > -- > > Key: NIFI-12362 > URL: https://issues.apache.org/jira/browse/NIFI-12362 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: Pierre Villard >Priority: Major > Fix For: 1.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12362) Conduct Apache NiFi 1.24.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790039#comment-17790039 ] ASF subversion and git services commented on NIFI-12362: Commit 5241f434829ca46a26a475600ef7c00e1e271e37 in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5241f43482 ] NIFI-12362-RC5 prepare release nifi-1.24.0-RC5 > Conduct Apache NiFi 1.24.0 Release > -- > > Key: NIFI-12362 > URL: https://issues.apache.org/jira/browse/NIFI-12362 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: Pierre Villard >Priority: Major > Fix For: 1.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-12362) Conduct Apache NiFi 1.24.0 Release
[ https://issues.apache.org/jira/browse/NIFI-12362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17790041#comment-17790041 ] ASF subversion and git services commented on NIFI-12362: Commit c5c5013b9b7165554a76932b99a11beb2153db06 in nifi's branch refs/heads/support/nifi-1.x from Pierre Villard [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=c5c5013b9b ] Merge branch 'NIFI-12362-RC5' into support/nifi-1.x > Conduct Apache NiFi 1.24.0 Release > -- > > Key: NIFI-12362 > URL: https://issues.apache.org/jira/browse/NIFI-12362 > Project: Apache NiFi > Issue Type: Task >Reporter: David Handermann >Assignee: Pierre Villard >Priority: Major > Fix For: 1.24.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] MINIFICPP-1951 - Prevent append overwriting resource [nifi-minifi-cpp]
adamdebreceni commented on code in PR #1640:
URL: https://github.com/apache/nifi-minifi-cpp/pull/1640#discussion_r1405967282
##
libminifi/include/core/StreamAppendLock.h:
##
@@ -0,0 +1,27 @@
+/**
+ * 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.
+ */
+#pragma once
+
+
+namespace org::apache::nifi::minifi::core {
+
+class StreamAppendLock {
Review Comment:
done
--
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
