bytedance / bytedance/videx

Self-implemented Videx-stat-server With SpringBoot

Open
#8 7 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
149
Forks
27
PR merge metrics
No merged PRs in 30d

Description

HI, 我目前想基于springboot 实现Videx-stat-server, 查看接口/ask_videx 发现optimizer 层主要通过Http 获取如下几个统计信息:
![Image](https://github.com/user-attachments/assets/88b8df08-c4d8-4535-8c5d-e7ecca311fa8)

对于这几个统计方法的描述不知道我理解的对不对?
1. table_model.scan_time: 实际计算的是如果全表扫描,花费的代价是多少
2. table_model.get_memory_buffer_size:这个很直白, 获取memory_buffer_size大小,估计是用来评估JOIN 或者创建零时表的成本
3. table_model.records_in_range:这个应该是核心,根据条件和我们的ndv+直方图,返回预估满足条件的行数
4. table_model.info_low:返回表的一些基础信息

Videx 从server获取信息是不是只需要这几个信息?这对我springboot实现很重要,盼回复!谢谢:)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the /ask_videx endpoint and the optimizer code that calls table_model.scan_time, get_memory_buffer_size, records_in_range, and info_low. Trace the server-side contract and compare it with the proposed SpringBoot implementation. The issue has no defined implementation scope or acceptance criteria; done would require a confirmed protocol and documented response requirements.

Written by the indexing model from the issue text.

Assessment

Tech stack
mysql, python, spring-boot
Domain
api, backend, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.