Search by Name
When you need speed and precision, Search by Name is your most direct tool. It is designed for scenarios where you know the name (or part of the name) of an asset and need a predictable, unambiguous result. This mode bypasses any AI interpretation to deliver the fastest and most deterministic search experience possible.
Key Characteristics
Search by Name operates on a simple principle: what you type is what you get. Its behavior is defined by a few core characteristics:
- Direct String Matching: The engine matches the text you enter directly against the names and identifiers of your data assets.
- Case-Insensitive: It treats uppercase and lowercase letters the same. A search for
Customer_Data
andcustomer_data
will return the exact same results. - Partial Matching: You don’t need the full name. A query for a substring like
_prod_
will find all assets containing that fragment, such asfct_orders_prod_daily
. - Speed and Efficiency: Because it avoids complex processing, this is the fastest search mode available, providing instant results.
When to Use Search by Name
This mode excels in situations where certainty and predictability are paramount.
Use Case | Description |
---|---|
Direct Navigation | You know the exact name of a table, like dim_user_profiles , and want to navigate straight to its documentation without ambiguity. |
Exploring Naming Conventions | Your organization uses consistent prefixes, like fin_ for finance data. A partial search for fin_ instantly reveals all related assets, helping you explore a specific domain. |
Automation and Scripting | Scripts, API calls, and data pipelines require stable, predictable results. Search by Name guarantees that a query will always return the same asset, making it safe for machine-to-machine communication. |
Practical Examples
Example 1: Finding a Specific Data Product
A data analyst needs to find the official sales analytics product.
- Query:
"sales_analytics_product"
- Result: The single Data Product with the qualified name
sales_analytics_product
.
Example 2: Discovering All Customer-Related Schemas
A developer wants to see all schemas related to customer data.
- Query:
"customer"
- Results: A list of all schemas containing the word “customer,” such as:
customer_profile_schema
customer_transaction_schema
customer_analytics_schema
Example 3: Locating a Specific Attribute
A report builder is looking for a revenue field.
- Query:
"revenue"
- Results: A list of all attributes containing the word “revenue,” including:
revenue_amount
total_revenue
projected_revenue
Strengths and Trade-offs
Search by Name is the bedrock of Blindata’s search functionality. It provides a reliable baseline for exact lookups, ensuring that discovery can be both fast and predictable.
Strengths | Limitations |
---|---|
Speed: The fastest search mode. | No Typo Correction: Misspellings will yield no results. |
Precision: Zero ambiguity in results. | No Synonym Recognition: Won’t find “sales” if you search for “revenue.” |
Predictability: Ideal for automation. | Requires Prior Knowledge: The user must know some part of the asset’s name. |
By providing a reliable foundation for exact lookups, it ensures that whether you are an analyst navigating the UI or a system executing an automated query, you can find what you’re looking for instantly.