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.