leonardBang opened a new pull request #12687:
URL: https://github.com/apache/flink/pull/12687
## What is the purpose of the change
* Flink doesn't contains a hbase shade jar right now, so users have to add
hbase dependency manually. This pull request import a new
flink-sql-connector-hbase module likes flink-sql-connector-elasticsearch7 to
offer bundled jar.
* **Specially, this PR is inspired by #12369， #9898**
## Brief change log
- Add new modular flink-sql-connector-hbase.
- Add new modular flink-end-to-end-test-hbase.
## Verifying this change
* End2end test `SQLClientHbaseITCase` covered
The new module flink-sql-connector-hbase only includes necessary
dependencies that used to reading or writing data from/to hbase. And the module
flink-end-to-end-test-hbase, just as name implies, is used for hbase e2e test.
(1) We do not shade hadoop dependencies into the jar. Because
flink-sql-connector-hive doesn't contains either, so we do this in similar way.
(2) We shade all dependencies that hbase needed but except
org.apache.hadoop.hbase.codec.* for preventing hbase region server throw
timeout exception . Because the hbase region server can not find the shaded
codec class to decoding data(byte[]).
(3) We add a new module, flink-end-to-end-test-hbase, only for e2e test.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: (no)
- The serializers: (no)
- The runtime per-record code paths (performance sensitive): ( no)
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
- The S3 file system connector: (no)
## Documentation
- Does this pull request introduce a new feature? (no)
- If yes, how is the feature documented? (not applicable / docs / JavaDocs
/ not documented)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
