The full-text index feature is disabled for ApsaraDB for HBase Performance-enhanced Edition. Its capabilities have been fully migrated to Lindorm and enhanced to be more powerful, mature, and user-friendly.
The Search service combines ApsaraDB for HBase's large-scale data storage with Apache Solr's enterprise-grade search capabilities, enabling complex multidimensional queries and full-text search on massive datasets.
How it works
After data is written to ApsaraDB for HBase Performance-enhanced Edition, Lindorm Tunnel Service (LTS, formerly BDS) — a real-time data synchronization pipeline — replicates that data to an Apache Solr cluster automatically. Queries then run against Solr's full-text indexes, not the HBase tables directly.
The three components — the HBase cluster, LTS, and the Solr cluster — are independent of each other and can be scaled separately. If query throughput grows, scale the Solr cluster. If synchronization becomes a bottleneck, scale LTS. Each tier stays isolated from the others, which also improves overall system stability.
Use cases
The Search service fits scenarios where you store large volumes of data and need to query across multiple fields simultaneously:
Logistics tracking: Store millions of shipment records and retrieve orders matching a specific courier, destination city, and delivery window — all in a single query.
Traffic monitoring: Store high-frequency vehicle records and find all incidents matching a given license plate, road segment, and time range.
E-commerce and membership: Store product catalogs and member profiles, then run complex conditional searches to surface relevant results for site users.
When to use the Search service
| Secondary indexes | Search service | |
|---|---|---|
| Query type | Non-primary-key lookups on a few columns | Complex multidimensional queries and full-text search |
| Best for | Tables with only a few columns and simple, predictable query patterns | Data that requires flexible, ad-hoc combinations of filter conditions |
| Integration | Native HBase feature | Deep integration with Apache Solr |
Use secondary indexes when your queries target a small, fixed set of non-primary-key columns. Switch to the Search service when your business requires combining multiple fields dynamically or running full-text search.
Search service vs. standalone Apache Solr
The Search service is fully compatible with Solr APIs, so you can use the same query syntax and tooling you already know. On top of that, it adds:
Simplified operations: Associate the HBase cluster with the Solr cluster through HBase Shell or API operations — no need to monitor the health of each service separately.
High reliability: Built-in monitoring and alerting, with high read/write performance.
Activate the Search service
Create an ApsaraDB for HBase Performance-enhanced Edition cluster.
Create an LTS cluster.
In the ApsaraDB for HBase console, click Full-text Index to purchase a Search instance and associate it with your HBase cluster.
For detailed steps, see Activate the Search service.
What's next
Quick start — run your first query against the Search service.
Manage indexes — create, update, and delete full-text indexes.
Update the configuration set — best practices for Solr configuration sets.