Member since
07-30-2018
49
Posts
7
Kudos Received
7
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2368 | 11-22-2021 08:37 AM | |
1477 | 11-01-2021 08:33 AM | |
1649 | 12-08-2020 09:27 AM | |
2722 | 10-14-2020 03:58 AM | |
1260 | 10-12-2020 10:29 AM |
12-08-2020
09:17 AM
@kumar79 I am not very sure with your complete use case, if you explain more would be better. Why you want to take date from shell/cron? you can use UpdateAttribute processor with custom property and use NiFi Regular Expression language to set date for you. E.g https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html#dates The attribute later you can use in your flow to satisfy QL condition. Hope it helps. -Akash
... View more
12-08-2020
09:05 AM
@DarkStar Is the join query works fine on PostgreSQL CLI? If yes, then what is the jdbc driver you are using? is that jdbc version supports joins with duplicate fields? It looks like you have T1.track_id and T3.track_id which are conflicting. May be can you try to change the field name, test it on psql CLI and then test again in NiFi ? -Akash
... View more
12-08-2020
08:49 AM
@scoe74 If it is just token you have to take from SiteA and then using that token you can download data from SiteB then you can use 1st InvokeHTTP to take the token, add the token as flowfile attribute and then using that token you can use 2nd InvokeHTTP to download the data. Hope it helps you. -Akash
... View more
11-23-2020
12:21 AM
1 Kudo
@dzbeda You should extend the Content repo as it will store the content of your flowfiles. Please go through the best practices for setup https://community.cloudera.com/t5/Community-Articles/HDF-CFM-NIFI-Best-practices-for-setting-up-a-high/ta-p/244999 Also note that NiFi should not be used as backup for any failover mechanism as it is meant for processing and not for storage. I would recommend to store the data to may be some centralised location from where you can store and retrieve data as per use case and in case of failure as well you can have backup on that location. NiFi can be used to hold data for a day or 2 but if it is not processed then it will hold data at content repository and can fill the content repo storage.
... View more
11-20-2020
02:30 AM
Do you see any Warns, Errors for "CN=admin, OU=ApacheNiFi" user in nifi-user.log file when you login to the ui?
... View more
11-17-2020
08:16 AM
@Vapper Looks like there are issues with authorization, can you please check your authorizations.xml file and check if the user you have mentioned in INITIAL_ADMIN_IDENTITY is assigned to all expected policies?
... View more
11-17-2020
05:28 AM
@fgarcia Cloudera NiFi Kafka processors should work with all Kafka distributions be it HDP, CDH, CDP, Confluent or Apache Kafka. We generally recommend to use *Kafka_0_10 with Broker version as 0.10 and likewise. Hope it helps 🙂
... View more
10-14-2020
03:58 AM
@justenji The timestamp details are not exposed by NiFi on Flow but NiFi does maintain it in flow history. [Only if NiFi is secured with SSL] So you can try https://${hostname}:${NIFI_PORT}/nifi-api/flow/history/components/{componentId} to get the details. But it will provide all history of that component you have to parse it as per your need. Note that this info gets purged as per flow history parameters in nifi.properties so you will have these details not from beginning but beginning of the date [days/hours] mentioned in properties. If you are looking for flow timestamp when it is exported to NiFi-Registry then checkout for https://${hostname}:${NR_PORT}//nifi-registry-api/buckets/{bucketId}/flows/{flowId} Br, Akash
... View more
10-12-2020
10:29 AM
@sunile_manjee I am not very familiar with AWS ELB but you can try to use HandleHttpRequest and HandleHttpResponse processors and check if it serves your use case
... View more
10-12-2020
10:18 AM
@rstewart Counter is in-memory content for NiFi service. There is no direct way to get value of particular counter. But you can try below call to get a json response from NiFi about all counters. curl -v -X GET "https://$HOSTNAME:9091/nifi-api/counter" -H "Authorization: Bearer $TOKEN" -H "Connection: close" -k Once you get the Json response you can parse it as per your use case
... View more
- « Previous
-
- 1
- 2
- Next »