Skip to content

Track native SQL support gaps and parity-harness follow-ups from the September audit #110

Description

@liuyongvs

Objective

Track the native support and test-infrastructure gaps identified by the SQL parity audit at main ebe550c69122909cd08fca8ee89380478a92cc5c, using released Apache Flink 2.2.1 as the oracle. Prioritize STRING/VARCHAR, DECIMAL, INT/BIGINT, TIMESTAMP and TIMESTAMP_LTZ; floating-point-only work is lower priority.

Evidence and scope

  • 51 query records contain explicit planner fallback reasons. A query can have several blockers, so one completed feature does not necessarily unlock a whole query.
  • 79 further zero-substitution records optimize to TableSourceScan alone after fixture/sink adaptation. They are not 79 missing compute operators and do not prove original connector IO or recovery contracts.
  • 53 queries fail on the host before native comparison: 32 missing functions, 3 missing tables, 6 FIRST_VALUE signature differences, 4 temporal signatures, 2 implicit conversions, 2 streaming shape/mode restrictions, 2 error-producing inputs and 2 JSON RETURNING runtime exceptions.
  • One of the 51 planner-rejected records also has an unexpanded JSON-path test parameter. Track its intended variants through the harness ticket rather than counting it as complete path coverage.
  • SQL examples in the child tickets are shapes for minimized regressions, not claims that every example has independently been executed. Preserve full-query evidence and assert native substitutions in new tests.

The 25 work items below comprise 21 feature-support tickets and 4 test/investigation tickets. They do not create native semantics for SQL that the released host cannot execute.

P1: common strings, exact numerics and temporal types

P2: remaining expressions and collection/JSON support

P2: aggregates and relational plan shapes

P3: floating-point work

Test setup and investigations

Existing related work

The implementations for #81, #93, #95, #97, #106, #107 and #123 shipped with the integrated stack in PR #150. The harness for #106/#107 uses a portable corpus derived from the public issues; the original independently produced September audit corpus was unavailable, so this is not a claim to have replayed it. The integrated tree passed all required CI and unchanged upstream suites before merging.

Completion criteria

Each child issue should link its implementation and parity evidence, identify actual native execution versus fallback, update the relevant documentation and close when its scoped work ships. The harness must account separately for host setup errors, expected exceptions, scan-only queries, explicit fallback and native result/changelog parity. Reassess remaining blockers after each implementation instead of assuming the original query counts are additive.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions