opensearch-project / opensearch-project/sql-jdbc
[BUG] JDBC version is hardcoded in multiple places
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
What is the bug?
JDBC version is hardcoded in multiple places.
How can one reproduce the bug?
Steps to reproduce the behavior:
- Go to https://github.com/opensearch-project/sql/blob/2.x/sql-jdbc/src/main/java/org/opensearch/jdbc/internal/Version.java
- Go to https://github.com/opensearch-project/sql/blob/2.x/sql-jdbc/build.gradle
- See that they each have hardcoded versions for the jdbc driver
What is the expected behavior?
One should use the other's version in order to avoid version mismatch occurrences.
What is your host/environment?
- OS: macOS
- Version OpenSearch 2.4
- Plugins
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the JDBC version declarations in sql-jdbc/src/main/java/org/opensearch/jdbc/internal/Version.java and sql-jdbc/build.gradle. Start by tracing how each value is used, then consolidate them so the driver version cannot diverge. Done means both places obtain the same version and the JDBC build remains reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- database
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100