OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Database

KV - V4.3.5
  • OBKV overview
  • Architecture
  • OBKV-Table
    • Introduction to OBKV-Table
      • Overview
      • OBKV-Table operation types
      • Core features of OBKV-Table
      • Differences between replace and insert_or_update
      • Supported value types
      • OBKV-Table data models
    • Use the OBKV-Table Java client
      • Java development guide for OBKV-Table
      • Prepare for development with OBKV-Table
      • Use the OBKV-Table Java client to connect to a cluster
      • Set client parameters
      • Supported client interfaces
      • Use the OBKV-Table Java client
    • Use the OBKV-Table GO client
      • Use the OBKV-Table Go client to connect to a cluster
      • Overview of the Go client
      • Individual API operations
      • Batch operations
      • About queries
      • Aggregation API
      • Filters
    • FAQ
  • OBKV-HBase
    • Overview
    • OBKV-HBase core features
    • Compatibility with HBase
    • Deployment
    • Application development with OBKV-HBase
      • Overview of OBKV-HBase application development
      • Data model
      • Data model design
      • Connect to a cluster using the OBKV-HBase client
      • Migrate HBase business code to OBKV-HBase
      • Data operation examples
      • Delete expired data
    • OBKV-HBase migration guide
    • OBKV-HBase management
      • Overview
      • High availability
      • Security and permissions
      • Monitoring metrics
    • Performance test
    • OBKV-HBase integrations
      • Flink
        • Synchronize data to OBKV-HBase by using Flink
    • Views
    • FAQ

Download PDF

Document Feedback
  1. Documentation Center
  3. OceanBase Database
  5. KV
  7. V4.3.5

OBKV-HBase core features

Last Updated:2026-09-04 10:25:15

HBase model features
Advanced features
OBKV-HBase client compatibility

HBase model features

Feature
Description
Basic features
  • Compatible with most features of HBase 0.94 and 1.1.13 via interface implementation
  • Supports common interfaces, such as put, get, exists, delete, append, increment, scan, and more
  • Supports HBase row locks
  • put, delete, get, and scan interfaces support multiple column families
  • Supports subpartitions starting from V4.3.5 BP2
  • Supports both standard table models and time series table models starting from V4.3.5 BP2
Filter
  • Supports filters including CompareFilter, SingleColumnValueFilter, PageFilter, ColumnCountGetFilter, PrefixFilter, SkipFilter, WhileMatchFilter, PageFilter, ColumnPrefixFilter, ColumnPaginationFilter, FirstKeyOnlyFilter, KeyOnlyFilter, RandomRowFilter, and TimestampsFilter
  • Supports multiple filters using FilterList
TTL
  • Table-level TTL (the TTL policy is set on the table, and all rows expire according to the table-level policy)
  • Supports real-time invisibility of expired data

Notice

The expired data deletion (TTL) feature is only available for OceanBase KV scenarios. It is disabled for SQL scenarios to prevent unexpected data loss.
MaxVersion
  • Supports configuring the maximum number of versions to keep, with excess versions deleted asynchronously in the background when combined with TTL
Ecosystem
  • Supports Flink integration with OBKV-HBase
Development tools
  • Does not support HBase shell
  • Supports accessing HBase table data via MySQL client

Advanced features

Feature
Description
Transactions
  • Single operations support row-level transactions
  • Batch operations support single-node transactions
  • Distributed transactions across nodes are not supported yet
Disaster recovery Leverages all existing disaster recovery capabilities of OceanBase Database, such as multi-replica architecture, primary/standby databases, two-city three-center, three IDCs across two regions, and five IDCs across three regions deployments
Multi-tenancy Leverages OceanBase Database's multi-tenancy capabilities
Scalability Leverages OceanBase Database's data partitioning and elastic scaling capabilities
Backup and restore Leverages OceanBase Database's backup and restore capabilities
Data compression Supports storage data compression
Data encryption Supports transparent data encryption (TDE)

OBKV-HBase client compatibility

Notice

OBKV-HBase only supports Java clients.

The obkv-hbase-client-java version roadmap is as follows:

  • 1.x client versions are compatible with HBase 1.x business scenarios.
  • 2.x client versions are compatible with HBase 2.x business scenarios.

Details are as follows:

obkv-hbase-client-java 1.x client version
Release notes
1.1.0 Supports partition splitting and batch get operations.
obkv-hbase-client-java 2.x client version
Release notes
2.1.0 Supports partition splitting and batch get operations.

Previous topic

Overview
Last

Next topic

Compatibility with HBase
Next
on this page
HBase model features
Advanced features
OBKV-HBase client compatibility