Skip to content

The Data Scientist

vector search instead

Why finding a home requires vector search instead of SQL

In the world of database management and information retrieval, the “Zero Results” page is the ultimate failure. For decades, structured query language (SQL) has ruled the web. If a user searches for bedroom_count > 3 AND location = ‘Los Angeles’, SQL works perfectly.

But human intent is rarely that structured.

When a user types “modern home with good natural light and a chef’s kitchen,” traditional keyword-based search engines fall apart. They look for the exact string “natural light” in the description column. If the agent wrote “sun-drenched” instead, the database returns zero results. This is the “Vocabulary Mismatch” problem, and it has plagued vector search instead (Real Estate, E-commerce, Travel) for 20 years.

However, the rapid adoption of Vector Embeddings and Semantic Search is finally solving this.

The Shift from Keyword to Context

The breakthrough lies in moving away from lexical search (matching words) to semantic search (matching meaning).

In a modern AI-driven architecture, listing data is no longer just stored as text strings. Instead, descriptions and images are passed through an embedding model (like OpenAI’s text-embedding-3 or similar) to generate high-dimensional vectors.

  • The Old Way: Search for “Fixer Upper.” Database looks for the string “Fixer Upper.”
  • The New Way: Search for “Fixer Upper.” The model understands that “Needs TLC,” “Contractor Special,” and “Blank Canvas” all share a similar vector space.

This allows for “Fuzzy Intent” matching. The distance between the user’s query vector and the document’s vector is calculated (often using Cosine Similarity), allowing the system to return results that are conceptually relevant even if they don’t share a single keyword.

Case Study: Vertical Search Applications

We are seeing this deployed live in industries that rely on visual and descriptive data.

Take Deli, a new AI-driven real estate platform. Instead of forcing users to check boxes for “Pool: Yes/No,” it allows for natural language queries like “Backyard that feels like a resort.” Behind the scenes, the system isn’t filtering columns. It analyzes the semantic weight of listing descriptions and, in some cases, computer vision tags from property photos, to map “resort” to concepts like “palm trees,” “infinity pool,” “cabana,” and “lush landscaping.”

This reduces the “Zero Results” rate significantly. By bridging the gap between how users talk and how databases store data, we are seeing a massive increase in query completion and user engagement.

The Challenge of Hybrid Search

The future, however, isn’t pure vector search. The challenge for data scientists is building Hybrid Search architectures. Sometimes, a user wants “fuzzy” vibes (Semantic), but “hard” constraints (SQL).

  • Query: “Cozy cottage under $500k.”
  • Constraint: Price < $500,000 (Hard Filter).
  • Vector: “Cozy cottage” (Semantic Match).

“Balancing pre-filtering and post-filtering retrieval methods is currently one of the most active areas of research in search engineering.”

For data scientists working in e-commerce or property listing platforms, the era of strict keyword matching is ending. The ability to interpret intent via vector embeddings is not just a UX improvement; it is a fundamental shift in how we structure our data pipelines.