Skip to main content

SolR, NiFi, Twitter and CDH 5.7

Image
By

Since the most interesting Apache NiFi parts are coming from ASF [1] or Hortonworks [2], I thought to use CDH 5.7 and do the same, just to be curious. Here's now my 30 minutes playground, currently running in Googles Compute.

On one of my playground nodes I installed Apache NiFi per
mkdir /software && cd /software && wget http://mirror.23media.de/apache/nifi/0.6.1/nifi-0.6.1-bin.tar.gz && tar xvfz nifi-0.6.1-bin.tar.gz

Then I've set only nifi.sensitive.props.key property in conf/nifi.properties to an easy to remember secret. The next bash /software/nifi-0.6.1/bin/nifi.sh install installs Apache NiFi as an service. After log in into Apache NiFi's WebUI, download and add the template [3] to Apache NiFi, move the template icon to the drawer, open it and edit the twitter credentials to fit your developer account.

To use an  schema-less SolR index (or Cloudera Search in CDH) I copied some example files over into a local directory:

cp -r /opt/cloudera/parcels/CDH/share/doc/solr-doc-4.10.3+cdh5.7.0+389/example/example-schemaless/solr/collection1/conf/* $HOME/solr_configs/conf/

And added to solrconfig.xml into the <updateRequestProcessorChain name="add-unknown-fields-to-the-schema"> declaration below <updateRequestProcessorChain name="add-unknown-fields-to-the-schema">:
<str>EEE MMM d HH:mm:ss Z yyyy</str>

So it looks like:
<processor>
<arr name="format">
<str>EEE MMM d HH:mm:ss Z yyyy</str>

Since the new Twitter API HTML format the client source, I added a HTML strip processor into the same declaration:

</processor>
  <processor class="solr.HTMLStripFieldUpdateProcessorFactory">
  <str name="fieldName">source_s</str>
</processor>

All configs are available per Gist [4,5].

To get the configs running, initialize SolR:

solrctl --zk ZK_HOST:2181/solr instancedir --create twitter $HOME/solr_configs
solrctl --zk ZK_HOST:2181/solr collection --create twitter -s 2 -c twitter -r 2

Setup Banana for SolR is pretty easy:
cd /software && wget https://github.com/lucidworks/banana/archive/release.zip && unzip release.zip && mv banana-release banana && cp -r banana /opt/cloudera/parcels/CDH/lib/solr/webapps/ on one of the solr hosts and check if it's running per http://solr-node:8983/banana/src/index.html. To move fast forward, I have a dashboard available on gist [5], too.

 Screenshot Dashboard:


Apache NiFi flow:

Conclusion

This demo shows that's pretty easy today by using available tools to setup more or less complex data flows within a few hours. Apache NiFi is pretty stable, has a lot of sinks available and runs now 2 weeks in Google Compute, captured over 200 mio tweets and stored them in SolR as well as in HDFS. It's interesting to play around with the data in realtime, interactive driven by Banana. 





Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

What are the performance implications of cross-platform execution within Wayang?

By
Apache Wayang ® enables cross-platform execution across multiple data processing platforms such as Spark, Flink, Java Streams, PostgreSQL or GraphChi. This capability fundamentally changes the performance behavior of distributed data pipelines. Wayang reduces manual data movement by selecting where each operator should run, but crossing platform boundaries still introduces serialization cost, shifts in locality, different memory strategies and new tuning constraints. Understanding these dynamics is essential before adopting Wayang for multi-platform pipelines at scale. Apache Wayang is a cross-platform data processing framework that lets developers run a single logical pipeline across engines such as Apache Spark, Apache Flink or a native Java backend. It provides an abstraction layer and a cost-based optimizer that selects the execution platform for each operator. This flexibility introduces new performance variables that do not exist in single-engine systems. Engine boundaries ...
Read more

Building a Model-Agnostic Multi-Agent System with OpenClaw

By
Over one week we rebuilt our AI stack around OpenClaw’s multi-agent architecture to avoid provider lock-in and stop wasting premium tokens. By aligning models to tasks, diversifying fallbacks across providers, enforcing minimal tool access, and switching to memory-first workflows with ephemeral sessions, we reduced token usage per task by about 70% and cut our monthly bill by 77% while improving operational resilience. How We Achieved 77% Cost Reduction and Provider Independence Over the past week, we rebuilt our AI infrastructure around OpenClaw’s multi-agent architecture. The result was a 77% cost reduction , provider independence , and a delegation system that routes work to the most cost-effective model for each job. Below is the technical journey of optimizing a 7-agent squad with OpenClaw. The Challenge: Model Provider Lock-In We started with a simple problem: our entire squad defaulted to a single model provider. This created three issues: Cost inefficiency beca...
Read more