[Summer 2021] Seata-Server HBase or Elasticsearch storage support

# Background

Seata-Server storage mode currently supports File, MySQL, Oracle, PostgreSQL, Redis, etc., but there is still a lack of storage support for large amounts of data, which makes the design of data audit complicated. So we want the storage of Seata-Server to support HBase, ElasticSearch, etc.

The Seata community wants to open the HBase or ElasticSearch adapting task to the `Summer 2021`.

# Target

This topic requires reference to Seata's existing storage schema extensions to implement HBase or Elasticsearch storage support, or both if the energy permits.

# Difficulty
Medium

# Mentor
@slievrly
[jimin.jm@alibaba-inc.com](mailto:jimin.jm@alibaba-inc.com)

# Output Requirements
* Implement HBase or Elasticsearch storage support for Seata-Server.
You can do both, if you have the energy.

# Technical Requirements
* Familiar with Java programming language.
* Understand common design patterns
* Ability to read source code

————————————————————————

# 背景
Seata-Server存储模式目前支持file，MySQL、Oracle、PostgreSQL、Redis等，但是仍缺少适合超大数据量的存储支持，这使得数据审计的设计方案变得复杂。因此希望Seata-Server的存储支持Hbase、Elasticsearch等。

Seata 社区想将 Hbase 或 Elasticsearch 的适配任务开放给 `Summer 2021`。

# 目标

这个题目要求参考Seata已有的存储模式扩展实现Hbase 或 Elasticsearch存储支持，如果精力允许也可实现两种方案。

# 难度
中等

# 导师
@slievrly
[jimin.jm@alibaba-inc.com](mailto:jimin.jm@alibaba-inc.com)

# 产出要求
* 实现 Seata-Server 的HBase 或 Elasticsearch 存储支持。
如果精力允许，可以2种存储方案都实现。

# 能力要求
* 熟悉Java开发语言。
* 理解常见设计模式。
* 具备一定的源码阅读能力

Start by reading Seata-Server's existing storage schema extensions and the current File, MySQL, Oracle, PostgreSQL, and Redis storage implementations. Implement HBase or Elasticsearch storage support, following an existing storage mode's design, and verify that the selected backend is supported by Seata-Server.

Written by the indexing model from the issue text.