apache / apache/sedona-db

Remove scalar subquery physical expression error where it drops metadata

Open
#1,231 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
503
Forks
61
Avg merge
2d 5h
Merged PRs (30d)
91

Description

In the 54.1 update I had to set a configuration value to get tests to pass. I'm not sure if we can work around this or whether we have to wait for it to get fixed upstream, but I'd like to track this here because we'll want to remove it eventually to get better subquery evaluation. The usptream issue is https://github.com/apache/datafusion/issues/24933 ; the 54 update PR is https://github.com/apache/sedona-db/pull/1226 .

Contributor guide

Open the contributing guide

Research direction

Start by reading the Apache DataFusion issue #24933 and the Sedona DB 54 update PR #1226 to identify the configuration workaround and the scalar subquery metadata error. Done means the workaround can be removed while the tests still pass and subquery evaluation improves, or the upstream fix is incorporated when available.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.