Build an e-commerce search prototype with OpenSearch

Connect to the data source

Enter the database connection details.

In the Connect to Database dialog box, enter the RDS Instance ID, Database Name, Username, and Password, and then click Connect.

Select the data source

Choose the tables to import.

In the Select Data Source dialog box, click the RDS tab. Set Select Database to opensearch (the connected instance is rm-bp1pgu04tn0ia280e). In the Select Table section, add product_1 and price_detail_1 to the selected list, and then click OK.

Configure the table schema

This example uses two tables:

• Primary table: the commodity table (product catalog)

• Secondary table: the commodity price table

The primary key ID of the commodity price table is associated with the foreign key ID of the commodity table.

When you define the application schema, the primary table product_1 contains the following 15 fields:

• category_name (category name, TEXT)

• image_url (LITERAL_ARRAY)

• description (product description, TEXT)

• brand_name (brand name, TEXT)

• thumbnail_url (LITERAL_ARRAY)

• title (product title, TEXT)

• is_onsale (INT)

• url (LITERAL)

• brand_id (LITERAL)

• series_id (LITERAL)

• sold_num (sales volume, INT)

• category_id (INT)

• onsale_time (listing time, INT)

• price (DOUBLE)

• series_name (TEXT)

For each field, you can configure the primary key, field tag, field type, and the join to a secondary table.

The secondary table price_detail_1 (data source opensearch:price_detail_1) defines the following four fields:

• discount_price, type DOUBLE

• pid, type INT, set as the primary key

• sale_price, type DOUBLE

• act_price, type DOUBLE

Define the index schema

Add all searchable fields from the commodity table and commodity price table to an index list named "default". This enables queries such as query=default:"keyword".

Set the industry to E-commerce and the template to General. The index field list contains the following index configurations:

• default (default index): contains the fields category_name, description, brand_name, title, create_by, and update_by. Analyzer: Industry - E-commerce general analyzer

• category_name (category name index): Analyzer: Industry - E-commerce general analyzer

• category_id: Analyzer: Keyword

• series_name: Analyzer: Chinese - general analyzer

• brand_name: Analyzer: Chinese - general analyzer

• id: Analyzer: Keyword

• title (title index): Analyzer: Industry - E-commerce general analyzer

• seller_id: Analyzer: Keyword

• brand_id: Analyzer: Keyword

• series_id: Analyzer: Keyword

Enable data synchronization

Configure automatic data synchronization so that updates in the data source are automatically pushed to Open Search.

On the data source configuration page, both the product_1 and price_detail_1 tables are associated with the same ApsaraDB RDS instance, and the Automatic Data Synchronization switch is turned on.

Finalize the application

Click Completed. On the Application Details page, the application status shows that initialization is in progress.

Example: Set up spelling correction

The following steps show how to configure a spelling correction rule.

Create a rough sort expression

1. In the Open Search console, go to Search Algorithm Center > Sort Configuration to open the Policy Management page.

2. Click Create to add a rough sort expression. Select representative fields such as text score and timeliness score. Rough sort significantly affects search performance, so choose fields carefully.

   In the basic information step, select the Target Application and its environment, and enter a Policy Name. The name must be 1 to 30 characters in length, start with a letter, and can contain uppercase letters, lowercase letters, digits, and underscores (_). Set Type to Expression, and then click Next.

   In the sort configuration step, set Scoring Feature to static_bm250 and Weight to 1, and then click Finish.

Create a fine sort expression

Add a fine sort expression for text relevance scoring.

On the basic information page of the Create Policy wizard, enter a Policy Name, set Application Scope to Fine Sort, set Type to Expression, and then click Next to go to the sort configuration step.

In the sort expression editor, enter text_relevance(title), and then click Finish.

Compare sort results

On the Search Test page, compare the results of a standard query with a query that applies the sort expression.

Select the test_han_indexes index and set the application type to Online Application. Enter query=title:'裙子' and set the config clause to start:0. The page shows the results of two fine sort policies side by side so that you can verify the effect of your fine sort configuration.

Drop-down suggestions

Drop-down suggestions help users find queries faster as they type, reducing input effort in e-commerce search. For setup instructions, see Drop-down suggestions.

Category prediction

Category prediction identifies the product category that a search query most likely targets. For setup instructions, see Category prediction.

Distinct clauses

When multiple products from a single vendor score highly, they may dominate the results page. Distinct clauses enforce diversity so that results include products from multiple vendors. For details, see Distinct clauses.

Filter clauses

Filter clauses let users narrow results by attribute ranges, such as price. For details, see Filter clauses.

The following Java code shows how to filter by price range:

if(!lowPrice.equals("")){
  queryElement.addFilter("price>=" + lowPrice);
}
if(!highPrice.equals("")){
  queryElement.addFilter("price<=" + highPrice);
}