Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
milvus
milvus
提交
b70665ed
M
milvus
项目概览
milvus
/
milvus
大约 1 年 前同步成功
通知
261
Star
22476
Fork
2472
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
DevOps
流水线
流水线任务
计划
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
M
milvus
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
DevOps
DevOps
流水线
流水线任务
计划
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
流水线任务
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
未验证
提交
b70665ed
编写于
9月 27, 2021
作者:
C
cai.zhang
提交者:
GitHub
9月 27, 2021
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Add comment for index interface (#8712)
Signed-off-by:
N
cai.zhang
<
cai.zhang@zilliz.com
>
上级
745221e8
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
13 addition
and
0 deletion
+13
-0
internal/types/types.go
internal/types/types.go
+13
-0
未找到文件。
internal/types/types.go
浏览文件 @
b70665ed
...
@@ -86,7 +86,10 @@ type IndexNode interface {
...
@@ -86,7 +86,10 @@ type IndexNode interface {
Component
Component
TimeTickProvider
TimeTickProvider
// CreateIndex receives request from IndexCoordinator to build an index.
// Index building is asynchronous, so when an index building request comes, IndexNode records the task and returns.
CreateIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
CreateIndexRequest
)
(
*
commonpb
.
Status
,
error
)
CreateIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
CreateIndexRequest
)
(
*
commonpb
.
Status
,
error
)
// GetMetrics gets the metrics about IndexNode.
GetMetrics
(
ctx
context
.
Context
,
req
*
milvuspb
.
GetMetricsRequest
)
(
*
milvuspb
.
GetMetricsResponse
,
error
)
GetMetrics
(
ctx
context
.
Context
,
req
*
milvuspb
.
GetMetricsRequest
)
(
*
milvuspb
.
GetMetricsResponse
,
error
)
}
}
...
@@ -94,10 +97,20 @@ type IndexCoord interface {
...
@@ -94,10 +97,20 @@ type IndexCoord interface {
Component
Component
TimeTickProvider
TimeTickProvider
// BuildIndex receives request from RootCoordinator to build an index.
// Index building is asynchronous, so when an index building request comes, an IndexBuildID is assigned to the task and
// the task is recorded in Meta. The background process assignTaskLoop will find this task and assign it to IndexNode for
// execution.
BuildIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
BuildIndexRequest
)
(
*
indexpb
.
BuildIndexResponse
,
error
)
BuildIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
BuildIndexRequest
)
(
*
indexpb
.
BuildIndexResponse
,
error
)
// DropIndex deletes indexes based on IndexID. One IndexID corresponds to the index of an entire column. A column is
// divided into many segments, and each segment corresponds to an IndexBuildID. IndexCoord uses IndexBuildID to record
// index tasks. Therefore, when DropIndex is called, delete all tasks corresponding to IndexBuildID corresponding to IndexID.
DropIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
DropIndexRequest
)
(
*
commonpb
.
Status
,
error
)
DropIndex
(
ctx
context
.
Context
,
req
*
indexpb
.
DropIndexRequest
)
(
*
commonpb
.
Status
,
error
)
// GetIndexStates gets the index states of the IndexBuildIDs in the request from RootCoordinator.
GetIndexStates
(
ctx
context
.
Context
,
req
*
indexpb
.
GetIndexStatesRequest
)
(
*
indexpb
.
GetIndexStatesResponse
,
error
)
GetIndexStates
(
ctx
context
.
Context
,
req
*
indexpb
.
GetIndexStatesRequest
)
(
*
indexpb
.
GetIndexStatesResponse
,
error
)
// GetIndexFilePaths gets the index files of the IndexBuildIDs in the request from RootCoordinator.
GetIndexFilePaths
(
ctx
context
.
Context
,
req
*
indexpb
.
GetIndexFilePathsRequest
)
(
*
indexpb
.
GetIndexFilePathsResponse
,
error
)
GetIndexFilePaths
(
ctx
context
.
Context
,
req
*
indexpb
.
GetIndexFilePathsRequest
)
(
*
indexpb
.
GetIndexFilePathsResponse
,
error
)
// GetMetrics gets the metrics about IndexCoord.
GetMetrics
(
ctx
context
.
Context
,
req
*
milvuspb
.
GetMetricsRequest
)
(
*
milvuspb
.
GetMetricsResponse
,
error
)
GetMetrics
(
ctx
context
.
Context
,
req
*
milvuspb
.
GetMetricsRequest
)
(
*
milvuspb
.
GetMetricsResponse
,
error
)
}
}
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录