[GitHub] [nifi] ottobackwards commented on pull request #6188: NIFI-10207: ensure allowableValues matches SUPPORTED_STATE in Process…
ottobackwards commented on PR #6188:
URL: https://github.com/apache/nifi/pull/6188#issuecomment-1179433421
verified after build
```json
"ProcessorRunStatusEntity" : {
"type" : "object",
"properties" : {
"revision" : {
"description" : "The revision for this request/response. The
revision is required for any mutable flow requests and is included in all
responses.",
"$ref" : "#/definitions/RevisionDTO"
},
"state" : {
"type" : "string",
"description" : "The run status of the Processor.",
"enum" : [ "RUNNING", "STOPPED", "DISABLED", "RUN_ONCE" ]
},
"disconnectedNodeAcknowledged" : {
"type" : "boolean",
"description" : "Acknowledges that this node is disconnected to
allow for mutable requests to proceed."
}
},
"xml" : {
"name" : "entity"
}
}
```
--
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
[GitHub] [nifi] ottobackwards opened a new pull request, #6188: NIFI-10207: ensure allowableValues matches SUPPORTED_STATE in Process…
ottobackwards opened a new pull request, #6188: URL: https://github.com/apache/nifi/pull/6188 …orRunStatusEntity # Summary [NIFI-10207](https://issues.apache.org/jira/browse/NIFI-10207) # 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 8 - [ ] JDK 11 - [ ] JDK 17 ### 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-10206) HandleHttpResponse always returns HTTP 404
[
https://issues.apache.org/jira/browse/NIFI-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann updated NIFI-10206:
Fix Version/s: 1.17.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> HandleHttpResponse always returns HTTP 404
> --
>
> Key: NIFI-10206
> URL: https://issues.apache.org/jira/browse/NIFI-10206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Fix For: 1.17.0
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> NIFI-3869 deleted {{response.flushBuffer()}} before calling
> {{AsyncContext.complete()}} but it seems to be necessary when Jetty's Handler
> is used (as in HandleHttpRequest/Response). Otherwise HTTP 404 is returned
> for all requests.
> Restoring the original logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (NIFI-10206) HandleHttpResponse always returns HTTP 404
[
https://issues.apache.org/jira/browse/NIFI-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564466#comment-17564466
]
ASF subversion and git services commented on NIFI-10206:
Commit 1685204cc1030b2228725eb4ba157539634d5149 in nifi's branch
refs/heads/main from Peter Turcsanyi
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1685204cc1 ]
NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoid HTTP 404
This closes #6186
Signed-off-by: David Handermann
> HandleHttpResponse always returns HTTP 404
> --
>
> Key: NIFI-10206
> URL: https://issues.apache.org/jira/browse/NIFI-10206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 40m
> Remaining Estimate: 0h
>
> NIFI-3869 deleted {{response.flushBuffer()}} before calling
> {{AsyncContext.complete()}} but it seems to be necessary when Jetty's Handler
> is used (as in HandleHttpRequest/Response). Otherwise HTTP 404 is returned
> for all requests.
> Restoring the original logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #6186: NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoi…
exceptionfactory closed pull request #6186: NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoi… URL: https://github.com/apache/nifi/pull/6186 -- 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
[GitHub] [nifi] exceptionfactory commented on pull request #6186: NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoi…
exceptionfactory commented on PR #6186: URL: https://github.com/apache/nifi/pull/6186#issuecomment-1179366857 Thanks for flagging this issue @turcsanyip! I noticed issues due to `flushBuffer()` during initial work on implementing HTTP/2 support. I will evaluate the changes and follow up soon. -- 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-10204) ListS3 with AWSCredentialsProviderControllerService cause invalid or malformed Token
[ https://issues.apache.org/jira/browse/NIFI-10204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564457#comment-17564457 ] Peter Turcsanyi commented on NIFI-10204: [~vadidde] I could not replicate the issue because it properly works for me. * could you please share the region where your bucket resides? * could you please check the configuration of the controller service looking for extra or missing characters (spaces, new lines, etc) > ListS3 with AWSCredentialsProviderControllerService cause invalid or > malformed Token > > > Key: NIFI-10204 > URL: https://issues.apache.org/jira/browse/NIFI-10204 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.15.2 >Reporter: davide >Priority: Major > Attachments: Screenshot 2022-07-08 at 12.48.29.png, Screenshot > 2022-07-08 at 12.49.59.png > > > I set ListS3 (see listS3 image) then provided an assume role with an external > id and role to access on another aws account in a > AWSCredentialsProviderControllerService. > Then i get this error: > ListS3[id=995de262----f0131a31] Failed to list contents of > bucket due to The provided token is malformed or otherwise invalid. (Service: > Amazon S3; Status Code: 400; Error Code: InvalidToken; Request ID: > E4Wx5G6; S3 Extended Request ID: CvR37+xxx; Proxy: null): > com.amazonaws.services.s3.model.AmazonS3Exception: The provided token is > malformed or otherwise invalid. (Service: Amazon S3; Status Code: 400; Error > Code: InvalidToken; Request ID: xx; S3 Extended Request ID: > CvxxGtArq7ak=; Proxy: null), S3 Extended Request ID: CvR37+dbdxxk= > From the nifi nodes with the aws cli listing on that bucket does it works. > Does anyone knows how to debug? or to solve? > I search across internet but i do not found anything like my problem. > thank you -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10207) ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue
[ https://issues.apache.org/jira/browse/NIFI-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler updated NIFI-10207: --- Description: A new run status of RUN_ONCE was added to the system in NIFI-8188. The ApiModelValue was not set however, so OpenApi/Swagger generations do not have support for RUN_ONCE as an allowable value, and get errors. see: https://github.com/Chaffelson/nipyapi/issues/309 > ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue > --- > > Key: NIFI-10207 > URL: https://issues.apache.org/jira/browse/NIFI-10207 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.14.0 >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > > A new run status of RUN_ONCE was added to the system in NIFI-8188. > The ApiModelValue was not set however, so OpenApi/Swagger generations do not > have support for RUN_ONCE as an allowable value, and get errors. > see: https://github.com/Chaffelson/nipyapi/issues/309 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10207) ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue
[ https://issues.apache.org/jira/browse/NIFI-10207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Otto Fowler reassigned NIFI-10207: -- Assignee: Otto Fowler > ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue > --- > > Key: NIFI-10207 > URL: https://issues.apache.org/jira/browse/NIFI-10207 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.14.0 >Reporter: Otto Fowler >Assignee: Otto Fowler >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10207) ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue
Otto Fowler created NIFI-10207: -- Summary: ProcessorRunStatusEntity does not declare RUN_ONCE in ApiModelValue Key: NIFI-10207 URL: https://issues.apache.org/jira/browse/NIFI-10207 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.14.0 Reporter: Otto Fowler -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] ottobackwards commented on pull request #6186: NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoi…
ottobackwards commented on PR #6186: URL: https://github.com/apache/nifi/pull/6186#issuecomment-1179334072 Looks good to me +1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@nifi.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564443#comment-17564443 ] Mark Payne commented on NIFI-10203: --- For clarification about what this affects: I was able to confirm that while the same UUID gets assigned to the clones, and this does cause problems for the data lineage, the processing of all clones appears to behave as expected otherwise. So this will cause confusion with data provenance and will make the logs confusing. However, it does not result in the FlowFiles getting mixed attributes otherwise, or referencing the wrong content, or prematurely removing content, or anything like that. Additionally, the FlowFile Repository refers to the FlowFiles via the one-up "ID" field, not the UUID field, so we don't run into additional issues after a restart. Will mark this as a Blocker priority, since it wouldn't make sense to release without getting this fixed first. > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.17.0 > > Attachments: Snipaste_2022-07-08_18-23-12.png > > Time Spent: 10m > Remaining Estimate: 0h > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564437#comment-17564437 ] Mark Payne commented on NIFI-10203: --- Thanks for reporting [~super_dachuan] . I submitted a pull request to address this. > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.17.0 > > Attachments: Snipaste_2022-07-08_18-23-12.png > > Time Spent: 10m > Remaining Estimate: 0h > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10203: -- Fix Version/s: 1.17.0 Status: Patch Available (was: Open) > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.3, 1.16.2, 1.16.1, 1.16.0 >Reporter: super dachuan >Priority: Blocker > Fix For: 1.17.0 > > Attachments: Snipaste_2022-07-08_18-23-12.png > > Time Spent: 10m > Remaining Estimate: 0h > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne reassigned NIFI-10203: - Assignee: Mark Payne > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Assignee: Mark Payne >Priority: Blocker > Fix For: 1.17.0 > > Attachments: Snipaste_2022-07-08_18-23-12.png > > Time Spent: 10m > Remaining Estimate: 0h > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] markap14 opened a new pull request, #6187: NIFI-10203: Fixed bug in which same FlowFile Builder was used repeate…
markap14 opened a new pull request, #6187: URL: https://github.com/apache/nifi/pull/6187 …dly for multiple FlowFiles; this caused mingling of their attributes when a FlowFile is routed to a relationship that has more than 1 destination (i.e., many connections with the same Relationship) # 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 8 - [ ] JDK 11 - [ ] JDK 17 ### 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-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Payne updated NIFI-10203: -- Priority: Blocker (was: Critical) > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Priority: Blocker > Attachments: Snipaste_2022-07-08_18-23-12.png > > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10206) HandleHttpResponse always returns HTTP 404
[
https://issues.apache.org/jira/browse/NIFI-10206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Turcsanyi updated NIFI-10206:
---
Status: Patch Available (was: In Progress)
> HandleHttpResponse always returns HTTP 404
> --
>
> Key: NIFI-10206
> URL: https://issues.apache.org/jira/browse/NIFI-10206
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Reporter: Peter Turcsanyi
>Assignee: Peter Turcsanyi
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> NIFI-3869 deleted {{response.flushBuffer()}} before calling
> {{AsyncContext.complete()}} but it seems to be necessary when Jetty's Handler
> is used (as in HandleHttpRequest/Response). Otherwise HTTP 404 is returned
> for all requests.
> Restoring the original logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] turcsanyip opened a new pull request, #6186: NIFI-10206: Restored flushBuffer() call in HandleHttpResponse to avoi…
turcsanyip opened a new pull request, #6186: URL: https://github.com/apache/nifi/pull/6186 …d HTTP 404 # Summary https://issues.apache.org/jira/browse/NIFI-10206 # 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 8 - [ ] JDK 11 - [ ] JDK 17 ### 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-10206) HandleHttpResponse always returns HTTP 404
Peter Turcsanyi created NIFI-10206:
--
Summary: HandleHttpResponse always returns HTTP 404
Key: NIFI-10206
URL: https://issues.apache.org/jira/browse/NIFI-10206
Project: Apache NiFi
Issue Type: Bug
Components: Extensions
Reporter: Peter Turcsanyi
Assignee: Peter Turcsanyi
NIFI-3869 deleted {{response.flushBuffer()}} before calling
{{AsyncContext.complete()}} but it seems to be necessary when Jetty's Handler
is used (as in HandleHttpRequest/Response). Otherwise HTTP 404 is returned for
all requests.
Restoring the original logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi-minifi-cpp] lordgamez opened a new pull request, #1366: MINIFICPP-1880 Address documentation issues of daemonset deployment
lordgamez opened a new pull request, #1366: URL: https://github.com/apache/nifi-minifi-cpp/pull/1366 https://issues.apache.org/jira/browse/MINIFICPP-1880 --- Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- 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-1880) Address issues of MiNiFi k8s daemonset example
Gábor Gyimesi created MINIFICPP-1880: Summary: Address issues of MiNiFi k8s daemonset example Key: MINIFICPP-1880 URL: https://issues.apache.org/jira/browse/MINIFICPP-1880 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Gábor Gyimesi Log volume is missing in the example. Also add examples for creating cluster read permissions for MiNiFi pod. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MINIFICPP-1880) Address issues of MiNiFi k8s daemonset example
[ https://issues.apache.org/jira/browse/MINIFICPP-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi reassigned MINIFICPP-1880: Assignee: Gábor Gyimesi > Address issues of MiNiFi k8s daemonset example > -- > > Key: MINIFICPP-1880 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1880 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Gábor Gyimesi >Assignee: Gábor Gyimesi >Priority: Minor > > Log volume is missing in the example. Also add examples for creating cluster > read permissions for MiNiFi pod. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10205) Process Group variable added during NIFI upgrade
naveen kumar saharan created NIFI-10205: --- Summary: Process Group variable added during NIFI upgrade Key: NIFI-10205 URL: https://issues.apache.org/jira/browse/NIFI-10205 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.16.3 Environment: PROD Reporter: naveen kumar saharan Attachments: image-2022-07-08-19-56-32-132.png, image-2022-07-08-20-04-35-585.png We are upgrading 1.12.1 to 1.16.3, after upgrade we are seeing weird behaviour # Random variable is getting added to PG # Local changes because of point 1 and also Local changes because of BackPressure 1Gb config adding to PG # Revert for local changes because of point 1,2 not happening. We have to deploy the flow after the commit local changes. Which is causing a dummy version in registry. !image-2022-07-08-19-56-32-132.png! !image-2022-07-08-20-04-35-585.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi-minifi-cpp] lordgamez commented on a diff in pull request #1364: MINIFICPP-1878 Enable Ninja build in Windows builds
lordgamez commented on code in PR #1364: URL: https://github.com/apache/nifi-minifi-cpp/pull/1364#discussion_r916872367 ## cmake/BundledCivetWeb.cmake: ## @@ -64,12 +61,11 @@ function(use_bundled_civetweb SOURCE_DIR BINARY_DIR) # Build project ExternalProject_Add( civetweb-external -URL "https://github.com/civetweb/civetweb/archive/v1.12.tar.gz; -URL_HASH "SHA256=8cab1e2ad8fb3e2e81fed0b2321a5afbd7269a644c44ed4c3607e0a212c6d9e1" +GIT_REPOSITORY "https://github.com/civetweb/civetweb.git; +GIT_TAG "4447b6501d5c568b4c6c0940eac801ec690b2250" # commit containing fix for MSVC issue https://github.com/civetweb/civetweb/issues/1024 Review Comment: Replaced with FetchContent in d578834c8d66fac12537468c21b8887283a38045 ## win_build_vs.bat: ## @@ -73,12 +73,17 @@ for %%x in (%*) do ( if [%%~x] EQU [/NONFREEUCRT] set "redist=-DMSI_REDISTRIBUTE_UCRT_NONASL=ON" if [%%~x] EQU [/L] set build_linter=ON if [%%~x] EQU [/RO] set real_odbc=ON +if [%%~x] EQU [/NJ] set generator="Ninja" ) mkdir %builddir% pushd %builddir%\ -cmake -G %generator% -A %build_platform% -DINSTALLER_MERGE_MODULES=%installer_merge_modules% -DTEST_CUSTOM_WEL_PROVIDER=%test_custom_wel_provider% -DENABLE_SQL=%build_SQL% -DUSE_REAL_ODBC_TEST_DRIVER=%real_odbc% -DCMAKE_BUILD_TYPE_INIT=%cmake_build_type% -DCMAKE_BUILD_TYPE=%cmake_build_type% -DWIN32=WIN32 -DENABLE_LIBRDKAFKA=%build_kafka% -DENABLE_JNI=%build_jni% -DOPENSSL_OFF=OFF -DENABLE_COAP=%build_coap% -DENABLE_AWS=%build_AWS% -DENABLE_PDH=%build_PDH% -DENABLE_AZURE=%build_azure% -DENABLE_SFTP=%build_SFTP% -DENABLE_SPLUNK=%build_SPLUNK% -DENABLE_GCP=%build_GCP% -DENABLE_NANOFI=%build_nanofi% -DENABLE_OPENCV=%build_opencv% -DENABLE_PROMETHEUS=%build_prometheus% -DENABLE_ELASTICSEARCH=%build_ELASTIC% -DUSE_SHARED_LIBS=OFF -DDISABLE_CONTROLLER=ON -DBUILD_ROCKSDB=ON -DFORCE_WINDOWS=ON -DUSE_SYSTEM_UUID=OFF -DDISABLE_LIBARCHIVE=OFF -DENABLE_SCRIPTING=OFF -DEXCLUDE_BOOST=ON -DENABLE_WEL=ON -DFAIL_ON_WARNINGS=OFF -DSKIP_TESTS=%skiptests% %strict_gsl_checks% %redist% -DENABLE_LINTER=% build_linter% "%scriptdir%" && msbuild /m nifi-minifi-cpp.sln /property:Configuration=%cmake_build_type% /property:Platform=%build_platform% && copy bin\%cmake_build_type%\minifi.exe main\ +if [%generator%] EQU ["Ninja"] ( +cmake -G %generator% -DINSTALLER_MERGE_MODULES=%installer_merge_modules% -DTEST_CUSTOM_WEL_PROVIDER=%test_custom_wel_provider% -DENABLE_SQL=%build_SQL% -DUSE_REAL_ODBC_TEST_DRIVER=%real_odbc% -DCMAKE_BUILD_TYPE_INIT=%cmake_build_type% -DCMAKE_BUILD_TYPE=%cmake_build_type% -DWIN32=WIN32 -DENABLE_LIBRDKAFKA=%build_kafka% -DENABLE_JNI=%build_jni% -DOPENSSL_OFF=OFF -DENABLE_COAP=%build_coap% -DENABLE_AWS=%build_AWS% -DENABLE_PDH=%build_PDH% -DENABLE_AZURE=%build_azure% -DENABLE_SFTP=%build_SFTP% -DENABLE_SPLUNK=%build_SPLUNK% -DENABLE_GCP=%build_GCP% -DENABLE_NANOFI=%build_nanofi% -DENABLE_OPENCV=%build_opencv% -DENABLE_PROMETHEUS=%build_prometheus% -DENABLE_ELASTICSEARCH=%build_ELASTIC% -DUSE_SHARED_LIBS=OFF -DDISABLE_CONTROLLER=ON -DBUILD_ROCKSDB=ON -DFORCE_WINDOWS=ON -DUSE_SYSTEM_UUID=OFF -DDISABLE_LIBARCHIVE=OFF -DENABLE_SCRIPTING=OFF -DEXCLUDE_BOOST=ON -DENABLE_WEL=ON -DFAIL_ON_WARNINGS=OFF -DSKIP_TESTS=%skiptests% %strict_gsl_checks% %redist% -DENABLE_LINTER=%build_linter% "% scriptdir%" && ninja +) else ( +cmake -G %generator% -A %build_platform% -DINSTALLER_MERGE_MODULES=%installer_merge_modules% -DTEST_CUSTOM_WEL_PROVIDER=%test_custom_wel_provider% -DENABLE_SQL=%build_SQL% -DUSE_REAL_ODBC_TEST_DRIVER=%real_odbc% -DCMAKE_BUILD_TYPE_INIT=%cmake_build_type% -DCMAKE_BUILD_TYPE=%cmake_build_type% -DWIN32=WIN32 -DENABLE_LIBRDKAFKA=%build_kafka% -DENABLE_JNI=%build_jni% -DOPENSSL_OFF=OFF -DENABLE_COAP=%build_coap% -DENABLE_AWS=%build_AWS% -DENABLE_PDH=%build_PDH% -DENABLE_AZURE=%build_azure% -DENABLE_SFTP=%build_SFTP% -DENABLE_SPLUNK=%build_SPLUNK% -DENABLE_GCP=%build_GCP% -DENABLE_NANOFI=%build_nanofi% -DENABLE_OPENCV=%build_opencv% -DENABLE_PROMETHEUS=%build_prometheus% -DENABLE_ELASTICSEARCH=%build_ELASTIC% -DUSE_SHARED_LIBS=OFF -DDISABLE_CONTROLLER=ON -DBUILD_ROCKSDB=ON -DFORCE_WINDOWS=ON -DUSE_SYSTEM_UUID=OFF -DDISABLE_LIBARCHIVE=OFF -DENABLE_SCRIPTING=OFF -DEXCLUDE_BOOST=ON -DENABLE_WEL=ON -DFAIL_ON_WARNINGS=OFF -DSKIP_TESTS=%skiptests% %strict_gsl_checks% %redist% -DENABLE_LINT ER=%build_linter% "%scriptdir%" && msbuild /m nifi-minifi-cpp.sln /property:Configuration=%cmake_build_type% /property:Platform=%build_platform% && copy bin\%cmake_build_type%\minifi.exe main\ +) Review Comment: Good point, thanks, updated in d578834c8d66fac12537468c21b8887283a38045 -- 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:
[GitHub] [nifi-minifi-cpp] lordgamez opened a new pull request, #1365: MINIFICPP-1879 Fix Prometheus switch in bootstrap.sh
lordgamez opened a new pull request, #1365: URL: https://github.com/apache/nifi-minifi-cpp/pull/1365 The issue probably slipped through when merging Prometheus functionality while changing `add_option` function in bootstrap.sh https://issues.apache.org/jira/browse/MINIFICPP-1879 Thank you for submitting a contribution to Apache NiFi - MiNiFi C++. In order to streamline the review of the contribution we ask you to ensure the following steps have been taken: ### For all changes: - [ ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message? - [ ] Does your PR title start with MINIFICPP- where is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character. - [ ] Has your PR been rebased against the latest commit within the target branch (typically main)? - [ ] Is your initial contribution a single, squashed commit? ### For code changes: - [ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under [ASF 2.0](http://www.apache.org/legal/resolved.html#category-a)? - [ ] If applicable, have you updated the LICENSE file? - [ ] If applicable, have you updated the NOTICE file? ### For documentation related changes: - [ ] Have you ensured that format looks appropriate for the output in which it is rendered? ### Note: Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible. -- 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] [Assigned] (MINIFICPP-1879) Prometheus option does not work in bootstrap.sh
[ https://issues.apache.org/jira/browse/MINIFICPP-1879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gábor Gyimesi reassigned MINIFICPP-1879: Assignee: Gábor Gyimesi > Prometheus option does not work in bootstrap.sh > --- > > Key: MINIFICPP-1879 > URL: https://issues.apache.org/jira/browse/MINIFICPP-1879 > Project: Apache NiFi MiNiFi C++ > Issue Type: Bug >Reporter: Gábor Gyimesi >Assignee: Gábor Gyimesi >Priority: Trivial > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINIFICPP-1879) Prometheus option does not work in bootstrap.sh
Gábor Gyimesi created MINIFICPP-1879: Summary: Prometheus option does not work in bootstrap.sh Key: MINIFICPP-1879 URL: https://issues.apache.org/jira/browse/MINIFICPP-1879 Project: Apache NiFi MiNiFi C++ Issue Type: Bug Reporter: Gábor Gyimesi -- This message was sent by Atlassian Jira (v8.20.10#820010)
[GitHub] [nifi] exceptionfactory closed pull request #6184: Bump jetty-server from 9.4.48.v20220622 to 10.0.10
exceptionfactory closed pull request #6184: Bump jetty-server from 9.4.48.v20220622 to 10.0.10 URL: https://github.com/apache/nifi/pull/6184 -- 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
[GitHub] [nifi] dependabot[bot] commented on pull request #6184: Bump jetty-server from 9.4.48.v20220622 to 10.0.10
dependabot[bot] commented on PR #6184: URL: https://github.com/apache/nifi/pull/6184#issuecomment-1179024492 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`. If you change your mind, just re-open this PR and I'll resolve any conflicts on it. -- 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-10199) PublishKafkaRecord should not flood the logs when a batch times out
[
https://issues.apache.org/jira/browse/NIFI-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Urban updated NIFI-10199:
Status: Patch Available (was: In Progress)
> PublishKafkaRecord should not flood the logs when a batch times out
> ---
>
> Key: NIFI-10199
> URL: https://issues.apache.org/jira/browse/NIFI-10199
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Urban
>Assignee: Daniel Urban
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently, PublishKafkaRecord reports errors on the record level. This means
> that when an error occurs on the batch level, the same error is reported for
> each record of said batch.
> For example, in case of a delivery timeout, a transactional Kafka producer
> logs a message like this:
> {code:java}
> 2022-06-29 13:16:20,913 INFO
> org.apache.kafka.clients.producer.internals.TransactionManager: [Producer
> clientId=producer-XYZ, transactionalId=XYZ] Transiting to abortable error
> state due to org.apache.kafka.common.errors.TimeoutException: Expiring 63
> record(s) for TOPIC-01:302002 ms has passed since batch creation {code}
> Then, following this, we get N lines, where N is the number of records in the
> batch. Also note that the TimeoutException is printed twice in this message.
> {code:java}
> 2022-06-29 13:16:20,913 ERROR
> org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_2_6:
> PublishKafkaRecord_2_6[id=91ba351d-96ad-1d0d-934c-cfd07e0bacd5] Failed to
> send
> StandardFlowFileRecord[uuid=349b4d38-451d-4e62-8ea9-636f7c666fc1,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1656453186665-7724448,
> container=default, section=416], offset=0,
> length=132021252],offset=0,name=NAME,size=132021252] to Kafka:
> org.apache.kafka.common.errors.TimeoutException: Expiring 63 record(s) for
> PROD_trn_lba_icode_vld_v2-38:302002 ms has passed since batch creation
> org.apache.kafka.common.errors.TimeoutException: Expiring 63 record(s) for
> PROD_trn_lba_icode_vld_v2-38:302002 ms has passed since batch creation{code}
> Experienced this with PublishKafkaRecord_2_6, but other versions might be
> affected as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[GitHub] [nifi] urbandan opened a new pull request, #6185: NIFI-10199: PublishKafka InFlightMessageTracker should not log batch …
urbandan opened a new pull request, #6185: URL: https://github.com/apache/nifi/pull/6185 …level errors on each record Currently, when a batch level error occurs (e.g. delivery timeout), the same error is logged for each record of the batch, needlessly flooding the logs. InFlightMessageTracker now only logs the first exception, or any later exceptions not equal to the first exception. # 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 8 - [ ] JDK 11 - [ ] JDK 17 ### 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-10204) ListS3 with AWSCredentialsProviderControllerService cause invalid or malformed Token
davide created NIFI-10204: - Summary: ListS3 with AWSCredentialsProviderControllerService cause invalid or malformed Token Key: NIFI-10204 URL: https://issues.apache.org/jira/browse/NIFI-10204 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.15.2 Reporter: davide Attachments: Screenshot 2022-07-08 at 12.48.29.png, Screenshot 2022-07-08 at 12.49.59.png I set ListS3 (see listS3 image) then provided an assume role with an external id and role to access on another aws account in a AWSCredentialsProviderControllerService. Then i get this error: ListS3[id=995de262----f0131a31] Failed to list contents of bucket due to The provided token is malformed or otherwise invalid. (Service: Amazon S3; Status Code: 400; Error Code: InvalidToken; Request ID: E4Wx5G6; S3 Extended Request ID: CvR37+xxx; Proxy: null): com.amazonaws.services.s3.model.AmazonS3Exception: The provided token is malformed or otherwise invalid. (Service: Amazon S3; Status Code: 400; Error Code: InvalidToken; Request ID: xx; S3 Extended Request ID: CvxxGtArq7ak=; Proxy: null), S3 Extended Request ID: CvR37+dbdxxk= >From the nifi nodes with the aws cli listing on that bucket does it works. Does anyone knows how to debug? or to solve? I search across internet but i do not found anything like my problem. thank you -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203 ] super dachuan deleted comment on NIFI-10203: -- was (Author: super_dachuan): Previous issue: https://issues.apache.org/jira/browse/NIFI-10064 caused by this bug > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Priority: Critical > Attachments: Snipaste_2022-07-08_18-23-12.png > > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17564221#comment-17564221 ] super dachuan commented on NIFI-10203: -- Previous issue: https://issues.apache.org/jira/browse/NIFI-10064 caused by this bug > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Priority: Critical > Attachments: Snipaste_2022-07-08_18-23-12.png > > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] super dachuan updated NIFI-10203: - External issue URL: (was: https://issues.apache.org/jira/browse/NIFI-10064) > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Priority: Critical > Attachments: Snipaste_2022-07-08_18-23-12.png > > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
[ https://issues.apache.org/jira/browse/NIFI-10203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] super dachuan updated NIFI-10203: - External issue URL: https://issues.apache.org/jira/browse/NIFI-10064 > Multi-connection relationship clone flowfile with same uuid > --- > > Key: NIFI-10203 > URL: https://issues.apache.org/jira/browse/NIFI-10203 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework >Affects Versions: 1.16.0, 1.16.1, 1.16.2, 1.16.3 >Reporter: super dachuan >Priority: Critical > Attachments: Snipaste_2022-07-08_18-23-12.png > > > A relationship could be generated many connections as we need , likes the > picture. Framework clone the orginal flowfile and transfer to all connection. > However, these flowfiles have same uuid, we expected every flowfile has > unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10203) Multi-connection relationship clone flowfile with same uuid
super dachuan created NIFI-10203: Summary: Multi-connection relationship clone flowfile with same uuid Key: NIFI-10203 URL: https://issues.apache.org/jira/browse/NIFI-10203 Project: Apache NiFi Issue Type: Bug Components: Core Framework Affects Versions: 1.16.3, 1.16.2, 1.16.1, 1.16.0 Reporter: super dachuan Attachments: Snipaste_2022-07-08_18-23-12.png A relationship could be generated many connections as we need , likes the picture. Framework clone the orginal flowfile and transfer to all connection. However, these flowfiles have same uuid, we expected every flowfile has unique uuid like the older versions. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (NIFI-10199) PublishKafkaRecord should not flood the logs when a batch times out
[
https://issues.apache.org/jira/browse/NIFI-10199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Urban reassigned NIFI-10199:
---
Assignee: Daniel Urban
> PublishKafkaRecord should not flood the logs when a batch times out
> ---
>
> Key: NIFI-10199
> URL: https://issues.apache.org/jira/browse/NIFI-10199
> Project: Apache NiFi
> Issue Type: Improvement
>Reporter: Daniel Urban
>Assignee: Daniel Urban
>Priority: Major
>
> Currently, PublishKafkaRecord reports errors on the record level. This means
> that when an error occurs on the batch level, the same error is reported for
> each record of said batch.
> For example, in case of a delivery timeout, a transactional Kafka producer
> logs a message like this:
> {code:java}
> 2022-06-29 13:16:20,913 INFO
> org.apache.kafka.clients.producer.internals.TransactionManager: [Producer
> clientId=producer-XYZ, transactionalId=XYZ] Transiting to abortable error
> state due to org.apache.kafka.common.errors.TimeoutException: Expiring 63
> record(s) for TOPIC-01:302002 ms has passed since batch creation {code}
> Then, following this, we get N lines, where N is the number of records in the
> batch. Also note that the TimeoutException is printed twice in this message.
> {code:java}
> 2022-06-29 13:16:20,913 ERROR
> org.apache.nifi.processors.kafka.pubsub.PublishKafkaRecord_2_6:
> PublishKafkaRecord_2_6[id=91ba351d-96ad-1d0d-934c-cfd07e0bacd5] Failed to
> send
> StandardFlowFileRecord[uuid=349b4d38-451d-4e62-8ea9-636f7c666fc1,claim=StandardContentClaim
> [resourceClaim=StandardResourceClaim[id=1656453186665-7724448,
> container=default, section=416], offset=0,
> length=132021252],offset=0,name=NAME,size=132021252] to Kafka:
> org.apache.kafka.common.errors.TimeoutException: Expiring 63 record(s) for
> PROD_trn_lba_icode_vld_v2-38:302002 ms has passed since batch creation
> org.apache.kafka.common.errors.TimeoutException: Expiring 63 record(s) for
> PROD_trn_lba_icode_vld_v2-38:302002 ms has passed since batch creation{code}
> Experienced this with PublishKafkaRecord_2_6, but other versions might be
> affected as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
