crate/crate

Support additional units for `INTERVAL` types

Open

#11,490 建立於 2021年6月17日

在 GitHub 查看
 (11 留言) (2 反應) (1 負責人)Java (3,863 star) (545 fork)batch import
complexity: no estimatefeature: sql: type systemgood first issueneeds concrete use-case

描述

Use case:

  • Compatibility with PostgreSQL
  • Time-series applications

Feature description:

the CrateDB INTERVAL data type does not currently support the PostgreSQL input units MILLENNIUM, CENTURY, DECADE, MILLISECOND, or MICROSECOND. the larger units might not be so useful for most CrateDB use-cases, but MILLISECOND and MICROSECOND appear to be good candidates for use with time-series applications

NOTE: this feature request was spun out of my work revamping the data types docs

貢獻者指南

技術棧
javasql
領域
backenddatabase
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
JavaSQLDatabase architecture
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
10
研究方向
The issue requires adding support for MILLISECOND, MICROSECOND, and possibly larger units to the INTERVAL type. Start by examining the interval parsing logic in the CrateDB codebase, likely in the `io.crate.types` package. The PR #11418 provides context from documentation revamp. Review PostgreSQL documentation for input format and ensure compatibility.