Member since
07-19-2018
613
Posts
100
Kudos Received
117
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
3706 | 01-11-2021 05:54 AM | |
2586 | 01-11-2021 05:52 AM | |
6988 | 01-08-2021 05:23 AM | |
6439 | 01-04-2021 04:08 AM | |
29537 | 12-18-2020 05:42 AM |
08-30-2018
11:20 AM
1 Kudo
The next thing you can do is write your own answer, then accept it. I believe you will get some profile badges for doing that.
... View more
08-30-2018
11:19 AM
@yong lau I seen your other post, but the error was hard to find in the bulk paste. Try posting your error in a code box so that we can see it better. Also be sure to dial into the actual error versus sending needless text. That said, HIVE LLAP requires some configurations we outline above in this post. Check those out as well as the links above Make sure you have the settings for low specs and for a single LLAP container and try to start LLAP. Sometimes it takes me 2-3 times to start without errors. Once you have it working with low specs, slowly increase specs. It is also important to know that the actual errors you need to find, are likely inside of the YARN containers, so you will have to dig them out to truely know the issue that actually stops it from starting.
... View more
08-30-2018
11:11 AM
1 Kudo
@Thuy
Le
There are 2 ways to do this: If you are using submit_date to get the timestamp If you are using now() for the timestamp I assume you want to use 2, but have included both just in case. In both cases you will need to append the "+0000" or other offset if it is known. The expression language is as follows:
${submit_date:toDate("yyyy-MM-dd-HH:mm:ss.S"):format("yyyy-MM-dd-HH:mm:ss.SSS")}+0000 ${now():format("yyyy-MM-dd-HH:mm:ss.SSS")}+0000 You can find the necessary documentation here: https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates If this answer is helpful please choose ACCEPT to mark the question resolved.
... View more
08-29-2018
05:23 PM
1 Kudo
This is the proper method... Good job!
... View more
08-29-2018
05:22 PM
@Bharath
Sudharsanam
Python Curl: https://stackoverflow.com/questions/25491090/how-to-use-python-to-execute-a-curl-command
... View more
08-29-2018
05:00 PM
1 Kudo
@Raffaele S I think you may need to adjust the user/group sync in ranger. Be sure to tail the ranger user sync logs while running the sync so that you can validate things are arriving correctly. Here are my configs: Additionally you will need to create policies in ranger admin as follows: the scrambled user for NiFi Proxy is cn=NIFIHOSTNAME, OU=NIFI Be sure to watch the log files and restart everything after making any changes. If this answer is helpful, please choose ACCEPT to mark the question as resolved.
... View more
08-29-2018
02:34 PM
Being a fan of Nifi and less a fan of programming or code writing (in terms of todays tools), i highly recommend that route over writing any functions. However, it realy is a case of "if it works use it". Test it for your Use Case and determine if the performance is where you need it to be.
... View more
08-29-2018
01:37 PM
1 Kudo
I believe the overall answer is YES... check out this link i found: https://github.com/sendgrid/hive-udfs-1/blob/master/src/main/java/com/maxmind/geoip2/WebServiceClient.java
... View more
08-29-2018
12:48 PM
@Raffaele S Use Group Sync portion of Ranger User Sync. Dialing into a specific group match should reduce the sync time, especially if your LDAPS contains thousands of users who do not need to be authorized in your cluster. Yes, with Ranger Admin UI it is possible to assign roles to groups, users, and tags. If this answer is helpful please click ACCEPT to mark the question as resolved.
... View more
08-29-2018
12:32 PM
I dont think this will be an official answer, but a few things that come to mind: 1. need to make sure the policies are created for at least the normal admin user, then policies for AD users, start with a small test case ( a single user or group) and go forward until all policies satisify all needs i added 2 groups, my personal user, CN=admin,OU=NIFI, and nifi host (cn=HOSTNAME,OU=NIFI) to all - nifi resource policy created a NiFi Proxy policy for cn=HOSTNAME,OU=NIFI 2. in my setups, i was missing a checkbox in nifi config area that turned on the ranger plugin (separate from the ranger config toggle) 3. make sure to restart everything after making adjustment
... View more