forked from cloudera/flume
/
RELEASENOTES
53 lines (46 loc) · 1.74 KB
/
RELEASENOTES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
Flume 0.9.1 Release Notes
=========================
This release of Flume has implements the core framework and has
implementations of most of the major features of the Flume system
describes in the Flume User Guide. Some sections are stable, while
others are have code under active development. We also list several
known bugs and instabilities.
Supported platforms: Linux, requires Java 1.6, not tested on windows
Stable:
* Introduction / Design
* Quick Start
* Psuedo-Distributed Mode (node configuration via master)
** Simple web interface
** Agent/collector roles
* Fully-Distributed Mode section:
** Static configuration of failover chains.
** Single master Memory-Backed and Zookeeper-Backed Configuration
Store.
* Data model of Flume event
* Output Bucketing with the CollectorSink
* Flume's Dataflow language
* Flume Shell
Stabilizing:
* Fully-Distributed Mode:
** Modes for unreliable network conditions in testing
** Disk failover mode and End-to-end modes
** DFO and E2E retransmission is unstable when connected to a network
sink.
* Sink/Source/Decorator Plugins
Active Development:
* Automatic versions of failover.
* Logical Naming translations.
* Multiple Flume Masters
* Output Formatting options
* Custom metadata extraction
Known Bugs
* ZK session timeout makes master unrecoverable
* Shell does not provide useful feedback on errors
* Translated configurations are not always auto-updated when logical
nodes are newly spawned onto physical nodes. An extra 'refreshAll'
command may need to be executed.
* Two collectorSources on the same node sometimes fails to translate
the more recent collectorSource
* Logical node names must be unique
* Logical nodes with the same name as the physical nodes on which they
run cannot be deleted