rahil-c opened a new pull request, #18432:
URL: https://github.com/apache/hudi/pull/18432

   Implements a new Spark TVF `hudi_vector_search` that performs exact 
nearest-neighbor search over embeddings stored in a Hudi table using 
brute-force KNN, without requiring a persistent vector index.
   
   New files:
   - HoodieVectorSearchTableValuedFunction: unresolved logical node holding raw 
args; parses single-query (table, col, ARRAY(...), k [, metric]) and 
batch-query (corpus, col, query_table, col, k [, metric]) modes; supports 
cosine, l2/euclidean, dot_product distance metrics.
   - HoodieVectorSearchPlanBuilder: builds the execution plan — single-query 
mode uses withColumn + orderBy + limit(k); batch-query mode uses 
crossJoin(broadcast(queries)) + window rank per _query_id; handles 
Float/Double/Byte embedding types via cast to Double before UDF. Fixes 
cross-join column ambiguity when corpus and query share column names by 
renaming clashing query columns to _query_<colname> before the join.
   
   Modified files:
   - TableValuedFunctions: registers hudi_vector_search alongside existing Hudi 
TVFs so all Spark adapters (3.3/3.4/3.5/4.0) inject it via 
SparkSessionExtensions.
   - HoodieSparkBaseAnalysis (ResolveReferences): resolves 
HoodieVectorSearchTableValuedFunction — evaluates the query vector constant at 
analysis time, resolves table by name or path, delegates to 
HoodieVectorSearchPlanBuilder.
   - TestHoodieVectorSearchFunction: end-to-end tests covering single/batch 
query modes, all three distance metrics, DataFrame API, path-based and 
view-based resolution, Float/Double embedding types, MOR tables, composability 
(WHERE, subqueries), error handling, exact distance verification, and 
same-column-name batch query regression test.
   
   ### Describe the issue this Pull Request addresses
   
   <!-- Either describe the issue inline here with motivation behind the 
changes 
        (or) link to an issue by including `Closes #<issue-number>` for 
context. 
        If this PR includes changes to the storage format, public APIs,
        or has breaking changes, use `!` (e.g., feat!: ...) -->
   
   ### Summary and Changelog
   
   <!-- Short, plain-English summary of what users gain or what changed in 
behavior.
        Followed by a detailed log of all the changes. Highlight if any code 
was copied. -->
   
   ### Impact
   
   <!-- Describe any public API or user-facing feature change or any 
performance impact. -->
   
   ### Risk Level
   
   <!-- Accepted values: none, low, medium or high. Other than `none`, explain 
the risk.
        If medium or high, explain what verification was done to mitigate the 
risks. -->
   
   ### Documentation Update
   
   <!-- Describe any necessary documentation update if there is any new 
feature, config, or user-facing change. If not, put "none".
   
   - The config description must be updated if new configs are added or the 
default value of the configs are changed.
   - Any new feature or user-facing change requires updating the Hudi website. 
Please follow the 
     [instruction](https://hudi.apache.org/contribute/developer-setup#website) 
to make changes to the website. -->
   
   ### Contributor's checklist
   
   - [ ] Read through [contributor's 
guide](https://hudi.apache.org/contribute/how-to-contribute)
   - [ ] Enough context is provided in the sections above
   - [ ] Adequate tests were added if applicable
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to