You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

[Progress record]:
Proposed time: 2022/07/27
Discussion time:
Accept/Reject Time:
Complete time:
[issues]: https://github.com/apache/incubator-linkis/issues/2533
[email]: After creating the LKIP and writing the preliminary content, start a discussion on the LKIP proposal. Currently, the discussion must be initiated in the WeChat group [Apache Linkis Community Development Group], and the minutes can be sent to the official dev mailbox of linkis. The email address for the minutes can be placed here
[Release]: The (planned) release version of Linkis
[Proposer]: An Lin

Motivation & Background

Currently linkis does not integrate hbase engine

Basic concept

Expect to achieve goals

  • Added support for hbase engine, allowing users to execute hbase commands through linkis+DSS.
  • Dependent environment: hbase client environment variable HBASE_HOME
  • Default supported hbase version: 2.10
  • Planned supported engine parameters and naming: None
  • Main usage scenarios: A script ending with hbase can be created in the scriptis of DSS, and hbase commands can be written in the script in the same way as the hbase shell.

Implementation plan

According to the linkis engine research and development ideas, the hbase client is packaged into the linkis engine using the jruby framework, which can be used as a conventional engine in linkis.

Changes


Modification Detail
1
Modification of maven module


2Modification of HTTP interface
3Modification of the client interface
4Modification of database table structure
5Modification of configuration item
6Modification Error code 
7Modifications for Third Party Dependencies

Compatibility, Deprecation, and Migration Plan

  • What impact (if any) will there be on existing users?

No effect, it is just to increase hbase engine support, users can choose whether to integrate or not

  • If we are changing behavior, how will we phase out the older behavior?
  • If we require special migration tools, describe them here.
  • When will we remove the existing behavior?


  • No labels