spring-projects / spring-projects/spring-boot

Create our own bindable properties objects for datasource binding

Open
#23,542 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: epic
Dominant language
Java
Stars
81.5k
Forks
42.7k
Avg merge
2d 4h
Merged PRs (30d)
65

Description

See #23436 for background. We think it's worth creating our own datasource properties objects (in the same way as we did for Flyway).

  • Hikari
  • Tomcat
  • DBCP2
  • Oracle UCP

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.

Research direction

Start by reading issue #23436 for the background and inspect the existing Flyway datasource properties implementation as the stated model. Then assess the binding requirements for Hikari, Tomcat, DBCP2, and Oracle UCP; done means each listed datasource has its own bindable properties object with appropriate coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, spring-boot
Domain
backend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.