oceanbase / oceanbase/seekdb

[Question]: SQL 错误 [4016] [HY000]: Internal error

Open
#789 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: question
Dominant language
C++
Stars
2.9k
Forks
339
Avg merge
1d 19h
Merged PRs (30d)
52

Description

1、The prepare sql is :
CALL DBMS_AI_SERVICE.CREATE_AI_MODEL(
'qwen8B-embedding',
'{
"type": "dense_embedding",
"model_name": "qwen8B-embedding"
}'
);

CALL DBMS_AI_SERVICE.CREATE_AI_MODEL_ENDPOINT('my_endpoint', '{
"ai_model_name": "qwen8B-embedding",
"url": "http://20.17.125.45:8002/v1/embeddings",
"access_key": "xxxx",
"provider": "aliyun-openAI"
}');

CREATE TABLE test.articles1 (
id INT AUTO_INCREMENT PRIMARY KEY,
title VARCHAR(255),
content TEXT,
embedding VECTOR(4096),
VECTOR INDEX vector_id(embedding)
WITH (
distance=l2,
lib=vsag,
type=hnsw
)
);

INSERT INTO test.articles1 (title, content, embedding)
VALUES (
'OceanBase SeekDB 介绍',
'SeekDB 是一款 AI 原生数据库,支持混合搜索。',
AI_EMBED('qwen8B-embedding', 'SeekDB 是一款 AI 原生数据库,支持混合搜索。')
);

INSERT INTO test.articles1 (title, content, embedding)
VALUES (
'OceanBase mysqlDB 介绍',
'Mysql是一款结构化数据存储的数据库,支持标准sql的查询。',
AI_EMBED('qwen8B-embedding', 'Mysql是一款结构化数据存储的数据库,支持标准sql的查询。')
);

2、when I execute the following sql:
SELECT
id,
title,
content
FROM test.articles1
ORDER BY semantic_vector_distance(embedding, AI_EMBED('qwen8B-embedding', 'AI数据库'))
APPROXIMATE
limit 10

3、The error is :
SQL 错误 [4016] [HY000]: Internal error

1、Is there has detail log to see the internal error ?
2、what is the error of sql to cause this problem?
Thanks a lot.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the CREATE_AI_MODEL, CREATE_AI_MODEL_ENDPOINT, table creation, INSERT, and semantic_vector_distance SELECT statements shown in the issue. Check the available database error log or diagnostic output for SQL error 4016, then isolate which statement triggers it. Done means identifying the failing SQL or configuration and documenting the relevant diagnostic details and correction.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
databases, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.