Member since
07-19-2016
91
Posts
10
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2665 | 08-12-2016 05:05 PM |
06-12-2017
06:25 PM
2 Kudos
@Alvin Jin Also, let's keep in mind that Confluent Schema Registry is for Avro and for Kafka only. Hortonworks Schema
Registry is meant to manage much more than Avro for Kafka. Stay tuned. Hortonworks Schema Registry is meant for all consumers from HDF and HDP platforms, not only for Kafka and will gradually support all commonly used formats.
... View more
06-12-2017
06:42 PM
Correct, you would have to implement a ConfluentSchemaRegistry controller service for NiFi.
... View more
05-23-2017
04:31 PM
@Alvin Jin NiFi uses locally mounted storage for all four of its repositories. There is no support for external repositories unless you can mount them as a local addressable disk. Thanks, Matt
... View more
06-06-2017
09:02 PM
@Alvin Jin My suggestion would be use something like: https://regex101.com/ You can enter your regex and sample test you want to run it against. Matt
... View more
11-03-2017
07:42 PM
Hi @Greg Keys, Thanks for the post. Row filtering works based on the column values which is not in the end. But I am not sure how to filter the rows based on the last column value. Can you please let me know. Thanks
... View more
11-06-2017
05:35 PM
No problem, glad it was helpful 🙂 If you are reaching the login screen, then it means your browser is not forwarding your credentials to NiFi. You could try setting the negotiate properties to just "myhost.de" instead of the full url with port. Another thing to look at might be the domain being used by your KDC... In this example I was using nifi.apache.org as the domain, so I had to add a mapping in /etc/hosts to map nifi.apache.org to localhost so I could use nifi.apache.org in my browser to access my local NiFi. If you are accessing myhost.de to get to your NiFi instance, but that isn't the domain in your KDC, then it won't line up and probably won't forward your credentials.
... View more
08-29-2016
05:17 PM
In 1.0.0 the difference will be that the cache server has to run on all nodes because there is no more concept of choosing where the controller service runs (since there is no master). The cache client would be configured to point to the cache server on one of the nodes, so if that node goes down there is still no automatic failover at this point.
... View more
08-12-2016
05:05 PM
Figured out it. It's not the firewall issue. Since the cluster and edge node are deployed in AWS. The remote host of edge node for site-to-site should be set as its public ip, rather than private ip. Singapore Dataflow: GetFile->output_port # Site to Site properties nifi.remote.input.socket.host=sig-public-ip
... View more
08-10-2016
06:13 PM
Hi @jsequeiros After setting up site-to-site properties on all nodes, the fetchSftp works as expected. Both worker nodes are involved in file fetching. How do we distribute tasks evenly among workers? since I found sometimes one worker took all the files. Sometimes, one took 3, while the other one took 1. I have total 4 test files. Thanks.
... View more
- « Previous
- Next »