Member since
03-01-2024
12
Posts
10
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
686 | 04-04-2024 12:13 AM | |
1171 | 03-18-2024 09:51 PM |
12-19-2024
12:21 PM
@mohdriyaz @Dahlgren Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.
... View more
06-02-2024
04:49 AM
2 Kudos
Hi @mohdriyaz , It seems the generatetablefetch by design pushes and penalize the flow to the upstream queue when there is an error that is considered none "sql query" error which per documentation only query execution error will go to the failure rel. It doesnt seem like there is anything you can do to change this behavior. The only thing I can think of to mitigate this issue is by adding another processor as a guard to help checking the connection status before calling the generateTableFetch processor. For example you can use PutSQL processors which seems from the description able to capture connectivity error through retry & maybe the failure rel per description: This is not going to solve the problem 100% but it will minimize it and it will help you capture the error. You can configure how many to retry and for how long in the relationship tab once you select to retry. Hope that helps. If it does help please accept the solution. S
... View more
05-10-2024
06:04 AM
Hello All, Here is my use case I am using Nifi 2.0.0.M1 . I developed one flow where i am connecting to a database and converting result to Json format and store these file on to a folder. This flow (flow.json.raw) is then deployed on a VM that contains Minifi. This flow works fine. Note : In Nifi , all the connection string - with user id and password ( Sensitive = True) is stored in Parameter context. Where as after generating the Flow.json.raw , this information (all the properties in Parameter Context - Nifi) is present inside file ( flow.json.raw) under Parameter Context Object. Issue : Problem here i am facing is , when i deploy this flow on another VM where user provide its own userId and Password , i can edit Flow.json.raw file and update ParameterContext - UserId . But since password is stored in encrypt format. i can't change the ParameterContext - password value. I need to store the Password in the encrypt format so that flow running under minifi should understand it and perform the operations. What i Tried I tried Encrypt-Config under Nifi Toolkit i tried to perform encryption using the algorithm mention in nifi.properties I am still searching for a method through which i can encrypt the password in the same way Nifi is doing with its ParameterContext properties where sensitivity flag is TRUE Thanks, Riyaz
... View more
Labels:
- Labels:
-
Apache MiNiFi
-
Apache NiFi
05-09-2024
08:39 PM
1 Kudo
Used Option2 - Groovy script for this scenario.
... View more
04-04-2024
12:13 AM
1 Kudo
I got the Solution. Use UpdateAttribute processor and Expression Language. Here "SignedURL" is the attribute (containing complex Json) and from that I fetch particular Key value using Expression Language (JSONPATH)
... View more
03-27-2024
12:20 AM
I am using GenerateTableFetch processor ( nifi 2.0) , with following configuration Max_column is "ID" and in some cases it is "UPDATE_DATETIME" This configuration is working fine. But for Partition size > 0 , I am getting no results. No error message in Logs Any Pointer ..??
... View more
Labels:
- Labels:
-
Apache NiFi
03-18-2024
09:51 PM
3 Kudos
I am able to solve the problem Access token Rest API generates two token (check under cookies) - Secure-Request-Token and other is Secure-Authorization-Bearer token. While calling any of the other API (like creating Parameter Context or updating Parameter context) - in Headers provide one more header "Request-Token" with the value of _secure-Request-Token (From cookies).
... View more