spring-projects / spring-projects/spring-batch
Azure performance recomendation for Azure-SQL-Server
Open
Nobody has claimed this yet.
status: waiting-for-triage
type: feature
- Dominant language
- Java
- Stars
- 3k
- Forks
- 2.5k
- Avg merge
- 6d 53m
- Merged PRs (30d)
- 3
Description
We run Spring Batch 5.2.3 in a Azure Cloud with a Azure SQL Server. We use Spring Batch heavily. Azure advice us to create some Index.
You may consider this Input to create the requested Index.
Details
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
Review the attached Azure SQL Server recommendations and the listed columns first; the issue names no source files, tests, or entry points. Trace where Spring Batch defines or uses these metadata fields, then determine which requested indexes are appropriate and how to validate them. Done means the index changes and their expected performance impact are agreed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java, spring, sql
- Domain
- backend, databases, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100