Member since
07-30-2019
333
Posts
356
Kudos Received
76
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
8579 | 02-17-2017 10:58 PM | |
1789 | 02-16-2017 07:55 PM | |
6967 | 12-21-2016 06:24 PM | |
1411 | 12-20-2016 01:29 PM | |
973 | 12-16-2016 01:21 PM |
04-15-2016
04:50 PM
Hi, the above links contain detailed instructions on removing and adding the NiFi service again, did they work for you? Or are you trying to preserve whatever data you have in the sandbox for NiFi?
... View more
03-29-2016
01:51 PM
To close the loop, Apache NiFi 0.6.0 now includes support for Kerberized HBase access.
... View more
03-28-2016
01:11 AM
I think the error is in the -d parameter that you specified. It must be a short name, not a full path. It will look in a directory in a predefined schemas folder then.
... View more
03-22-2016
04:58 PM
8 Kudos
Well, it's a super-loaded question, but I'll try to highlight the most important differences and give some food for thought: Kettle is an ETL tool, came from ETL world, and largely remains there. Pentaho is making a shift to introduce many BI and reporting features, too NiFi is a dataflow management platform. This is a term somewhat new to the IT crowd, but I'm sure over time it will become as ubiquitous as ETL, BI, etc. It has some aspects of ETL, Streaming, Batch, Workflow, but takes a niche of its own. Imagine if you wanted ingest to become a first-class citizen in your IT landscape. NiFi has interactive model, where one 'molds' the flow as the data continues to flow. E.g. there's no requirement to compile and deploy changes to the flow 'somewhere' NiFi's Provenance feature is the biggest differentiator. Think super-charged lineage, where complete data history is captured on top of lineage (not sampling, but full payloads, changes, etc.). This enables powerful search and replay capabilities down the line, too. NiFi has native clustering, remote site-to-site protocol, backpressure, flow control, full REST API among other highlights - look them up 🙂
... View more
03-22-2016
04:51 PM
3 Kudos
To add to this - a better way to act on important errors is to configure the logging subsystem to additionally send specific error categories to your destination of choice (e.g. active notification vs passive parsing of logs). NiFi is leveraging a very flexible logback system (an evolution of log4j). The best part - changes to the $NIFI_HOME/conf/logback.xml configuration file do not require an instance restart, will be picked up within 30 seconds or less.
... View more
03-19-2016
11:37 AM
4 Kudos
Yes, check out these processors: TransformXml EvaluateXQuery EvaluateXPath With approaches described in your link above and these processors one should be able to achieve it easily.
... View more
03-15-2016
02:21 PM
1 Kudo
Ahmed, still trying to understand the issue. Did you run into a roadblock when implementing the receiving side? Looks like you had the send side figured out already. Reading through the Azure Service Bus docs, they do mention there is a AMQP support. NiFi supports AMQP out-of-the-box, can you leverage it to communicate with Azure SB? https://azure.microsoft.com/en-us/documentation/articles/service-bus-amqp-overview/
... View more
03-15-2016
01:43 PM
2 Kudos
I wonder if this is what you were looking for: https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi.processors.azure.eventhub.GetAzureEventHub/index.html
... View more
03-14-2016
01:53 PM
5 Kudos
Hi Shishir,
The currently available NiFi version does not yet support a kerberized HBase. You can watch https://issues.apache.org/jira/browse/NIFI-1488 for progress.
... View more
03-08-2016
06:21 PM
2 Kudos
You need to forward port 9090 for your VM, e.g. map 9090->9090 in VM network settings
... View more