apache / apache/amoro

[Bug]: Partition filter does not work

Open
#4,122 2 comments 0 reactions 0 assignees View on GitHub
stale type:bug
Dominant language
Java
Stars
1.2k
Forks
395
Avg merge
4d 10h
Merged PRs (30d)
33

Description

### What happened?

The field `partitions` in `org.apache.amoro.optimizing.plan.AbstractOptimizingEvaluator.PendingInput` is marked as "@JsonIgnore"

Image

When `partitions` is set into the table runtime and subsequently retrieved while in the `planning` state via the TableRuntimeStore, `partitions` loss occurs:

Image

Image

Image

### Affects Versions

master

### What table formats are you seeing the problem on?

_No response_

### What engines are you seeing the problem on?

_No response_

### How to reproduce

_No response_

### Relevant log output

```shell

```

### Anything else

_No response_

### Are you willing to submit a PR?

- [x] Yes I am willing to submit a PR!

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Contributor guide

Open the contributing guide

Research direction

Start at org.apache.amoro.optimizing.plan.AbstractOptimizingEvaluator.PendingInput and inspect how the partitions field is serialized before TableRuntimeStore retrieval in the planning state. Verify that a partition filter survives the table-runtime round trip and is available after retrieval; add regression coverage if the surrounding code provides a test entry point.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, data-engineering
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.