forked from IGinX-THU/IGinX
-
Notifications
You must be signed in to change notification settings - Fork 0
Feat(core, dataSources): show columns #148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
RemHero
wants to merge
156
commits into
main
Choose a base branch
from
feat_show_columns_prefix_filter_push_down_test
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
使项目版本切换更便捷。 移除了下面模块对特定版本的依赖 a. 测试 @RemHero b. docker 添加了一个 github workflow 用来切换版本
Co-authored-by: zhuyuqing <8178047+zhuyuqing@users.noreply.github.com>
The key column in previous downsample query result is confusing. It refers to the start of a window in such results, while user would assume it is a key for a record. Also, user should be able to slice windows based on queried data, instead of specifying key range. fix Add two columns: window_start and window_end to avoid misunderstanding. Adjust downsample sql statement SQL adjust Allow user to use: SELECT <expression> (, <expression>)* FROM prefixPath <whereClause>? <downsamplingClause>? <downsamplingClause>: OVER WINDOW LEFT_BRACKET SIZE DURATION (IN <timeInterval>)? (SLIDE DURATION)? RIGHT_BRACKET; to generate windows according to queried data. doc:https://oxlh5mrwi0.feishu.cn/wiki/BUerw0yvQiGBgOkz6YjcfbXInvd
配置方法 Mongodb 使用 uri 对连接参数进行详细配置,包括鉴权机制,相关语法参见 Mongodb 文档 Redis 使用 username 和 password 两个参数配置用户名和参数,若不设置该选项,则不使用鉴权。
What's wrong? [Relational storage engine] Querying non-existing path prefix in dummy relational engine would cause exception, because the engine tries to connect to a database that does not exist. Fix Query infomation about databases before making connection.
This reverts commit 7832a82.
IGinX-THU#398) User can alter the params of read-only dummy storage engine. The HAS_DATA & IS_READ_ONLY attributes cannot be modified. SQL ALTER STORAGEENGINE <engine_id> WITH PARAMS "(<param_key>:<param_value>,?)+"; example: alter storageengine 2 with params "dummy_dir:test/new_data"; ——简化实现,后续随节点移除、容错能力的增强,需要相应调整实现 同时,按需相应调整测试脚本目录结构
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.