分享

关于Flume的HbaseSink可否在非hbase节点上正常工作?

hongqianli 发表于 2015-7-30 10:43:32 [显示全部楼层] 只看大图 回帖奖励 阅读模式 关闭右栏 11 26204
NEOGX 发表于 2015-7-30 14:30:46
hongqianli 发表于 2015-7-30 13:31
你应该没有用过hbasesink吧

恩,看到了。谢谢。
不过官网似乎已经写的很清楚了,这个是写入hbase的,没有hbase环境,恐怕写入不了





This sink writes data to HBase. The Hbase configuration is picked up from the first hbase-site.xml encountered in the classpath. A class implementing HbaseEventSerializer which is specified by the configuration is used to convert the events into HBase puts and/or increments. These puts and increments are then written to HBase. This sink provides the same consistency guarantees as HBase, which is currently row-wise atomicity. In the event of Hbase failing to write certain events, the sink will replay all events in that transaction.

The HBaseSink supports writing data to secure HBase. To write to secure HBase, the user the agent is running as must have write permissions to the table the sink is configured to write to. The principal and keytab to use to authenticate against the KDC can be specified in the configuration. The hbase-site.xml in the Flume agent’s classpath must have authentication set to kerberos (For details on how to do this, please refer to HBase documentation).

For convenience, two serializers are provided with Flume. The SimpleHbaseEventSerializer (org.apache.flume.sink.hbase.SimpleHbaseEventSerializer) writes the event body as-is to HBase, and optionally increments a column in Hbase. This is primarily an example implementation. The RegexHbaseEventSerializer (org.apache.flume.sink.hbase.RegexHbaseEventSerializer) breaks the event body based on the given regex and writes each part into different columns.

The type is the FQCN: org.apache.flume.sink.hbase.HBaseSink.


回复

使用道具 举报

hongqianli 发表于 2015-7-30 14:45:52
NEOGX 发表于 2015-7-30 14:30
恩,看到了。谢谢。
不过官网似乎已经写的很清楚了,这个是写入hbase的,没有hbase环境,恐怕写入不了
...

我想也是吧。谢了。

回复

使用道具 举报

12
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

关闭

推荐上一条 /2 下一条