Skip to main content

Flume 1.2.0 released

By Anonymous
Listen:

The Apache Flume Team released yesterday the next large release with number 1.2.0. Here a overview about the fixes and additions (thanks Mike, I copy your overview):

Apache Flume 1.2.0 is the third release under the auspices of Apache of the so-called "NG" codeline, and our first release as a top-level Apache project! Flume 1.2.0 has been put through many stress and regression tests, is stable, production-ready software, and is backwards-compatible with Flume 1.1.0. Four months of very active development went into this release: a whopping 192 patches were committed since 1.1.0, representing many features, enhancements, and bug fixes. While the full change log can be found in the link below, here are a few new feature highlights:

* New durable file channel 
* New client API 
* New HBase sinks (two different implementations) 
* New Interceptor interface (a plugin processing API) 
* New JMX-based monitoring support

With this release - the first after evolving into a tier 1 Apache project - we've updated the website and firstly have a well written UserGuide (again thanks to Mike and Ralph for their great effort).

User-Guide: http://flume.apache.org/FlumeUserGuide.html
Api-Documention:  http://flume.apache.org/releases/content/1.2.0/apidocs/

What's the next?
Now, we got a increasing interest into a Windows version. I don't know why, but that's happen. I try to port some of the sinks into a Windows Platform - if you're a Windows Developer and you've time to spent into the project, all hands are welcome.
















Labels:






























Comments











Post a Comment



















Popular posts from this blog





















Why Is Customer Obsession Disappearing?












By
























 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 now we're seeing the problems that came with it. "Cases" What Not to Do Coinbase, as main example, has long been synonymous with making cryptocurrency accessible. Whether you’re a first-time buyer or a seasoned trader, their platform was once the gold standard for user experience. But lately, their customer support practices have been making headlines for all the wrong reasons: Coinbase - Stuck in the Loop:  Users have reported being caugh...




















Post a Comment









Read more




























MySQL Scaling in 2024












By
























When your MySQL database reaches its performance limits, vertical scaling through hardware upgrades provides a temporary solution. Long-term growth, though, requires a more comprehensive approach. This involves optimizing the database strategically and integrating complementary technologies. Caching The implementation of a caching layer, such as Memcached  or Redis , can result in a notable reduction in the load and an increase ni performance at MySQL. In-memory stores cache data that is accessed frequently, enabling near-instantaneous responses and freeing the database for other tasks. For applications with heavy read traffic on relatively static data (e.g. product catalogues, user profiles), caching represents a low-effort, high-impact solution. Consider a online shop product catalogue with thousands of items. With each visit to the website, the application queries the database in order to retrieve product details. By using caching, the retrieved details can be stored in Memcached (a...




















Post a Comment









Read more




























Deal with corrupted messages in Apache Kafka












By
























Under some strange circumstances, it can happen that a message in a Kafka topic is corrupted. This often happens when using 3rd party frameworks with Kafka. In addition, Kafka < 0.9 does not have a lock on Log.read() at the consumer read level, but does have a lock on Log.write(). This can lead to a rare race condition as described in KAKFA-2477 [1]. A likely log entry looks like this:   ERROR Error processing message, stopping consumer:  (kafka.tools.ConsoleConsumer$) kafka.message.InvalidMessageException: Message is corrupt (stored crc = xxxxxxxxxx, computed crc = yyyyyyyyyy    Kafka-Tools  Kafka stores the offset of each consumer in Zookeeper. To read the offsets, Kafka provides handy tools [2]. But you can also use zkCli.sh, at least to display the consumer and the stored offsets. First we need to find the consumer for a topic (> Kafka 0.9):  bin/kafka-consumer-groups.sh --zookeeper management01:2181 --describe --group test  Prior to Kafka 0.9, the only way to get this in...




















Post a Comment









Read more