confluentinc/ksql

Make `key` are reserved key word

Open

#6,896 创建于 2021年1月25日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)Java (5,739 star) (1,048 fork)batch import
enhancementfix-it-weekgood first issuestreaming-engine

描述

Atm, key is not a reserved key word in ksqlDB. Thus users could use it as a name for streams/tables/columns etc. We should add key as a reserved key word though to make sure we can use it if we evolve the language further.

贡献者指南

技术栈
javasqlkafka
领域
backenddatabase
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Basic knowledge of ksqlDB SQL syntaxUnderstanding of parser generators (e.g., ANTLR)Java development experience
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Look into the ksqlDB grammar file, likely a .g4 file in the parser module (e.g., src/main/antlr4/io/confluent/ksql/parser/), to see how other reserved keywords are defined. Add 'key' to the list of reserved keywords. Ensure that existing queries using 'key' as an identifier are properly handled or deprecated. The issue has no comments or PRs, so the implementation is open.