Skip to content

Commit 9a6c06a

Browse files
committed
Trim duplicated inline comment on wildcard-table check
The inline block repeated the method-level Javadoc rationale for why vectorSearch() targets a single concrete index. Collapse to a one-line reference so readers do not see the same reasoning twice. No functional change. Signed-off-by: Eric Wei <mengwei.eric@gmail.com>
1 parent b2527e5 commit 9a6c06a

1 file changed

Lines changed: 2 additions & 5 deletions

File tree

opensearch/src/main/java/org/opensearch/sql/opensearch/storage/VectorSearchTableFunctionImplementation.java

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -203,11 +203,8 @@ private void validateNamedArgs() {
203203
* its own error message.
204204
*/
205205
private void validateTableName(String tableName) {
206-
// Flag wildcard and multi-target patterns with a dedicated message before the generic
207-
// character-class check, so users get an actionable hint instead of "must contain only
208-
// alphanumeric characters, dots, ...". vectorSearch() targets a single index because
209-
// top-k semantics, dimension checks, and the embedded filter JSON are not defined across
210-
// heterogeneous shards.
206+
// Dedicated error for fan-out patterns ('*' and ',') before the generic regex; see Javadoc
207+
// for why vectorSearch() targets a single index.
211208
if (tableName.indexOf('*') >= 0 || tableName.indexOf(',') >= 0) {
212209
throw new ExpressionEvaluationException(
213210
String.format(

0 commit comments

Comments
 (0)