danny0405 commented on code in PR #19613:
URL: https://github.com/apache/hudi/pull/19613#discussion_r3789249627


##########
rfc/rfc-full-text-search/rfc-full-text-search.md:
##########
@@ -0,0 +1,891 @@
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+# RFC: Hudi Full-Text Search Index
+
+## Proposers
+
+- @danny0405
+
+## Approvers
+
+- TBD
+
+## Status
+
+Issue: TBD
+
+> This proposal intentionally does not claim an RFC number. The number and
+> catalog entry will be reserved through the separate RFC-number process.
+
+## Abstract
+
+This RFC proposes a full-text index for Apache Hudi. It supports token, phrase,
+and multi-column search over string columns, exposes standard predicates 
through
+Spark SQL, and offers a Lance-style direct table API through Hudi RS Python.

Review Comment:
   Addressed. The RFC now explains that the design draws from Lucene, 
Elasticsearch/OpenSearch, Tantivy, and Lance, and links their primary 
specifications or documentation. Hybrid text/vector retrieval is identified as 
a future user benefit but remains outside this RFC.



-- 
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