@Deenag Yes, this is a typical method to filter out flowfiles based on attributes matching expression language.  You setup the routes you want and ignore the rest. ... View more

@Nidutt you should be able to use NifI expression language in the flow to change date int to ISO timestamps.    Here is a template you can use that shows many examples of timestamp formatting:   https://github.com/steven-matison/NiFi-Templates/blob/master/Working_with_TimeStamps.xml   I think you may find that nifi attributes remain strings in your flow without a strict date type, after all an ISO timestamp is really a string, your end point database just knows it is a "timestamp"....       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

@jloormoreira    A couple suggestions:   If you are using the hdp sandbox, you should be be able to spin up the vm and have ambari and services installed out of the box.  No need to run cluster install wizard.  This is the HDP Sandbox: https://www.cloudera.com/downloads/hortonworks-sandbox/hdp.html?utm_source=mktg-tutorial If you are installing a cluster yourself,  you need to back up and complete the documentated steps to install ambari-server & ambari-agent and setup ambari-server.  Install as root user and do not do anything for "SSL" until you have base install completed.   Complete host mapping for your fqdn (/etc/hosts) in your machine and in the VM.  Make sure these are right.   Make sure the VM hostname is right and persisting.   Next, in the VM complete password less auth steps for the node by creating ssh keys (ssh-keygen) and adding that ~/.ssh/id_rsa.pub key to root ~/.ssh/authorized_keys.  Be sure to do the initial login ssh root@yourfqdn and click Y the first time.  Now you can go to ambari to install cluster.   During cluster install use the id_rsa  (not id_rsa.pub) for register host.  Once these basics are completed the rest of the install should go fine.  My last bit of advice is, if the size of the vm you are using is limited do no try to install all ambari services.   It will take a 16-32gb instance to run whole stack and even this is almost too much for single node.  In the 8-16gb range you will have issues trying to install everything so recommend installing only basics (yarn,hdfs,ambari metrics) + the other components you need. ... View more

Python 3 is not supported by any versions of Ambari.   You can reference the following posts for more information:   https://community.cloudera.com/t5/Support-Questions/Python3-x-Compatibility-in-HDP-2-6-x-and-3-x/td-p/242185     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

@Mondi you should be able to enable the HBASE plugin by editing the hue.ini file from your admin console and telling it the HBASE Thrift Server.     Reference https://docs.gethue.com/administrator/configuration/connectors/#hbase for the information below.   HBase Specify the comma-separated list of HBase Thrift servers for clusters in the format of “(name|host:port)": [hbase] hbase_clusters=(Cluster|localhost:9090) In the full reference above there are some additional hbase artifacts for impersonization and kerberos. ... View more

@redmonc2   You should update the post with the input data, and a screen shot of your flow, for better responses from your peers.  If you provide this info I will update my response below.   Without being able to see the input data I believe you just need to adjust your flow so that you are breaking up the input data into multiple flowfiles.   For example, if that input data is lines of dates you want to change formats, your flow should split the lines with SplitText, then get each split FlowFiles date to an attribute called date (${date}) with ExtractText that uses regex to get the entire split content to the date attribute.  With an attribute called date in each flowfile,  you can then use your expression language in updateAttribute:   ${date:toDate("ddHHmm:ssMMMyy"):format("yyyy/MM/dd HH:mm:ss")}   Once you have the format correct for each date, you can proceed with the dates downstream as attributes or write them back to the content of the flowfile and merge them together.   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