Skip to main content
Create a ParadeDB index over the mock_items table from Connect Your App. The same index supports text search, vector search, filtering, sorting, and aggregations in the next page.
If search_idx already exists, drop it first with DROP INDEX search_idx;.
The first indexed column, id, is also the key_field. ParadeDB uses the key field as the row’s stable identifier inside the index. In your own schema, use a primary key or another column with a UNIQUE constraint. See Choosing a Key Field for the full rules. Everything after id is a field you can search, filter, sort, group, or aggregate. The description column is indexed for full-text search, embedding is indexed for vector search, and fields like rating, category, and created_at are available for filters, Top K queries, and facets. For production schemas, define this index in your migration system instead of running ad hoc SQL. The full Create an Index reference includes framework-native examples and tokenizer options. Next, run your first queries.