Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

REST Catalog alterTable silently reports success when the server returns a non-table/column 404

Open Beginner friendly
#10,267 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java
Domain
api, database

Research direction

Start at the REST Catalog alterTable entry point and inspect its NoSuchResourceException handling for 404 resource types beyond TABLE and COLUMN. Compare the analogous createBranch default branch mentioned in the issue. Done means an unmapped 404, such as a DATABASE not-found, no longer returns silent success; verify the concurrent-database-drop reproduction reports an error.

Written by the indexing model from the issue text.

Description

Search before asking
  • I searched in the issues and found no similar issues.
Paimon version

master (1.5-SNAPSHOT)

Compute Engine

Any engine using the REST Catalog.

Minimal reproduce step
  1. Use a REST catalog.
  2. Call alterTable(identifier, changes, ignoreIfNotExists = false) in a situation where the REST server answers with a 404 whose resource type is neither TABLE nor COLUMN, for example a DATABASE not-found because the table's database was concurrently dropped.
What doesn't meet your expectations?

alterTable returns normally and reports success even though the ALTER did not apply. The NoSuchResourceException handler only covers the TABLE and COLUMN resource types; for any other type it falls through the if/else-if chain and the method returns without error, so a failed alter is silently swallowed.

Anything else?

The sibling createBranch already rethrows in the analogous default branch of the same kind of dispatch. alterTable was the only one that let an unmapped 404 fall through to silent success.

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Dominant language
Java
Stars
3.4k
Forks
1.4k
Avg merge
1d 11h
Merged PRs (30d)
490

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/paimon

All issues in apache/paimon

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.