Skip to content

Commit 2c28a86

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 ca6da43 commit 2c28a86

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
@@ -234,11 +234,8 @@ private void validateNamedArgs() {
234234
* its own error message.
235235
*/
236236
private void validateTableName(String tableName) {
237-
// Flag wildcard and multi-target patterns with a dedicated message before the generic
238-
// character-class check, so users get an actionable hint instead of "must contain only
239-
// alphanumeric characters, dots, ...". vectorSearch() targets a single index because
240-
// top-k semantics, dimension checks, and the embedded filter JSON are not defined across
241-
// heterogeneous shards.
237+
// Dedicated error for fan-out patterns ('*' and ',') before the generic regex; see Javadoc
238+
// for why vectorSearch() targets a single index.
242239
if (tableName.indexOf('*') >= 0 || tableName.indexOf(',') >= 0) {
243240
throw new ExpressionEvaluationException(
244241
String.format(

0 commit comments

Comments
 (0)