Re: [PR] NIFI-12452 Improve support for DescribedValue [nifi]
EndzeitBegins commented on PR #8102: URL: https://github.com/apache/nifi/pull/8102#issuecomment-1837946154 Thank you for your feedback @exceptionfactory and @markap14. I renamed `defaultDescribedValue(DescribedValue)` to `defaultValue(DescribedValue)` making it an overload of the existing `defaultValue(String)`. In this process I also removed all calls to `defaultValue` that statically provide `null` I could find in the codebase. All these calls were effectively doing nothing, as the existing implementation of `defaultValue` just returns the `PropertyDescriptor.Builder` without any modification upon receiving `null`. I assumed this is a more straightforward change than keeping the calls but as `defaultValue((String) null)`. -- 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-12390 add more jvm metrics to 1.x line [nifi]
esecules closed pull request #8062: Nifi-12390 add more jvm metrics to 1.x line URL: https://github.com/apache/nifi/pull/8062 -- 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-12390 more jvm metrics [nifi]
esecules closed pull request #8050: NIFI-12390 more jvm metrics URL: https://github.com/apache/nifi/pull/8050 -- 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-12459) The node disconnection on nifi cluster mode. Failed to connect to cluster due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket to nifi-2/
[
https://issues.apache.org/jira/browse/NIFI-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Joseph updated NIFI-12459:
---
Description:
This issue has been observed in both 1.22 and 1.23.2Nifi is running in cluster
mode in k8s (3 pods), Embedded zookeeper is enabled. The nodes appear to be
disconnected, there is a pop up that says.
This node is currently not connected to the cluster. Any modifications to the
data flow made here will not replicate across the cluster. (PFA)
2 out of 3 nifi pods are having the below message:
[Clustering Tasks Thread-3] o.apache.nifi.controller.FlowController Failed to
send heartbeat due to: org.apache.nifi.cluster.protocol.ProtocolException:
Failed to send message to Cluster Coordinator
So we :
executed to pods having the issue (kubectl exec -it bash),
proceed to opt/nifi/data/conf_directory ,
delete the flow.xml.gz file,
exit the pod,
delete the pod using kubectl delete po command .
{_}This was once suggested to us by one of the members here.{_}RESULT:
The pods came back up, but the UI this time had a different error.
The Flow Controller is initializing the Data Flow(PFA).
The logs do not have any exception stack trace but only this.
[main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster due
to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket
to nifi-2/:11443 due to: java.net.UnknownHostException: nifi-2
The node disconnection has been happening for us here and there (not frequent)
!image-2023-12-04-10-11-08-601.png|width=762,height=382!
!image-2023-12-04-10-11-53-220.png!
was:
This issue has been observed in both 1.22 and 1.23.2Nifi is running in cluster
mode in k8s (3 pods), Embedded zookeeper is enabled. The nodes appear to be
disconnected, there is a pop up that says.
This node is currently not connected to the cluster. Any modifications to the
data flow made here will not replicate across the cluster. (PFA)
So we :
executed to pods having the issue (kubectl exec -it bash),
proceed to opt/nifi/data/conf_directory ,
delete the flow.xml.gz file,
exit the pod,
delete the pod using kubectl delete po command .
{_}This was once suggested to us by one of the members here.{_}RESULT:
The pods came back up, but the UI this time had a different error.
The Flow Controller is initializing the Data Flow(PFA).
The logs do not have any exception stack trace but only this.
[main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster due
to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket
to nifi-2/:11443 due to: java.net.UnknownHostException: nifi-2
The node disconnection has been happening for us here and there (not frequent)
!image-2023-12-04-10-11-08-601.png|width=762,height=382!
!image-2023-12-04-10-11-53-220.png!
> The node disconnection on nifi cluster mode. Failed to connect to cluster due
> to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create
> socket to nifi-2/:11443 due to: java.net.UnknownHostException
>
>
> Key: NIFI-12459
> URL: https://issues.apache.org/jira/browse/NIFI-12459
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
>Affects Versions: 1.22.0, 1.23.2
>Reporter: John Joseph
>Priority: Major
> Attachments: image-2023-12-04-10-11-08-601.png,
> image-2023-12-04-10-11-53-220.png
>
>
> This issue has been observed in both 1.22 and 1.23.2Nifi is running in
> cluster mode in k8s (3 pods), Embedded zookeeper is enabled. The nodes appear
> to be disconnected, there is a pop up that says.
> This node is currently not connected to the cluster. Any modifications to the
> data flow made here will not replicate across the cluster. (PFA)
> 2 out of 3 nifi pods are having the below message:
> [Clustering Tasks Thread-3] o.apache.nifi.controller.FlowController Failed to
> send heartbeat due to: org.apache.nifi.cluster.protocol.ProtocolException:
> Failed to send message to Cluster Coordinator
> So we :
> executed to pods having the issue (kubectl exec -it
> bash),
> proceed to opt/nifi/data/conf_directory ,
> delete the flow.xml.gz file,
> exit the pod,
> delete the pod using kubectl delete po command .
> {_}This was once suggested to us by one of the members here.{_}RESULT:
> The pods came back up, but the UI this time had a different error.
> The Flow Controller is initializing the Data Flow(PFA).
> The logs do not have any exception stack trace but only this.
> [main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster
> due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed
Re: [PR] NIFI-11958 Azure Data Explorer as sink [nifi]
tanmaya-panda1 commented on PR #7624: URL: https://github.com/apache/nifi/pull/7624#issuecomment-1837866306 @exceptionfactory : Can you please take a look at this PR. This is long pending item, we wanted to close this before the end of this year. We would appreciate your review on this item whenever you have some time. -- 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-12459) The node disconnection on nifi cluster mode. Failed to connect to cluster due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket to nifi-2/
[
https://issues.apache.org/jira/browse/NIFI-12459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Joseph updated NIFI-12459:
---
Summary: The node disconnection on nifi cluster mode. Failed to connect to
cluster due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to
create socket to nifi-2/:11443 due to:
java.net.UnknownHostException (was: The node disconnection on nifi cluster
mode, java.net.UnknownHostException:)
> The node disconnection on nifi cluster mode. Failed to connect to cluster due
> to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create
> socket to nifi-2/:11443 due to: java.net.UnknownHostException
>
>
> Key: NIFI-12459
> URL: https://issues.apache.org/jira/browse/NIFI-12459
> Project: Apache NiFi
> Issue Type: Bug
> Components: NiFi Stateless
>Affects Versions: 1.22.0, 1.23.2
>Reporter: John Joseph
>Priority: Major
> Attachments: image-2023-12-04-10-11-08-601.png,
> image-2023-12-04-10-11-53-220.png
>
>
> This issue has been observed in both 1.22 and 1.23.2Nifi is running in
> cluster mode in k8s (3 pods), Embedded zookeeper is enabled. The nodes appear
> to be disconnected, there is a pop up that says.
> This node is currently not connected to the cluster. Any modifications to the
> data flow made here will not replicate across the cluster. (PFA)
> So we :
> executed to pods having the issue (kubectl exec -it
> bash),
> proceed to opt/nifi/data/conf_directory ,
> delete the flow.xml.gz file,
> exit the pod,
> delete the pod using kubectl delete po command .
> {_}This was once suggested to us by one of the members here.{_}RESULT:
> The pods came back up, but the UI this time had a different error.
> The Flow Controller is initializing the Data Flow(PFA).
> The logs do not have any exception stack trace but only this.
> [main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster
> due to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create
> socket to nifi-2/:11443 due to: java.net.UnknownHostException:
> nifi-2
> The node disconnection has been happening for us here and there (not frequent)
>
> !image-2023-12-04-10-11-08-601.png|width=762,height=382!
> !image-2023-12-04-10-11-53-220.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (NIFI-12459) The node disconnection on nifi cluster mode, java.net.UnknownHostException:
John Joseph created NIFI-12459:
--
Summary: The node disconnection on nifi cluster mode,
java.net.UnknownHostException:
Key: NIFI-12459
URL: https://issues.apache.org/jira/browse/NIFI-12459
Project: Apache NiFi
Issue Type: Bug
Components: NiFi Stateless
Affects Versions: 1.23.2, 1.22.0
Reporter: John Joseph
Attachments: image-2023-12-04-10-11-08-601.png,
image-2023-12-04-10-11-53-220.png
This issue has been observed in both 1.22 and 1.23.2Nifi is running in cluster
mode in k8s (3 pods), Embedded zookeeper is enabled. The nodes appear to be
disconnected, there is a pop up that says.
This node is currently not connected to the cluster. Any modifications to the
data flow made here will not replicate across the cluster. (PFA)
So we :
executed to pods having the issue (kubectl exec -it bash),
proceed to opt/nifi/data/conf_directory ,
delete the flow.xml.gz file,
exit the pod,
delete the pod using kubectl delete po command .
{_}This was once suggested to us by one of the members here.{_}RESULT:
The pods came back up, but the UI this time had a different error.
The Flow Controller is initializing the Data Flow(PFA).
The logs do not have any exception stack trace but only this.
[main] o.a.nifi.controller.StandardFlowService Failed to connect to cluster due
to: org.apache.nifi.cluster.protocol.ProtocolException: Failed to create socket
to nifi-2/:11443 due to: java.net.UnknownHostException: nifi-2
The node disconnection has been happening for us here and there (not frequent)
!image-2023-12-04-10-11-08-601.png|width=762,height=382!
!image-2023-12-04-10-11-53-220.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[PR] Update Dockerfile for alpine v3 / liberica v21 [nifi]
hawko2600 opened a new pull request, #8111: URL: https://github.com/apache/nifi/pull/8111 Alter Dockerfile to rebase on Alpine Linux v3 with Liberica OpenJDK v21 for NiFi 2.0.0 # 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 - [ ] [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
[PR] NIFI-12458: Upgrade Groovy to 4.0.16 from 4.0.15 [nifi]
mattyb149 opened a new pull request, #8110: URL: https://github.com/apache/nifi/pull/8110 # Summary [NIFI-12458](https://issues.apache.org/jira/browse/NIFI-12458) Includes bug fixes and dependency upgrades (see Jira for details) # 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 - [x] 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) - [x] 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-12458) Update to Groovy 4.0.16 from 4.0.15
Matt Burgess created NIFI-12458: --- Summary: Update to Groovy 4.0.16 from 4.0.15 Key: NIFI-12458 URL: https://issues.apache.org/jira/browse/NIFI-12458 Project: Apache NiFi Issue Type: Improvement Components: Extensions Reporter: Matt Burgess Fix For: 2.0.0 There are some fixes in the latest Groovy release (https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12353637) notably GROOVY-8948, GROOVY-11189, GROOVY-11206, and GROOVY-11209 and a number of dependency upgrades. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12458) Update to Groovy 4.0.16 from 4.0.15
[ https://issues.apache.org/jira/browse/NIFI-12458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned NIFI-12458: --- Assignee: Matt Burgess > Update to Groovy 4.0.16 from 4.0.15 > --- > > Key: NIFI-12458 > URL: https://issues.apache.org/jira/browse/NIFI-12458 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions >Reporter: Matt Burgess >Assignee: Matt Burgess >Priority: Major > Fix For: 2.0.0 > > > There are some fixes in the latest Groovy release > (https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318123&version=12353637) > notably GROOVY-8948, GROOVY-11189, GROOVY-11206, and GROOVY-11209 and a > number of dependency upgrades. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-12318) GenerateRecord could not generate bytes data
[ https://issues.apache.org/jira/browse/NIFI-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-12318: Affects Version/s: (was: 1.23.2) Status: Patch Available (was: In Progress) > GenerateRecord could not generate bytes data > > > Key: NIFI-12318 > URL: https://issues.apache.org/jira/browse/NIFI-12318 > Project: Apache NiFi > Issue Type: Bug > Environment: Apache Nifi 1.23.2 > jdk verson:11.0.20 >Reporter: Ashley >Assignee: Matt Burgess >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Attachments: image-2023-11-06-18-49-08-984.png, > image-2023-11-06-18-49-50-676.png, image-2023-11-06-18-50-59-897.png, > image-2023-11-06-18-51-41-326.png, image-2023-11-06-18-52-07-939.png, > image-2023-11-06-18-52-10-969.png > > Time Spent: 10m > Remaining Estimate: 0h > > I tried to generate bytes data using GenerateRecord,but encountered ERROR. > The ERROR: > !image-2023-11-06-18-52-10-969.png! > GenerateRecord properties: > !image-2023-11-06-18-49-50-676.png! > Schema Text: > !image-2023-11-06-18-49-08-984.png! > AvroRecordSetWriter properteis: > !image-2023-11-06-18-50-59-897.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12318: Fixed byte array generation in GenerateRecord [nifi]
mattyb149 opened a new pull request, #8109: URL: https://github.com/apache/nifi/pull/8109 # Summary [NIFI-12318](https://issues.apache.org/jira/browse/NIFI-12318) GenerateRecords just needs to enforce `byte` type of the generated number(s). # 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 - [ ] 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] [Updated] (NIFI-12318) GenerateRecord could not generate bytes data
[ https://issues.apache.org/jira/browse/NIFI-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess updated NIFI-12318: Fix Version/s: 1.25.0 2.0.0 > GenerateRecord could not generate bytes data > > > Key: NIFI-12318 > URL: https://issues.apache.org/jira/browse/NIFI-12318 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.23.2 > Environment: Apache Nifi 1.23.2 > jdk verson:11.0.20 >Reporter: Ashley >Assignee: Matt Burgess >Priority: Major > Fix For: 1.25.0, 2.0.0 > > Attachments: image-2023-11-06-18-49-08-984.png, > image-2023-11-06-18-49-50-676.png, image-2023-11-06-18-50-59-897.png, > image-2023-11-06-18-51-41-326.png, image-2023-11-06-18-52-07-939.png, > image-2023-11-06-18-52-10-969.png > > > I tried to generate bytes data using GenerateRecord,but encountered ERROR. > The ERROR: > !image-2023-11-06-18-52-10-969.png! > GenerateRecord properties: > !image-2023-11-06-18-49-50-676.png! > Schema Text: > !image-2023-11-06-18-49-08-984.png! > AvroRecordSetWriter properteis: > !image-2023-11-06-18-50-59-897.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-12318) GenerateRecord could not generate bytes data
[ https://issues.apache.org/jira/browse/NIFI-12318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Burgess reassigned NIFI-12318: --- Assignee: Matt Burgess > GenerateRecord could not generate bytes data > > > Key: NIFI-12318 > URL: https://issues.apache.org/jira/browse/NIFI-12318 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.23.2 > Environment: Apache Nifi 1.23.2 > jdk verson:11.0.20 >Reporter: Ashley >Assignee: Matt Burgess >Priority: Major > Attachments: image-2023-11-06-18-49-08-984.png, > image-2023-11-06-18-49-50-676.png, image-2023-11-06-18-50-59-897.png, > image-2023-11-06-18-51-41-326.png, image-2023-11-06-18-52-07-939.png, > image-2023-11-06-18-52-10-969.png > > > I tried to generate bytes data using GenerateRecord,but encountered ERROR. > The ERROR: > !image-2023-11-06-18-52-10-969.png! > GenerateRecord properties: > !image-2023-11-06-18-49-50-676.png! > Schema Text: > !image-2023-11-06-18-49-08-984.png! > AvroRecordSetWriter properteis: > !image-2023-11-06-18-50-59-897.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12453, NIFI-12454: Allow easily determining cluster state of a n… [nifi]
markap14 commented on PR #8100: URL: https://github.com/apache/nifi/pull/8100#issuecomment-1837601257 Yeah fair, @exceptionfactory, I didn't really intend to include that in there, was just some doc updates that I was working on previously and forgot to stash them away :) Have moved them into a new PR. -- 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-12457: Added additional use case based documentation and fixed s… [nifi]
markap14 opened a new pull request, #8108: URL: https://github.com/apache/nifi/pull/8108 …ome typos/made some clarifications in related docs # 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 - [ ] [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-12457) Add Use Case documentation to explain how to use RouteOnAttribute for specific use cases
[ https://issues.apache.org/jira/browse/NIFI-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-12457: -- Status: Patch Available (was: Open) > Add Use Case documentation to explain how to use RouteOnAttribute for > specific use cases > > > Key: NIFI-12457 > URL: https://issues.apache.org/jira/browse/NIFI-12457 > Project: Apache NiFi > Issue Type: Improvement >Reporter: Mark Payne >Assignee: Mark Payne >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > Add @MultiProcessorUseCase that explains how to use RouteOnAttribute in > conjunction with List/Fetch S3 in order to fetch only specific files. > Also add documentation showing how to use RouteOnAttribute alongside > PartitionRecord in order to route record-oriented data based on the contents > of the FlowFile -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-12457) Add Use Case documentation to explain how to use RouteOnAttribute for specific use cases
Mark Payne created NIFI-12457: - Summary: Add Use Case documentation to explain how to use RouteOnAttribute for specific use cases Key: NIFI-12457 URL: https://issues.apache.org/jira/browse/NIFI-12457 Project: Apache NiFi Issue Type: Improvement Reporter: Mark Payne Assignee: Mark Payne Add @MultiProcessorUseCase that explains how to use RouteOnAttribute in conjunction with List/Fetch S3 in order to fetch only specific files. Also add documentation showing how to use RouteOnAttribute alongside PartitionRecord in order to route record-oriented data based on the contents of the FlowFile -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [PR] NIFI-12452 Improve support for DescribedValue [nifi]
markap14 commented on code in PR #8102:
URL: https://github.com/apache/nifi/pull/8102#discussion_r1413205387
##
nifi-api/src/main/java/org/apache/nifi/components/PropertyDescriptor.java:
##
@@ -313,6 +313,27 @@ public Builder defaultValue(final String value) {
return this;
}
+/**
+ * Specifies the initial value and the default value that will be used
+ * if the user does not specify a value. When {@link #build()} is
+ * called, if Allowable Values have been set (see
+ * {@link #allowableValues(AllowableValue...)})
+ * and the "Value" of the {@link DescribedValue} object is not
+ * the "Value" of one of those Allowable Values, an Exception will be
thrown.
+ * If the Allowable Values have been set using the
+ * {@link #allowableValues(AllowableValue...)} method, the default
value
+ * should be set providing the {@link AllowableValue} to this method.
+ *
+ * @param describedValue default value holder
+ * @return the builder
+ */
+public Builder defaultDescribedValue(final DescribedValue
describedValue) {
Review Comment:
I definitely think it's fine to require `.defaultValue((String) null)`. But
I'm not sure this is ever needed, since `null` is always the default unless
otherwise specified.
--
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-12412) ConsumeAzureEventHub should support Blob checkpoint store access via proxy
[ https://issues.apache.org/jira/browse/NIFI-12412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Turcsanyi updated NIFI-12412: --- Status: Patch Available (was: Open) > ConsumeAzureEventHub should support Blob checkpoint store access via proxy > -- > > Key: NIFI-12412 > URL: https://issues.apache.org/jira/browse/NIFI-12412 > Project: Apache NiFi > Issue Type: Bug >Reporter: Peter Turcsanyi >Assignee: Peter Turcsanyi >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > NIFI-6240 introduced proxy support for AzureEventHub processors and applied > the proxy configuration for the Event Hubs API calls. ConsumeAzureEventHub > also needs access to Blob Storage for storing checkpoints. The proxy > configuration should be used for the Blob API calls too. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[PR] NIFI-12412 Added proxy support for Blob checkpoint store in ConsumeAz… [nifi]
turcsanyip opened a new pull request, #8107: URL: https://github.com/apache/nifi/pull/8107 …ureEventHub # Summary [NIFI-12412](https://issues.apache.org/jira/browse/NIFI-12412) # 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] [Created] (NIFI-12456) Improve leniency of JSON readers and flexibility of JSON Writer
Mark Payne created NIFI-12456:
-
Summary: Improve leniency of JSON readers and flexibility of JSON
Writer
Key: NIFI-12456
URL: https://issues.apache.org/jira/browse/NIFI-12456
Project: Apache NiFi
Issue Type: Improvement
Components: Extensions
Reporter: Mark Payne
Currently, we adhere to the JSON specification fairly strictly, with the
exception of allowing for "JSON Lines" / ndjson / ldjson.
However, the Jackson library allows for several {{Features}} that we do not
expose, which may be helpful for handling data that does not strictly adhere to
the schema, or where there are preferences in serialization.
For example, {{JsonParser.Feature}} allows for the ability to allow comments in
JSON (to include lines beginning with {{{}//{}}}, {{{}/*{}}}, and "YAML Style"
comments (#)). Additionally, it allows for single-quotes for field names or no
quoting at all. While these do not adhere to the specification, they are common
enough for the parser to support them, and we should do.
Similarly, on the serialization side, we have had requests to support writing
decimal values without use of scientific notation, which can be achieved by
enabling the {{WRITE_BIGDECIMAL_AS_PLAIN}} feature.
We should expose these options on the JsonTreeReader and the JSON Writer. I
don't know of any downside to enabling the leniency / non-standard options, so
it probably makes sense to simply enable them all by default. Though there is
argument for introducing a new "Parsing Leniency" option that allows the user
to disable these features.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-12442) Adding support for RocksDB
[ https://issues.apache.org/jira/browse/NIFI-12442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17792522#comment-17792522 ] Giovanni commented on NIFI-12442: - Thanks for your considerations. Surely the advantage is the speed of calculation. A data flow possibly enrich data with half a million checks on 30 seconds with 2 clustered nodes (in my private experience, with my local clustered components). It's way efficient than other solutions. Obviously is up to the user to choose which one solution fits better for its purpose. At FS space cost and possibly RAM (depending of which RocksOptions the user choose), it could delivery a fast output. I understand the problematic relative to the maintainability and compatibility could be a problem. As you said, it's probably a better solution to create an external library, that receive constant updates, that a possible RocksDb chooser user could use. Thank you, at this point I think that this Ticket could be closed. > Adding support for RocksDB > -- > > Key: NIFI-12442 > URL: https://issues.apache.org/jira/browse/NIFI-12442 > Project: Apache NiFi > Issue Type: Improvement >Affects Versions: 1.23.2 >Reporter: Giovanni >Priority: Minor > Original Estimate: 336h > Remaining Estimate: 336h > > I would like to suggest the creation of 3 new components: > The first one is a service, which opens an existing RocksDb or, eventually, > using RocksOptions, create it from scratch. It will manage all the open > options (classic, read/write, only read, secondary). > The second one, is a RocksDbReader, that uses the service to communicate with > the RocksDb in order to retrieve informations through a lookup. It can save > the searched content inside an attribute or inside the flowFile content. It > will be capable of using both APIs, such as simple "db.get" and via > RocksIterator. > The last one, is a RocksDbWriter, that uses the same service as the reader, > but can write values inside the RocksDb, both from flowFile attribute or > flowFile content, using properties to determine the key to use. > > Feel free to express your opinions, if you think this will be useful or > useless. -- This message was sent by Atlassian Jira (v8.20.10#820010)
