[jira] [Updated] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
[ https://issues.apache.org/jira/browse/NIFI-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11579: Priority: Major (was: Critical) > InvokeHttp is not working when setting Username and password as grant type > -- > > Key: NIFI-11579 > URL: https://issues.apache.org/jira/browse/NIFI-11579 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2023-05-22-15-49-35-231.png, > image-2023-05-22-15-51-44-000.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set basic authentication and username and password > in my controller service, it throws below error. > !image-2023-05-22-15-49-35-231.png! > > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 > access token request failed: java.io.UncheckedIOException: OAuth2 access > token request failed > - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized > token > 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': > was expecting (JSON String, Number, Array, Object or token 'null', 'true' or > 'false') > at [Source: > (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated > 513 chars]; line: 1, column: 81] > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > !image-2023-05-22-15-51-44-000.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11578) InvokeHttp is not working when setting client credentials as grant type
[ https://issues.apache.org/jira/browse/NIFI-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11578: Priority: Major (was: Critical) > InvokeHttp is not working when setting client credentials as grant type > --- > > Key: NIFI-11578 > URL: https://issues.apache.org/jira/browse/NIFI-11578 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2023-05-22-15-35-35-597.png, > image-2023-05-22-15-38-28-096.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set client credentials in my Invokehttp method, it > throws below error. > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400]: > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400 > > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > !image-2023-05-22-15-38-28-096.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-11578) InvokeHttp is not working when setting client credentials as grant type
[ https://issues.apache.org/jira/browse/NIFI-11578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17731504#comment-17731504 ] Vrinda Palod commented on NIFI-11578: - Hi Team any update on this ? > InvokeHttp is not working when setting client credentials as grant type > --- > > Key: NIFI-11578 > URL: https://issues.apache.org/jira/browse/NIFI-11578 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Critical > Attachments: image-2023-05-22-15-35-35-597.png, > image-2023-05-22-15-38-28-096.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set client credentials in my Invokehttp method, it > throws below error. > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400]: > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400 > > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > !image-2023-05-22-15-38-28-096.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
[ https://issues.apache.org/jira/browse/NIFI-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11579: Description: Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set basic authentication and username and password in my controller service, it throws below error. !image-2023-05-22-15-49-35-231.png! InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 access token request failed: java.io.UncheckedIOException: OAuth2 access token request failed - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated 513 chars]; line: 1, column: 81] Below is how I am setting up my controller service. There is no issue with endpoint url we are using. !image-2023-05-22-15-51-44-000.png! was: Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set basic authentication and username and password in my controller service, it throws below error. !image-2023-05-22-15-49-35-231.png! InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 access token request failed: java.io.UncheckedIOException: OAuth2 access token request failed - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated 513 chars]; line: 1, column: 81] Below is how I am setting up my controller service. There is no issue with endpoint url we are using. > InvokeHttp is not working when setting Username and password as grant type > -- > > Key: NIFI-11579 > URL: https://issues.apache.org/jira/browse/NIFI-11579 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Critical > Attachments: image-2023-05-22-15-49-35-231.png, > image-2023-05-22-15-51-44-000.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set basic authentication and username and password > in my controller service, it throws below error. > !image-2023-05-22-15-49-35-231.png! > > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 > access token request failed: java.io.UncheckedIOException: OAuth2 access > token request failed > - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized > token > 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': > was expecting (JSON String, Number, Array, Object or token 'null', 'true' or > 'false') > at [Source: > (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb
[jira] [Updated] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
[ https://issues.apache.org/jira/browse/NIFI-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11579: Attachment: image-2023-05-22-15-51-44-000.png > InvokeHttp is not working when setting Username and password as grant type > -- > > Key: NIFI-11579 > URL: https://issues.apache.org/jira/browse/NIFI-11579 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Critical > Attachments: image-2023-05-22-15-49-35-231.png, > image-2023-05-22-15-51-44-000.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set basic authentication and username and password > in my controller service, it throws below error. > !image-2023-05-22-15-49-35-231.png! > > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 > access token request failed: java.io.UncheckedIOException: OAuth2 access > token request failed > - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized > token > 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': > was expecting (JSON String, Number, Array, Object or token 'null', 'true' or > 'false') > at [Source: > (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated > 513 chars]; line: 1, column: 81] > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
[ https://issues.apache.org/jira/browse/NIFI-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11579: Description: Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set basic authentication and username and password in my controller service, it throws below error. !image-2023-05-22-15-49-35-231.png! InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 access token request failed: java.io.UncheckedIOException: OAuth2 access token request failed - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized token 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': was expecting (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated 513 chars]; line: 1, column: 81] Below is how I am setting up my controller service. There is no issue with endpoint url we are using. was: Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set client credentials in my Invokehttp method, it throws below error. InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400]: org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400 Below is how I am setting up my controller service. There is no issue with endpoint url we are using. !image-2023-05-22-15-38-28-096.png! > InvokeHttp is not working when setting Username and password as grant type > -- > > Key: NIFI-11579 > URL: https://issues.apache.org/jira/browse/NIFI-11579 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Critical > Attachments: image-2023-05-22-15-49-35-231.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set basic authentication and username and password > in my controller service, it throws below error. > !image-2023-05-22-15-49-35-231.png! > > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to java.io.UncheckedIOException: OAuth2 > access token request failed: java.io.UncheckedIOException: OAuth2 access > token request failed > - Caused by: com.fasterxml.jackson.core.JsonParseException: Unrecognized > token > 'eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9': > was expecting (JSON String, Number, Array, Object or token 'null', 'true' or > 'false') > at [Source: > (String)"eyJraWQiOiJlN2RmMGRmNS01ODcwLTQ0MjEtOTA2Mi1iZDkyZmVlYWI0MTMiLCJhbGciOiJQUzUxMiJ9.eyJzdWIiOiJhNzA1NjQ5IiwiYXVkIjoiTGRhcFByb3ZpZGVyIiwibmJmIjoxNjg0NzUwNTM5LCJpc3MiOiJMZGFwUHJvdmlkZXIiLCJwcmVmZXJyZWRfdXNlcm5hbWUiOiJhNzA1NjQ5IiwiZXhwIjoxNjg0NzkzNzM5LCJpYXQiOjE2ODQ3NTA1MzksImp0aSI6ImEwNjc3MjNjLWY5ZTgtNDg2Yi1iNjk5LWM3MThlM2JkYjI0ZSJ9.hnUxMPxCKNluxdLkPrlIy6JWkZAjEvbjWfDRxQjBSVXRyXNrcqgHyBb6Ruvca59xeWmEg1p4wuE5AENuzUEcwnuGX5vX-G0gx-4zY1WYpN7pp6JbXnKUxIXLqr4KMDyHAT0_0aVuNbgqJZ1MLOrfssh4jw_Trxol92N4kb0I4z"[truncated > 513 chars]; line: 1, column: 81] > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
[ https://issues.apache.org/jira/browse/NIFI-11579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-11579: Attachment: image-2023-05-22-15-49-35-231.png > InvokeHttp is not working when setting Username and password as grant type > -- > > Key: NIFI-11579 > URL: https://issues.apache.org/jira/browse/NIFI-11579 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.20.0, 1.21.0 >Reporter: Vrinda Palod >Priority: Critical > Attachments: image-2023-05-22-15-49-35-231.png > > > Hi Team, > I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider > controller service. When I set client credentials in my Invokehttp method, it > throws below error. > InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly > initialize Processor. If still scheduled to run, NiFi will attempt to > initialize and run the Processor again after the 'Administrative Yield > Duration' has elapsed. Failure is due to > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400]: > org.apache.nifi.processor.exception.ProcessException: OAuth2 access token > request failed [HTTP 400 > > > Below is how I am setting up my controller service. There is no issue with > endpoint url we are using. > !image-2023-05-22-15-38-28-096.png! > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11579) InvokeHttp is not working when setting Username and password as grant type
Vrinda Palod created NIFI-11579: --- Summary: InvokeHttp is not working when setting Username and password as grant type Key: NIFI-11579 URL: https://issues.apache.org/jira/browse/NIFI-11579 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.20.0, 1.21.0 Reporter: Vrinda Palod Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set client credentials in my Invokehttp method, it throws below error. InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400]: org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400 Below is how I am setting up my controller service. There is no issue with endpoint url we are using. !image-2023-05-22-15-38-28-096.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-11578) InvokeHttp is not working when setting client credentials as grant type
Vrinda Palod created NIFI-11578: --- Summary: InvokeHttp is not working when setting client credentials as grant type Key: NIFI-11578 URL: https://issues.apache.org/jira/browse/NIFI-11578 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.21.0, 1.20.0 Reporter: Vrinda Palod Attachments: image-2023-05-22-15-35-35-597.png, image-2023-05-22-15-38-28-096.png Hi Team, I am trying to run Invokrhttp using StandardOauth2AccessTokenProvider controller service. When I set client credentials in my Invokehttp method, it throws below error. InvokeHTTP[id=32a98900-0188-1000--88fdac58] Failed to properly initialize Processor. If still scheduled to run, NiFi will attempt to initialize and run the Processor again after the 'Administrative Yield Duration' has elapsed. Failure is due to org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400]: org.apache.nifi.processor.exception.ProcessException: OAuth2 access token request failed [HTTP 400 Below is how I am setting up my controller service. There is no issue with endpoint url we are using. !image-2023-05-22-15-38-28-096.png! -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (NIFI-10664) Could not read from StandardFlowFileRecord in nifi
[ https://issues.apache.org/jira/browse/NIFI-10664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633772#comment-17633772 ] Vrinda Palod commented on NIFI-10664: - can you please help with the fix or the resolution.? > Could not read from StandardFlowFileRecord in nifi > -- > > Key: NIFI-10664 > URL: https://issues.apache.org/jira/browse/NIFI-10664 > Project: Apache NiFi > Issue Type: Bug >Affects Versions: 1.16.3 >Reporter: Vrinda Palod >Priority: Critical > > Hi Team, > > We are continuously getting this error at random interval of time. We are not > able to figure out from which flow/Process group this error is coming. Need > help in moving further > > org.apache.nifi.processor.exception.FlowFileAccessException: Could not read > from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] > org.apache.nifi.processor.exception.FlowFileAccessException: Could not read > from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] at > org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:93) > at > org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:99) > at > org.apache.nifi.controller.repository.io.TaskTerminationInputStream.read(TaskTerminationInputStream.java:62) > at org.apache.nifi.stream.io.StreamUtils.copy(StreamUtils.java:35) at > org.apache.nifi.processors.standard.ExecuteStreamCommand$2run(ExecuteStreamCommand.java:634) > at java.base/java.lang.Thread.run(Thread.java:834) Caused by: > java.io.IOException: Stream is closed at > org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.checkClosed(DisableOnCloseInputStream.java:65) > at > org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.read(DisableOnCloseInputStream.java:48) > at > org.apache.nifi.stream.io.ByteCountingInputStream.read(ByteCountingInputStream.java:52) > at java.base/java.io.FilterInputStream.read(FilterInputStream.java:133) at > org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82) > ... 5 common frames omitted -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10665) NIFI Performance issue - ConvertExcelToCSVProcessor to handle more data
Vrinda Palod created NIFI-10665: --- Summary: NIFI Performance issue - ConvertExcelToCSVProcessor to handle more data Key: NIFI-10665 URL: https://issues.apache.org/jira/browse/NIFI-10665 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.16.3 Reporter: Vrinda Palod Hi Team, We are continuously getting this error at random interval of time. We are not able to figure out from which flow/Process group this error is coming. Need help in moving further org.apache.nifi.processor.exception.FlowFileAccessException: Could not read from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] org.apache.nifi.processor.exception.FlowFileAccessException: Could not read from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:93) at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:99) at org.apache.nifi.controller.repository.io.TaskTerminationInputStream.read(TaskTerminationInputStream.java:62) at org.apache.nifi.stream.io.StreamUtils.copy(StreamUtils.java:35) at org.apache.nifi.processors.standard.ExecuteStreamCommand$2run(ExecuteStreamCommand.java:634) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.io.IOException: Stream is closed at org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.checkClosed(DisableOnCloseInputStream.java:65) at org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.read(DisableOnCloseInputStream.java:48) at org.apache.nifi.stream.io.ByteCountingInputStream.read(ByteCountingInputStream.java:52) at java.base/java.io.FilterInputStream.read(FilterInputStream.java:133) at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82) ... 5 common frames omitted -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10664) Could not read from StandardFlowFileRecord in nifi
Vrinda Palod created NIFI-10664: --- Summary: Could not read from StandardFlowFileRecord in nifi Key: NIFI-10664 URL: https://issues.apache.org/jira/browse/NIFI-10664 Project: Apache NiFi Issue Type: Bug Affects Versions: 1.16.3 Reporter: Vrinda Palod Hi Team, We are continuously getting this error at random interval of time. We are not able to figure out from which flow/Process group this error is coming. Need help in moving further org.apache.nifi.processor.exception.FlowFileAccessException: Could not read from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] org.apache.nifi.processor.exception.FlowFileAccessException: Could not read from StandardFlowFileRecord[uuid=*,claim=,offset=0,name=*,size=0] at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:93) at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:99) at org.apache.nifi.controller.repository.io.TaskTerminationInputStream.read(TaskTerminationInputStream.java:62) at org.apache.nifi.stream.io.StreamUtils.copy(StreamUtils.java:35) at org.apache.nifi.processors.standard.ExecuteStreamCommand$2run(ExecuteStreamCommand.java:634) at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.io.IOException: Stream is closed at org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.checkClosed(DisableOnCloseInputStream.java:65) at org.apache.nifi.controller.repository.io.DisableOnCloseInputStream.read(DisableOnCloseInputStream.java:48) at org.apache.nifi.stream.io.ByteCountingInputStream.read(ByteCountingInputStream.java:52) at java.base/java.io.FilterInputStream.read(FilterInputStream.java:133) at org.apache.nifi.controller.repository.io.FlowFileAccessInputStream.read(FlowFileAccessInputStream.java:82) ... 5 common frames omitted -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10546) Commons HttpClient 3.1 has reached EOL. Need to upgrade it
[ https://issues.apache.org/jira/browse/NIFI-10546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-10546: Description: Please upgrade the Commons HttpClient 3.1 to latest version in below locations. |/nifidata/apps/nifi_binary/work/nar/extensions/nifi-hbase_1_1_2-client-service-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.1.jar| |/nifidata/apps/nifi_binary/work/nar/extensions/nifi-hive-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.0.1.jar| |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.1.jar| |/nifidata/apps/nifi_toolkit_binary/lib/commons-httpclient-3.1.jar| was: Please upgrade the OpenSAML 2.6 to latest version in below locations. |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/opensaml-2.6.6.jar| |/nifidata/apps/nifi_toolkit_binary/lib/opensaml-2.6.6.jar| > Commons HttpClient 3.1 has reached EOL. Need to upgrade it > --- > > Key: NIFI-10546 > URL: https://issues.apache.org/jira/browse/NIFI-10546 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework, Core UI >Affects Versions: 1.17.0, 1.16.3, 1.18.0 >Reporter: Vrinda Palod >Priority: Critical > > Please upgrade the Commons HttpClient 3.1 to latest version in below > locations. > > > |/nifidata/apps/nifi_binary/work/nar/extensions/nifi-hbase_1_1_2-client-service-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.1.jar| > |/nifidata/apps/nifi_binary/work/nar/extensions/nifi-hive-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.0.1.jar| > |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/commons-httpclient-3.1.jar| > |/nifidata/apps/nifi_toolkit_binary/lib/commons-httpclient-3.1.jar| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10546) Commons HttpClient 3.1 has reached EOL. Need to upgrade it
Vrinda Palod created NIFI-10546: --- Summary: Commons HttpClient 3.1 has reached EOL. Need to upgrade it Key: NIFI-10546 URL: https://issues.apache.org/jira/browse/NIFI-10546 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Core UI Affects Versions: 1.17.0, 1.16.3, 1.18.0 Reporter: Vrinda Palod Please upgrade the OpenSAML 2.6 to latest version in below locations. |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/opensaml-2.6.6.jar| |/nifidata/apps/nifi_toolkit_binary/lib/opensaml-2.6.6.jar| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10545) OpenSAML 2.6.6 has reached EOL. Need to upgrade it
Vrinda Palod created NIFI-10545: --- Summary: OpenSAML 2.6.6 has reached EOL. Need to upgrade it Key: NIFI-10545 URL: https://issues.apache.org/jira/browse/NIFI-10545 Project: Apache NiFi Issue Type: Improvement Components: Core Framework, Core UI Affects Versions: 1.16.3, 1.17.0, 1.18.0 Reporter: Vrinda Palod Please upgrade the OpenSAML 2.6 to latest version in below locations. |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/opensaml-2.6.6.jar| |/nifidata/apps/nifi_toolkit_binary/lib/opensaml-2.6.6.jar| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (NIFI-10544) Joda-Time 2.2 has reached EOL
Vrinda Palod created NIFI-10544: --- Summary: Joda-Time 2.2 has reached EOL Key: NIFI-10544 URL: https://issues.apache.org/jira/browse/NIFI-10544 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.3 Reporter: Vrinda Palod Please upgrade the joda-time version at below path as ithas reached EOL. |/nifidata/apps/nifi_binary/work/nar/framework/nifi-framework-nar-1.16.3.nar-unpacked/NAR-INF/bundled-dependencies/joda-time-2.2.jar| |/nifidata/apps/nifi_toolkit_binary/lib/joda-time-2.2.jar| -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (NIFI-10115) Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar and nifi-email-nar-1.16.1
[ https://issues.apache.org/jira/browse/NIFI-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-10115: Flags: Important > Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar and > nifi-email-nar-1.16.1 > - > > Key: NIFI-10115 > URL: https://issues.apache.org/jira/browse/NIFI-10115 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.1, 1.16.2 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2022-06-14-17-24-52-479.png > > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-hive-nar and nifi-email-nar-1.16.1 as he version of mail -1.4.7 has > reached EOL > > !image-2022-06-14-17-24-52-479.png! > > Nifi-hive-nar-1.16.1 > nifi-email-nar-1.16.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10127) EOL component guava-28.0-jre.jar upgrade required in nifi_toolkit_binary
Vrinda Palod created NIFI-10127: --- Summary: EOL component guava-28.0-jre.jar upgrade required in nifi_toolkit_binary Key: NIFI-10127 URL: https://issues.apache.org/jira/browse/NIFI-10127 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.3, 1.16.2, 1.16.1 Reporter: Vrinda Palod EOL component guava-28.0-jre.jar upgrade required in nifi_toolkit_binary to the latest guava version. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10126) EOL of guava-28.0-jre.jar in nifi core
Vrinda Palod created NIFI-10126: --- Summary: EOL of guava-28.0-jre.jar in nifi core Key: NIFI-10126 URL: https://issues.apache.org/jira/browse/NIFI-10126 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.3, 1.16.2, 1.16.1 Reporter: Vrinda Palod Please upgrade the guava-28.0-jre.jar to the guava-31.1-jre.jar as used by other modules in the nifi application. Below is the list where the upgrade has not been done. nifi-cassandra-services-api-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-19.0.jar nifi-hadoop-libraries-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-27.0-jre.jar nifi-hbase_1_1_2-client-service-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-12.0.1.jar nifi-hbase_2-client-service-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-11.0.2.jar guava-14.0.1.jar nifi-social-media-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-14.0.1.jar nifi-framework-nar-1.16.1.nar-unpacked/NAR-INF/bundled-dependencies/guava-27.0.1-jre.jar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10125) EOL of javax.activation-api-1.2.0 in nifi-hadoop-libraries-nar-1.16.3.nar
Vrinda Palod created NIFI-10125: --- Summary: EOL of javax.activation-api-1.2.0 in nifi-hadoop-libraries-nar-1.16.3.nar Key: NIFI-10125 URL: https://issues.apache.org/jira/browse/NIFI-10125 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.3, 1.16.2, 1.16.1 Reporter: Vrinda Palod what is the plan to remove the EOl component javax.activation-api-1.2.0 in nifi-hadoop-libraries-nar-1.16.3.nar -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10124) EOL of activation-1.1 jar used in nifi-hive-nar-1.16.3
Vrinda Palod created NIFI-10124: --- Summary: EOL of activation-1.1 jar used in nifi-hive-nar-1.16.3 Key: NIFI-10124 URL: https://issues.apache.org/jira/browse/NIFI-10124 Project: Apache NiFi Issue Type: Improvement Affects Versions: 1.16.3, 1.16.2, 1.16.1 Reporter: Vrinda Palod what is the plan to remove the EOl component javax.activation-1.1 jar from nifi-hive-nar-1.16.3 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10115) Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar
[ https://issues.apache.org/jira/browse/NIFI-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-10115: Description: What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-hive-nar and nifi-email-nar-1.16.1 as he version of mail -1.4.7 has reached EOL !image-2022-06-14-17-24-52-479.png! Nifi-hive-nar-1.16.1 nifi-email-nar-1.16.1 was: What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-hive-nar and nifi-email-nar-1.16.1 as he version of javax.mail -1.4.7 has reached EOL Nifi-hive-nar-1.16.1 nifi-email-nar-1.16.1 > Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar > --- > > Key: NIFI-10115 > URL: https://issues.apache.org/jira/browse/NIFI-10115 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.1, 1.16.2 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2022-06-14-17-24-52-479.png > > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-hive-nar and nifi-email-nar-1.16.1 as he version of mail -1.4.7 has > reached EOL > > !image-2022-06-14-17-24-52-479.png! > > Nifi-hive-nar-1.16.1 > nifi-email-nar-1.16.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10115) Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar and nifi-email-nar-1.16.1
[ https://issues.apache.org/jira/browse/NIFI-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-10115: Summary: Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar and nifi-email-nar-1.16.1 (was: Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar) > Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar and > nifi-email-nar-1.16.1 > - > > Key: NIFI-10115 > URL: https://issues.apache.org/jira/browse/NIFI-10115 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.1, 1.16.2 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2022-06-14-17-24-52-479.png > > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-hive-nar and nifi-email-nar-1.16.1 as he version of mail -1.4.7 has > reached EOL > > !image-2022-06-14-17-24-52-479.png! > > Nifi-hive-nar-1.16.1 > nifi-email-nar-1.16.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (NIFI-10115) Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar
[ https://issues.apache.org/jira/browse/NIFI-10115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-10115: Attachment: image-2022-06-14-17-24-52-479.png > Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar > --- > > Key: NIFI-10115 > URL: https://issues.apache.org/jira/browse/NIFI-10115 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.1, 1.16.2 >Reporter: Vrinda Palod >Priority: Major > Attachments: image-2022-06-14-17-24-52-479.png > > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-hive-nar and nifi-email-nar-1.16.1 as he version of javax.mail -1.4.7 > has reached EOL > > Nifi-hive-nar-1.16.1 > nifi-email-nar-1.16.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-10115) Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar
Vrinda Palod created NIFI-10115: --- Summary: Remove mail-1.4.7 jar from the nifi-hive-nar-1.16.1.nar Key: NIFI-10115 URL: https://issues.apache.org/jira/browse/NIFI-10115 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.2, 1.16.1 Reporter: Vrinda Palod What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-hive-nar and nifi-email-nar-1.16.1 as he version of javax.mail -1.4.7 has reached EOL Nifi-hive-nar-1.16.1 nifi-email-nar-1.16.1 -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Created] (NIFI-9880) EOL for Oracle JavaBeans Activation Framework (JAF) 1.2.0
Vrinda Palod created NIFI-9880: -- Summary: EOL for Oracle JavaBeans Activation Framework (JAF) 1.2.0 Key: NIFI-9880 URL: https://issues.apache.org/jira/browse/NIFI-9880 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.0 Reporter: Vrinda Palod What is the plan for upgrading java activation framework provided by oracle as it has reached the end of life. The current version we use is the latest version and has reached its EOL. [https://github.com/apache/nifi/blob/main/pom.xml] || | | com.sun.activation| | | javax.activation| | | 1.2.0| | | | Looks like the activation framework ownership changed to jakartha EE and might have to use a different version of the library -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Comment Edited] (NIFI-7554) Upgrade guava version
[ https://issues.apache.org/jira/browse/NIFI-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503612#comment-17503612 ] Vrinda Palod edited comment on NIFI-7554 at 3/9/22, 2:24 PM: - [~mtien] Any update on this ? was (Author: JIRAUSER284902): Any update on this > Upgrade guava version > - > > Key: NIFI-7554 > URL: https://issues.apache.org/jira/browse/NIFI-7554 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.11.4 >Reporter: Margot Tien >Assignee: Margot Tien >Priority: Major > Labels: dependencies > Time Spent: 1h 10m > Remaining Estimate: 0h > > Upgrade com.google.guava:guava dependency version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Commented] (NIFI-7554) Upgrade guava version
[ https://issues.apache.org/jira/browse/NIFI-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17503612#comment-17503612 ] Vrinda Palod commented on NIFI-7554: Any update on this > Upgrade guava version > - > > Key: NIFI-7554 > URL: https://issues.apache.org/jira/browse/NIFI-7554 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.11.4 >Reporter: Margot Tien >Assignee: Margot Tien >Priority: Major > Labels: dependencies > Time Spent: 1h 10m > Remaining Estimate: 0h > > Upgrade com.google.guava:guava dependency version. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9662) End of life for mail-1.4.7.jar used in nifi-framework-bundle
[ https://issues.apache.org/jira/browse/NIFI-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-9662: --- Priority: Critical (was: Major) > End of life for mail-1.4.7.jar used in nifi-framework-bundle > > > Key: NIFI-9662 > URL: https://issues.apache.org/jira/browse/NIFI-9662 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.0 >Reporter: Vrinda Palod >Priority: Critical > Labels: dependencies > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-nar-bundles/nifi-framework-bundle/pom.xml. > The current Nifi version has moved to Jakarta mail but this one is not > upgraded yet. > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/pom.xml] > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9661) End of life for mail-1.4.7.jar used in Nifi Registry ranger plugin
[ https://issues.apache.org/jira/browse/NIFI-9661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-9661: --- Priority: Critical (was: Major) > End of life for mail-1.4.7.jar used in Nifi Registry ranger plugin > -- > > Key: NIFI-9661 > URL: https://issues.apache.org/jira/browse/NIFI-9661 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.0 >Reporter: Vrinda Palod >Priority: Critical > Labels: dependencies > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml. > The current Nifi version has moved to Jakarta mail but this one is not > upgraded yet. > [https://github.com/apache/nifi/blob/main/nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml] > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (NIFI-9662) End of life for mail-1.4.7.jar used in nifi-framework-bundle
[ https://issues.apache.org/jira/browse/NIFI-9662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vrinda Palod updated NIFI-9662: --- Description: What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-nar-bundles/nifi-framework-bundle/pom.xml. The current Nifi version has moved to Jakarta mail but this one is not upgraded yet. [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/pom.xml] was: What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml. The current Nifi version has moved to Jakarta mail but this one is not upgraded yet. [https://github.com/apache/nifi/blob/main/nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml] > End of life for mail-1.4.7.jar used in nifi-framework-bundle > > > Key: NIFI-9662 > URL: https://issues.apache.org/jira/browse/NIFI-9662 > Project: Apache NiFi > Issue Type: Improvement > Components: Core Framework >Affects Versions: 1.16.0 >Reporter: Vrinda Palod >Priority: Major > Labels: dependencies > > What is the plan for upgrading mail-1.4.7.jar jar file used inside > nifi-nar-bundles/nifi-framework-bundle/pom.xml. > The current Nifi version has moved to Jakarta mail but this one is not > upgraded yet. > [https://github.com/apache/nifi/blob/main/nifi-nar-bundles/nifi-framework-bundle/pom.xml] > > > -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9662) End of life for mail-1.4.7.jar used in nifi-framework-bundle
Vrinda Palod created NIFI-9662: -- Summary: End of life for mail-1.4.7.jar used in nifi-framework-bundle Key: NIFI-9662 URL: https://issues.apache.org/jira/browse/NIFI-9662 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.0 Reporter: Vrinda Palod What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml. The current Nifi version has moved to Jakarta mail but this one is not upgraded yet. [https://github.com/apache/nifi/blob/main/nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml] -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Created] (NIFI-9661) End of life for mail-1.4.7.jar used in Nifi Registry ranger plugin
Vrinda Palod created NIFI-9661: -- Summary: End of life for mail-1.4.7.jar used in Nifi Registry ranger plugin Key: NIFI-9661 URL: https://issues.apache.org/jira/browse/NIFI-9661 Project: Apache NiFi Issue Type: Improvement Components: Core Framework Affects Versions: 1.16.0 Reporter: Vrinda Palod What is the plan for upgrading mail-1.4.7.jar jar file used inside nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml. The current Nifi version has moved to Jakarta mail but this one is not upgraded yet. [https://github.com/apache/nifi/blob/main/nifi-registry/nifi-registry-extensions/nifi-registry-ranger/nifi-registry-ranger-plugin/pom.xml] -- This message was sent by Atlassian Jira (v8.20.1#820001)
