spring-projects / spring-projects/spring-batch

Flexible meta-data table names

Open
#4,902 1 comment 9 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

has: votes in: core type: feature
Dominant language
Java
Stars
3k
Forks
2.5k
Avg merge
6d 53m
Merged PRs (30d)
3

Description

Expected Behavior

I would like to suggest adding support for customizing meta table names and their case (upper/lower) directly through configuration in Spring Batch. I believe this feature would help users adapt Spring Batch more easily to various database environments and organizational naming conventions.

Example:

spring:
  batch:
    jdbc:
      meta-table-map:
        BATCH_JOB_INSTANCE: myapp_job_instance
        BATCH_JOB_EXECUTION: myapp_job_execution
      table-case: lower    # default: upper

Context

At the moment, only the table prefix can be configured, and there is no way to fully customize meta table names or their case through configuration. This can cause difficulties with case-sensitive databases or in organizations that require specific naming standards. Providing a way to directly map table names and set their case would make configuration much more flexible and user-friendly.

Contribution

If the team agrees that this would be a valuable improvement, I would be very happy to work on the implementation and contribute a pull request. Of course, I’m open to any feedback or suggestions you may have about the approach.

Thank you very much for your time and consideration. I look forward to your thoughts!

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 reviewing Spring Batch's existing table-prefix configuration and metadata table naming behavior. Trace how the configured prefix reaches the metadata schema and database operations, then define configuration handling for explicit table mappings and case selection. Done means the requested names and case can be configured consistently across the metadata tables.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
database
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.