Member since
07-19-2018
613
Posts
101
Kudos Received
117
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 5095 | 01-11-2021 05:54 AM | |
| 3421 | 01-11-2021 05:52 AM | |
| 8789 | 01-08-2021 05:23 AM | |
| 8385 | 01-04-2021 04:08 AM | |
| 36687 | 12-18-2020 05:42 AM |
06-01-2020
06:46 AM
1 Kudo
@HarshR No problem..... Centos with a Desktop not working right, NOoooooo say it aint so....
... View more
06-01-2020
06:25 AM
@renuu this should be the correct format for a $_GET request to the service: https://localhost:8080/api/alarm?sort-by=from-date=${lastTime} However, are you sure this is the correct Remote Url? I see maybe an issue with sort-by=from-date=... Maybe this should be sort-by=SomeValue&from-date=${lastTime}. I also suspect the dashes (-) in the variable names as this is not a good practice in variable naming. What is the service you are trying to get the alarm from? If its private can you PM me the details. There are 4 ways to pass data from NiFi to InvokeHttp: In the Remote Url as $_GET like above using format: ?value1=1&value2=2 In the body of the flowfile content, for example $_POST of json In Cookie using "Attributes to send" (pick an existing attribute). In Cookie using + (Add) property Based on the service's requirements, you will need to handle invokeHttp to suit the requirements.
... View more
06-01-2020
05:12 AM
@renuu Good morning, the Expression Language you are looking for to create an ISO format timestamp for 10 minutes ago is: ${now():minus(600000):format("yyyy-MM-dd'T'HH:mm:ss.SSS'Z'", "GMT")} Processor Configuration: Processor Configuration FlowFile Output: FlowFile Output If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
05-31-2020
04:24 AM
@Waleed_Malik have you tried setting Nifi to the IP in the port forwarding list: 172.18.0.2 Localhost, 0.0.0.0, 127.0.01 etc can cause issues with nifi web server attaching to the correct IP. Even tho it may say its running on those ports, you may not be able to get to them in the browser. If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
05-30-2020
08:57 AM
1 Kudo
@ischuldt24 ListFile reads the entire directory and creates a 0 byte flowfile for each file to send to FetchFile. If the run schedule is not controlled for your large folder, it is possible to create endless loops which never complete. What you describe sounds like run schedule is very low (0 sec is default), and not enough time to finish reading the directory before it would try again. The length of time that ListFile takes to read the directory would depend on the number of files, network connectivity to the file location, and the NiFi Enviroment's Configuration and Tuning (how many nodes, spec tuning, and flow tuning). Additionally it would be nice for community members to know the details of your environment. NiFi Version, screen shots of configuration of the processor(s), including the run schedule above, details of the NiFi Environment Nodes (ram, cpu, cores, etc)... As for your question about alternatives to ListFIle. You can always execute a custom script, but I suspect this may result in some of the same issues you have if the environment is not capable of handling large numbers of files. If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
05-29-2020
07:01 AM
After you posted this new issue, I created a sample like yours, and I had the same error you have above. Then I added the DistributedMapCacheServer, enabled it, and re-tested my flow. I created a template for DetectDuplicate which you can find here: https://github.com/steven-dfheinz/NiFi-Templates/blob/master/DetectDuplicate_DistributedMapCache_Demo.xml If you install the template, you still have to + ADD the Map Cache Server in the Template's Process Group Controller Services. The NiFI Template system does not include the server (known bug), it only includes the client.
... View more
05-28-2020
12:38 PM
@renuu The solution you are looking for is to add the DistributedMapCacheServer from the controller services tab. Set this to the same port as the DisitributedMapCachClient. Enable. Test flow again. If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
05-28-2020
06:08 AM
1 Kudo
@HarshR I was able to build without issues in a single vagrant VM which I use for build from source projects. I suspect you need a slight modification to your build environment. I have shared all the details of mine below. Here are the commands I used: 1 git clone --recursive https://github.com/apache/metron 2 cd metron/ 3 mvn clean install -DskipTests Here are the changes in the Operating System: 1 yum install wget rsync nano maven java java-devel rpm-build gcc -y 2 yum install ntp python python-devel rpm-build gcc-c++ java-1.7.0-openjdk java-1.7.0-openjdk-devel git -y 3 wget https://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c11-py2.7.egg#md5=fe1f997bc722265116870bc7919059ea 4 sh setuptools-0.6c11-py2.7.egg 5 wget https://downloads.apache.org/maven/maven-3/3.6.3/binaries/apache-maven-3.6.3-bin.tar.gz -P /tmp 6 tar xf /tmp/apache-maven-3.6.3-bin.tar.gz -C /opt 7 ln -s /opt/apache-maven-3.6.3 /opt/maven 8 nano /etc/profile.d/maven.sh 9 chmod +x /etc/profile.d/maven.sh 10 source /etc/profile.d/maven.sh 28 yum --enablerepo=extras install epel-release 29 yum install npm -y The setuptools and custom maven version work were to satisfy building Ambari From Source. The contents of the maven file above: export JAVA_HOME=/usr/lib/jvm/jre-openjdk export M2_HOME=/opt/maven export MAVEN_HOME=/opt/maven export PATH=${M2_HOME}/bin:${PATH} Versions: npm: 3.10.10 node: 6.17.1 maven: 3.6.3 Final Build Summary: [INFO] Reactor Summary: [INFO] [INFO] Metron 0.7.2 ....................................... SUCCESS [ 13.246 s] [INFO] metron-stellar 0.7.2 ............................... SUCCESS [ 10.567 s] [INFO] stellar-common 0.7.2 ............................... SUCCESS [02:49 min] [INFO] metron-analytics 0.7.2 ............................. SUCCESS [ 2.595 s] [INFO] metron-maas-common 0.7.2 ........................... SUCCESS [ 3.928 s] [INFO] metron-platform 0.7.2 .............................. SUCCESS [ 0.203 s] [INFO] metron-zookeeper 0.7.2 ............................. SUCCESS [ 0.695 s] [INFO] metron-test-utilities 0.7.2 ........................ SUCCESS [ 34.358 s] [INFO] metron-integration-test 0.7.2 ...................... SUCCESS [ 38.603 s] [INFO] metron-maas-service 0.7.2 .......................... SUCCESS [ 5.446 s] [INFO] metron-common 0.7.2 ................................ SUCCESS [ 42.033 s] [INFO] metron-statistics 0.7.2 ............................ SUCCESS [ 11.303 s] [INFO] metron-common-streaming 0.7.2 ...................... SUCCESS [ 0.138 s] [INFO] metron-common-storm 0.7.2 .......................... SUCCESS [ 1.258 s] [INFO] metron-hbase 0.7.2 ................................. SUCCESS [ 0.132 s] [INFO] metron-hbase-common 0.7.2 .......................... SUCCESS [ 27.949 s] [INFO] metron-enrichment 0.7.2 ............................ SUCCESS [ 0.171 s] [INFO] metron-enrichment-common 0.7.2 ..................... SUCCESS [ 20.860 s] [INFO] metron-writer 0.7.2 ................................ SUCCESS [ 0.132 s] [INFO] metron-writer-common 0.7.2 ......................... SUCCESS [ 7.072 s] [INFO] metron-writer-storm 0.7.2 .......................... SUCCESS [ 18.700 s] [INFO] metron-storm-kafka-override 0.7.2 .................. SUCCESS [ 9.467 s] [INFO] metron-storm-kafka 0.7.2 ........................... SUCCESS [ 0.640 s] [INFO] metron-profiler-common 0.7.2 ....................... SUCCESS [ 1.150 s] [INFO] metron-profiler-client 0.7.2 ....................... SUCCESS [ 15.490 s] [INFO] metron-profiler-storm 0.7.2 ........................ SUCCESS [ 21.331 s] [INFO] metron-profiler-spark 0.7.2 ........................ SUCCESS [02:31 min] [INFO] metron-profiler-repl 0.7.2 ......................... SUCCESS [ 7.415 s] [INFO] metron-hbase-client 0.7.2 .......................... SUCCESS [ 12.459 s] [INFO] metron-enrichment-storm 0.7.2 ...................... SUCCESS [ 20.594 s] [INFO] metron-indexing 0.7.2 .............................. SUCCESS [ 0.151 s] [INFO] metron-indexing-common 0.7.2 ....................... SUCCESS [ 11.446 s] [INFO] metron-solr 0.7.2 .................................. SUCCESS [ 0.105 s] [INFO] metron-solr-common 0.7.2 ........................... SUCCESS [01:18 min] [INFO] metron-indexing-storm 0.7.2 ........................ SUCCESS [ 0.621 s] [INFO] metron-solr-storm 0.7.2 ............................ SUCCESS [ 18.554 s] [INFO] metron-job 0.7.2 ................................... SUCCESS [ 0.604 s] [INFO] metron-pcap 0.7.2 .................................. SUCCESS [ 4.397 s] [INFO] metron-pcap-backend 0.7.2 .......................... SUCCESS [ 21.134 s] [INFO] metron-data-management 0.7.2 ....................... SUCCESS [ 37.270 s] [INFO] metron-parsing 0.7.2 ............................... SUCCESS [ 0.115 s] [INFO] metron-parsers-common 0.7.2 ........................ SUCCESS [ 29.593 s] [INFO] metron-parsers 0.7.2 ............................... SUCCESS [ 22.274 s] [INFO] metron-management 0.7.2 ............................ SUCCESS [ 6.627 s] [INFO] elasticsearch-shaded 0.7.2 ......................... SUCCESS [ 51.804 s] [INFO] metron-elasticsearch 0.7.2 ......................... SUCCESS [ 0.095 s] [INFO] metron-elasticsearch-common 0.7.2 .................. SUCCESS [ 9.219 s] [INFO] metron-elasticsearch-storm 0.7.2 ................... SUCCESS [ 20.834 s] [INFO] metron-parsing-storm 0.7.2 ......................... SUCCESS [ 22.158 s] [INFO] metron-hbase-server 0.7.2 .......................... SUCCESS [ 10.565 s] [INFO] metron-deployment 0.7.2 ............................ SUCCESS [ 0.249 s] [INFO] Elasticsearch Ambari Management Pack 0.7.2.0 ....... SUCCESS [ 0.174 s] [INFO] Metron Ambari Management Pack 0.7.2.0 .............. SUCCESS [ 1.012 s] [INFO] metron-contrib 0.7.2 ............................... SUCCESS [ 0.090 s] [INFO] metron-docker 0.7.2 ................................ SUCCESS [ 0.641 s] [INFO] metron-performance 0.7.2 ........................... SUCCESS [ 1.571 s] [INFO] metron-interface 0.7.2 ............................. SUCCESS [ 0.129 s] [INFO] metron-config 0.7.2 ................................ SUCCESS [02:22 min] [INFO] metron-alerts 0.7.2 ................................ SUCCESS [03:11 min] [INFO] metron-rest-client 0.7.2 ........................... SUCCESS [ 7.283 s] [INFO] metron-rest 0.7.2 .................................. SUCCESS [01:53 min] [INFO] site-book 0.7.2 .................................... SUCCESS [ 4.580 s] [INFO] 3rd party Functions (just for tests) 0.7.2 ......... SUCCESS [ 0.933 s] [INFO] stellar-zeppelin 0.7.2 ............................. SUCCESS [ 29.864 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 24:59 min [INFO] Finished at: 2020-05-28T12:58:08Z [INFO] ------------------------------------------------------------------------ If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more
05-28-2020
05:58 AM
1 Kudo
@Udhav Yes. Permissions very user specific. Can you create separate scratch locations for the user? They would need to be chown correctly to the user and writeable chmod 777. Right now that /tmp/hive is hadoopuser:supergroup.
... View more
05-28-2020
05:50 AM
@renuu Try the DistributedMapCacheClient Controller Service, not Redis (unless you have a redis system you can use). If you use the other one you can set it to localhost and work within NiFi. After creating the DistributedMapCacheClient be sure to click + and add DistributedMapCacheServer to run on the same port. Here are some screen shots of my sample: DetectDuplicate: DistributedMapCacheClient: DistributedMapCacheServer: Additionally, when working a demo flow, be sure to always route the other relationships during testing (detectDuplicate). You do this so when its running you can see the duplicate or non-duplicate outputs. If you run the flow, and it doesn't work as expected you will see where it went, then can adjust. For example, below is how I use an output port to hold all the routes for InvokeHttp. Later when I know it works, I will auto terminate what I don't need, and route what I do need. Last but not least, spend some time in the community doing research to learn from other examples for your Use Case by searching the community: https://community.cloudera.com/t5/forums/searchpage/tab/message?advanced=false&allow_punctuation=false&filter=includeTkbs,location&include_tkbs=true&location=tkb-board:CommunityArticles&q=distributedmapcache If this answer resolves your issue or allows you to move forward, please choose to ACCEPT this solution and close this topic. If you have further dialogue on this topic please comment here or feel free to private message me. If you have new questions related to your Use Case please create separate topic and feel free to tag me in your post. Thanks, Steven @ DFHZ
... View more