Member since
01-27-2023
126
Posts
31
Kudos Received
23
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
46 | 05-31-2023 03:01 AM | |
143 | 05-22-2023 06:55 AM | |
146 | 05-15-2023 05:33 AM | |
285 | 05-10-2023 01:57 AM | |
97 | 05-09-2023 11:40 PM |
06-02-2023
03:45 PM
@Dracile, I do not think that SplitJson is the correct processor for you. What you are trying to achieve might be possible using some JOLT transformations. Unfortunately, I am not near a computer to test a correct transformation but I know that @SAMSAL has plenty of experience in using jolts and he might be able to further assist you.
... View more
05-31-2023
06:20 AM
1 Kudo
@steven-matison Thanks man. It is true, the session.commit() method can be found in the abstract processor class, which is why I did not think of adding it. This helped me a lot! Also I needed to close the Inputstream with IOUtils.closeQuietly(stream_content) Thirdly I had to use the enumerate function for the dictionnary, because it couldn't read the line file = session.putAttribute(file, "list_value", d[file]) So I just filled the dict with empty values and used session.putAttribute(file, "list_value", json_data['list'][i]) It is ugly, but works at least.
... View more
05-31-2023
03:01 AM
Well I am not expert in migrating from a version to another so my answer might not be good enough for you :(. Besides that, I had no time to read the release notes for 1.21.0 and I am not quite sure if anything changed in terms of config files. Assuming that you will keep the hostname and the port for each nifi node and you are using the embedded zookeeper, you should: 1. Stop the current NiFi instance. 2. Copy the authorizations.xml, authorizers.xml, bootstrap.conf, flow.json.gz, flow.xml.gz, logback.xml, login-identity-providers.xml, nifi.properties, stateless.properties, state-management.xml, users.xml and zookeeper.properties into the conf folder from within your new nifi instance. 3. Make sure that in nifi.properties, on your new instance, you are pointing to the same content repository, database repostiory (and all the other repositories) as in the previous instance --> assuming that you followed the best practices and had all those repositories moved on separate disks. Otherwise, make sure that you process all your data on your old instance and start fresh on your new instance. 4. Start the new NiFi Instance. If you are just interested in migrating just the flows from the canvas, you can add all your flows into a template and save them on your local machine. Afterwards, you can open your new nifi instance, upload your template and add it to your canvas.
... View more
05-29-2023
09:32 AM
@MarcusBrandao 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. If you are still experiencing the issue, can you provide the information our experts requested? Thanks.
... View more
05-25-2023
12:59 AM
everybody is entitled to an opinion but may I ask why are you saying this? 🙂 As you are on a NiFi post, I assume that you are referring to the Cloudera NiFi documentation? I find it very helpful, especially combined with the NiFi's original documentation. It even has some additional thins compared to the original documentation. No matter the feedback, positive or negative, it is good when you know what to do with it. In your case, if you would provide a better and more structured feedback, maybe somebody from Cloudera would understand your point of view and he/she could modify the documentation 🙂
... View more
05-23-2023
11:51 PM
Thank you for your response cotopaul. In MQTT 5 there is a feature for Request-Response, in that feature there is a field setting to determine the response topic (different from the actual topic). The response topic field represents the topics on which the responses from the receivers of the message are expected. I was wondering if maybe NiFi could get the response topic field value from the MQTT as an attribute
... View more
05-23-2023
01:21 AM
@mks27, To be really honest, when it comes to login and certificates, I am in no position to provide an input, as I never got to fully understand how they work 😞 While you are waiting for a better answer, from somebody with far more experience and knowledge as me, I would try the following: - Assuming that you configured LDAP authentication, I assume that you have the User and Policies Menu in your NiFi Menu (top Right). - Now, based on your error, I see that you are using the user mohit.kumar and you have no privileges to do anything. - What I would suggest is to login with the user which was provided as Initial Admin Identity and provide your user (mohit.kumar) with all the necessary roles to perform the action you are trying to perform. See: https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#initial-admin-identity Have a look here as well: https://pierrevillard.com/2017/01/24/integration-of-nifi-with-ldap/comment-page-1/
... View more
05-22-2023
08:27 AM
@cotopaul Please go through my latest response before concluding its a hardware or setup issue. FYI, Nifi is working fine for more than a week for me since I removed the ExecuteScript Processor. That's the only change I did and I replicated the issue several times before posting here. Nifi has restarted several times since then without any issues. could you please care to explain what sort of hardware issue it could be that it affects only ExecuteScript processor running python code?
... View more
05-15-2023
10:22 PM
Thank you very much! This gives me confidence that my attempts are not going in the wrong direction.I already use ExecuteStreamCommand Processors excessively and it is a pleasure to use them here as well.
... View more