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

[Bug] ResultSetMetaData.getCatalogName throws IndexOutOfBoundsException instead of SQLException for out-of-range columns

Open Beginner friendly
#18,241 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
java
Domain
databases

Research direction

Start in the class containing IoTDBResultMetadata.getCatalogName(int) and compare it with the seven sibling ResultSetMetaData accessors that call checkColumnIndex(column) first. Reproduce the issue with getCatalogName(0) or another out-of-range column, then verify that invalid indexes consistently produce SQLException rather than IndexOutOfBoundsException.

Written by the indexing model from the issue text.

Description

Search before asking
  • I searched in the issues and found nothing similar.
Version

master (2.0.x). The affected code is also present in released 2.0.x versions.

Describe the bug and provide the minimal reproduce step

IoTDBResultMetadata.getCatalogName(int column) reads columnInfoList.get(column - 1) before its range check runs, so an out-of-range column index throws a raw IndexOutOfBoundsException instead of the SQLException required by the ResultSetMetaData contract. The subsequent range check (if (column < 1 || column > columnInfoList.size())) is therefore unreachable for an out-of-range column. The seven sibling ResultSetMetaData accessors in the same class all call checkColumnIndex(column) first; getCatalogName is the only one missing that guard.

Minimal reproduce step:

  1. Obtain a ResultSetMetaData from any (non-empty) query result.
  2. Call metaData.getCatalogName(0) (or any column index <= 0 or > column count).
  3. A raw IndexOutOfBoundsException is thrown instead of a SQLException.
What did you expect to see?

getCatalogName throws a SQLException for an out-of-range column index, consistent with the ResultSetMetaData contract and with the sibling accessors.

What did you see instead?

A raw java.lang.IndexOutOfBoundsException from columnInfoList.get(column - 1).

Anything else?

The fix is to call checkColumnIndex(column) first, as the sibling accessors already do — it throws SQLException on column <= 0, column > size, and an empty column list. I'd like to work on this and will open a PR.

Are you willing to submit a PR?
  • I'm willing to submit a PR!
Dominant language
Java
Stars
6.4k
Forks
1.2k
Avg merge
1d 8h
Merged PRs (30d)
129

Contributor guide

Open the contributing guide

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/iotdb

All issues in apache/iotdb

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.