<div id="readability-page-1" class="page"><div>
 <a href="/m/category/JAVA/spring-batch">JAVA/spring-batch</a><h3>정수원님 Springbatch 강의 재정리(8~10강)</h3>
 </div><cite>Berno</cite>
 2023. 7. 19. 16:21
 <div>
 <h3 data-ke-size="size23">0. 이 글의 목적</h3>
기존 정수원 님의 강의는 SpringBoot 2.x, Spring-batch 4.x 버전을 사용 중이었으나 최신은 SpringBoot 3.x, Spring-batch 5.x 버전이기에 나는 최신으로 하면서 동작하지 않는 코드와 최신 방법으로 코드를 변형하기 위함


<h3 data-ke-size="size23">1. Spring Batch의 전략</h3>
하나의 Job이 존재하며 이 Job은 여러 Step으로 구성된다. 각 Step에서의 실제 수행은 tasklet에서 이루어진다.


<h3 data-ke-size="size23">2. 그러면 무엇이 바뀌었는가</h3>
우선 StepBuilderFactory와 JobBuilderFactory가 deprecated되었다.
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="1874" data-origin-height="1652">
 <span data-url="https://blog.kakaocdn.net/dn/co0G4C/btsogcCgt9Y/o3xR5ae4FkDAyy8NAYXaTK/img.png" data-lightbox="lightbox" data-alt="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration">
 <img src="https://blog.kakaocdn.net/dn/co0G4C/btsogcCgt9Y/o3xR5ae4FkDAyy8NAYXaTK/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1874" data-origin-height="1652">
 
 <figcaption>https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration</figcaption>
</figure>
이제 직접 JobBuilder와 StepBuilder를 구현해야 한다.
<pre id="code_1689748775461" data-ke-language="java" data-ke-type="codeblock"><code>//@EnableBatchProcessing
@Configuration
@RequiredArgsConstructor
public class HelloJobConfiguration extends DefaultBatchConfiguration {
 @Bean
 public Job job(JobRepository jobRepository, Step helloStep1, Step helloStep2) {
 return new JobBuilder("myJob", jobRepository)
 .start(helloStep1)
 .next(helloStep2)
 .build();
 }

 @Bean
 public Step helloStep1(JobRepository jobRepository, PlatformTransactionManager platformTransactionManager) {
 return new StepBuilder("helloStep1", jobRepository).tasklet(new Tasklet() {
 @Override
 public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
 System.out.println("======================");
 System.out.println(" &gt;&gt; Hello Spring Batch!!");
 System.out.println("======================");

 return RepeatStatus.FINISHED;
 }
 }, platformTransactionManager).build();
 }

 @Bean
 public Step helloStep2(JobRepository jobRepository, PlatformTransactionManager platformTransactionManager) {
 return new StepBuilder("helloStep2", jobRepository).tasklet((contribution, chunkContext) -&gt; {
 System.out.println("======================");
 System.out.println(" &gt;&gt;step2 was executed");
 System.out.println("======================");

 return RepeatStatus.FINISHED;
 }, platformTransactionManager).build();
 }

}</code></pre>
이 코드에서 job 메서드에 Step이 직접 파라미터로 들어가고 있다. 메서드 이름과 파라미터명이 동일하면 상관이 없지만 이 파라미터 이름을 메서드 이름과 맞춰주지 않으면 직접 Qualifier로 지정을 해줘야 한다.&nbsp;
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="1730" data-origin-height="603">
 
 <img src="https://blog.kakaocdn.net/dn/b68TwN/btsofqOAqOT/ePSx6mmNgFK7Gkkgqf8oX0/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1730" data-origin-height="603">
 
 
</figure>

그리고 나는 현재 @EnableBatchProcessing을 주석처리해 둔 상태이다. 그 이유는 DefaultBatchConfiguration을 상속받으면 사용하지 않아도 된다 나와있기 때문이다.
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="2088" data-origin-height="1650">
 <span data-url="https://blog.kakaocdn.net/dn/tLUW0/btsofsMmXv6/fxLuydGArbda2Wixd9WUak/img.png" data-lightbox="lightbox" data-alt="https://docs.spring.io/spring-batch/docs/current/reference/html/index-single.html#new-configuration-class">
 <img src="https://blog.kakaocdn.net/dn/tLUW0/btsofsMmXv6/fxLuydGArbda2Wixd9WUak/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="2088" data-origin-height="1650">
 
 <figcaption>https://docs.spring.io/spring-batch/docs/current/reference/html/index-single.html#new-configuration-class</figcaption>
</figure><figure data-ke-mobilestyle="widthOrigin" data-origin-width="1128" data-origin-height="408">
 
 <img src="https://blog.kakaocdn.net/dn/bKP8LP/btsofphSBwJ/wrKd7pkBxkUDEHo2zkgPL0/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1128" data-origin-height="408">
 
 
</figure>

문제는 저렇게 하는 경우 에러는 발생하지 않지만 수행이 되지 않는다. 무엇이 문제일까.
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="1456" data-origin-height="824">
 
 <img src="https://blog.kakaocdn.net/dn/X0Y7C/btsogch3mAk/2wJIu9kkEkLOMRB8nIP12K/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1456" data-origin-height="824">
 
 <figcaption>https://github.com/spring-projects/spring-boot/issues/33435</figcaption>
</figure><figure data-ke-mobilestyle="widthOrigin" data-origin-width="1612" data-origin-height="536">
 
 <img src="https://blog.kakaocdn.net/dn/mTFUT/btsoeJ2gKMR/7ex2rKdAmkJxIa1tWN7qc0/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1612" data-origin-height="536">
 
 <figcaption>https://www.baeldung.com/spring-boot-3-migration#spring-batch</figcaption>
</figure>

놀랍게도 spring boot3부터는 EnableBatchProcessing이나 DefaultBatchConfiguration을 사용하면 자동으로 수행하는 것을 막아둔 상태다.

그렇다면 선택지는 2개가 있다. DefaultBatchConfiguration상속을 제거하거나 Runner를 구현해야 한다. 나는 Runner를 구현했다.

이렇게 구현해서 사용하였다.
<pre id="code_1689749073036" data-ke-language="java" data-ke-type="codeblock"><code>@Component
public class BatchJobLauncher implements CommandLineRunner {

 @Autowired
 private JobLauncher jobLauncher;

 @Autowired
 private Job job;

 @Override
 public void run(String... args) throws Exception {
 JobExecution execution = jobLauncher.run(job, new JobParameters());
 System.out.println("Exit status :: " + execution.getStatus());
 }
}</code></pre>

아직 에러가 발생한다.
<pre id="code_1689750959175" data-ke-language="java" data-ke-type="codeblock"><code>Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
2023-07-19T14:34:11.640+09:00 ERROR 26798 --- [ main] o.s.boot.SpringApplication : Application run failed

java.lang.IllegalStateException: Failed to execute CommandLineRunner
	at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:774) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:755) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:319) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-3.1.1.jar:3.1.1]
	at com.example.springbatch.SpringBatchApplication.main(SpringBatchApplication.java:15) ~[main/:na]
Caused by: org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [SELECT JOB_INSTANCE_ID, JOB_NAME
FROM BATCH_JOB_INSTANCE
WHERE JOB_NAME = ?
 and JOB_KEY = ?]</code></pre>
스키마에 대한 설정이 부족했다. Spring Batch는 메타 데이터에 대한 저장을 위해 6개의 테이블을 필요로 하고 있다.
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="831" data-origin-height="679">
 <span data-url="https://blog.kakaocdn.net/dn/yxWYF/btsn89m93e0/KwJiU6lkRc6AfJMnc3sGpk/img.png" data-lightbox="lightbox" data-alt="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview">
 <img src="https://blog.kakaocdn.net/dn/yxWYF/btsn89m93e0/KwJiU6lkRc6AfJMnc3sGpk/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="831" data-origin-height="679">
 
 <figcaption>https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview</figcaption>
</figure>

다행히 이 모든 쿼리를 제공해주고 있다.
인텔리제이 기준 파일 검색으로 schema- 로 검색하여 본인의 db에 맞는 것으로 사용하면 된다.
<figure data-ke-mobilestyle="widthOrigin" data-origin-width="1730" data-origin-height="1795">
 
 <img src="https://blog.kakaocdn.net/dn/bEuKC3/btsn9Uwy6mz/GV6sIuvbOjOXMSfH9raFMK/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" width="699" height="725" data-origin-width="1730" data-origin-height="1795">
 
 
</figure>


테이블을 만들었으니 이제 진짜 실행해 보자.

<figure data-ke-mobilestyle="widthOrigin" data-origin-width="1646" data-origin-height="748">
 
 <img src="https://blog.kakaocdn.net/dn/t4UHi/btsoeAddms0/ycyMjlZFWFcc3e6IDcGZkK/img.png" onerror="this.onerror=null; this.src='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png'; this.srcset='//t1.daumcdn.net/tistory_admin/static/images/no-image-v1.png';" data-origin-width="1646" data-origin-height="748">
 
 
</figure>

잘된다.


<h3 data-ke-size="size23">3. 마무리</h3>
이제 다음 강의에서 spring batch 4로 되어있는 부분을 다시 5로 바꾸면서 알아갈 생각을 하니 벌써부터 블로그 글감이 떨어지지 않을 것 같아 행복하다.


출처 :
[1] : <a href="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration">https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration</a>
<figure id="og_1689751273856" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="object" data-og-title="Spring Batch 5.0 Migration Guide" data-og-description="Spring Batch is a framework for writing batch applications using Java and Spring - spring-projects/spring-batch" data-og-host="github.com" data-og-source-url="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration" data-og-url="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide" data-og-image="https://scrap.kakaocdn.net/dn/cJ6t2X/hyTmCSpLzO/i5NYrEJuGiBKfSrcSXMpXk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"><a href="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration" target="_blank" rel="noopener" data-source-url="https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration">

<div>
Spring Batch 5.0 Migration Guide
Spring Batch is a framework for writing batch applications using Java and Spring - spring-projects/spring-batch
github.com
</div>
</a><img src="https://scrap.kakaocdn.net/dn/cJ6t2X/hyTmCSpLzO/i5NYrEJuGiBKfSrcSXMpXk/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"></figure>
[2] : <a href="https://github.com/spring-projects/spring-boot/issues/33435">https://github.com/spring-projects/spring-boot/issues/33435</a>
<figure id="og_1689751275167" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="object" data-og-title="Remove @EnableBatchProcessing mentions in reference documentation for sliced tests and user configuration · Issue #33435 · spr" data-og-description="As of #32330, usage of @EnableBatchProcessing is now discouraged since this turns off the Spring Boot auto-configuration for Spring Batch. This annotation is still featured frequently in our own re..." data-og-host="github.com" data-og-source-url="https://github.com/spring-projects/spring-boot/issues/33435" data-og-url="https://github.com/spring-projects/spring-boot/issues/33435" data-og-image="https://scrap.kakaocdn.net/dn/HmzcP/hyTnNx1IPn/qG9NgJusMRm1AigTM9sCkK/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"><a href="https://github.com/spring-projects/spring-boot/issues/33435" target="_blank" rel="noopener" data-source-url="https://github.com/spring-projects/spring-boot/issues/33435">

<div>
Remove @EnableBatchProcessing mentions in reference documentation for sliced tests and user configuration · Issue #33435 · spr
As of #32330, usage of @EnableBatchProcessing is now discouraged since this turns off the Spring Boot auto-configuration for Spring Batch. This annotation is still featured frequently in our own re...
github.com
</div>
</a><img src="https://scrap.kakaocdn.net/dn/HmzcP/hyTnNx1IPn/qG9NgJusMRm1AigTM9sCkK/img.png?width=1200&amp;height=600&amp;face=0_0_1200_600"></figure>
[3] : <a href="https://www.baeldung.com/spring-boot-3-migration#spring-batch">https://www.baeldung.com/spring-boot-3-migration#spring-batch</a>
<a href="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview">[4] : https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview</a>
<figure id="og_1689751281365" contenteditable="false" data-ke-type="opengraph" data-ke-align="alignCenter" data-og-type="website" data-og-title="Meta-Data Schema" data-og-description="The Spring Batch Metadata tables closely match the domain objects that represent them in Java. For example, JobInstance, JobExecution, JobParameters, and StepExecution map to BATCH_JOB_INSTANCE, BATCH_JOB_EXECUTION, BATCH_JOB_EXECUTION_PARAMS, and BATCH_ST" data-og-host="docs.spring.io" data-og-source-url="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview" data-og-url="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview" data-og-image="https://scrap.kakaocdn.net/dn/c5Nt92/hyTmoNpECo/8ajgWLT4L0B7oYRPo6Lbl0/img.png?width=831&amp;height=679&amp;face=0_0_831_679"><a href="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview" target="_blank" rel="noopener" data-source-url="https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview">

<div>
Meta-Data Schema
The Spring Batch Metadata tables closely match the domain objects that represent them in Java. For example, JobInstance, JobExecution, JobParameters, and StepExecution map to BATCH_JOB_INSTANCE, BATCH_JOB_EXECUTION, BATCH_JOB_EXECUTION_PARAMS, and BATCH_ST
docs.spring.io
</div>
</a><img src="https://scrap.kakaocdn.net/dn/c5Nt92/hyTmoNpECo/8ajgWLT4L0B7oYRPo6Lbl0/img.png?width=831&amp;height=679&amp;face=0_0_831_679"></figure>

 
 
 </div></div>

흔한 컴공출신 개발자

bernoyoun

0. 이 글의 목적
기존 정수원 님의 강의는 SpringBoot 2.x, Spring-batch 4.x 버전을 사용 중이었으나 최신은 SpringBoot 3.x, Spring-batch 5.x 버전이기에 나는 최신으로 하면서 동작하지 않는 코드와 최신 방법으로 코드를 변형하기 위함
 
 
1. Spring Batch의 전략
하나의 Job이 존재하며 이 Job은 여러 Step으로 구성된다. 각 Step에서의 실제 수행은 tasklet에서 이루어진다.
 
 
2. 그러면 무엇이 바뀌었는가
우선 StepBuilderFactory와 JobBuilderFactory가 deprecated되었다.
이제 직접 JobBuilder와 StepBuilder를 구현해야 한다.
//@EnableBatchProcessing
@Configuration
@RequiredArgsConstructor
public class HelloJobConfiguration extends DefaultBatchConfiguration {
    @Bean
    public Job job(JobRepository jobRepository, Step helloStep1, Step helloStep2) {
        return new JobBuilder("myJob", jobRepository)
                .start(helloStep1)
                .next(helloStep2)
                .build();
    }
    @Bean
    public Step helloStep1(JobRepository jobRepository, PlatformTransactionManager platformTransactionManager) {
        return new StepBuilder("helloStep1", jobRepository).tasklet(new Tasklet() {
            @Override
            public RepeatStatus execute(StepContribution contribution, ChunkContext chunkContext) throws Exception {
                System.out.println("======================");
                System.out.println(" >> Hello Spring Batch!!");
                System.out.println("======================");
                return RepeatStatus.FINISHED;
            }
        }, platformTransactionManager).build();
    }
    @Bean
    public Step helloStep2(JobRepository jobRepository, PlatformTransactionManager platformTransactionManager) {
        return new StepBuilder("helloStep2", jobRepository).tasklet((contribution, chunkContext) -> {
            System.out.println("======================");
            System.out.println(" >>step2 was executed");
            System.out.println("======================");
            return RepeatStatus.FINISHED;
        }, platformTransactionManager).build();
    }
}
이 코드에서 job 메서드에 Step이 직접 파라미터로 들어가고 있다. 메서드 이름과 파라미터명이 동일하면 상관이 없지만 이 파라미터 이름을 메서드 이름과 맞춰주지 않으면 직접 Qualifier로 지정을 해줘야 한다. 
 
그리고 나는 현재 @EnableBatchProcessing을 주석처리해 둔 상태이다. 그 이유는 DefaultBatchConfiguration을 상속받으면 사용하지 않아도 된다 나와있기 때문이다.
 
문제는 저렇게 하는 경우 에러는 발생하지 않지만 수행이 되지 않는다. 무엇이 문제일까.
 
놀랍게도 spring boot3부터는 EnableBatchProcessing이나 DefaultBatchConfiguration을 사용하면 자동으로 수행하는 것을 막아둔 상태다.
 
그렇다면 선택지는 2개가 있다. DefaultBatchConfiguration상속을 제거하거나 Runner를 구현해야 한다. 나는 Runner를 구현했다.
 
이렇게 구현해서 사용하였다.
@Component
public class BatchJobLauncher implements CommandLineRunner {
    @Autowired
    private JobLauncher jobLauncher;
    @Autowired
    private Job job;
    @Override
    public void run(String... args) throws Exception {
        JobExecution execution = jobLauncher.run(job, new JobParameters());
        System.out.println("Exit status :: " + execution.getStatus());
    }
}
 
아직 에러가 발생한다.
Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled.
2023-07-19T14:34:11.640+09:00 ERROR 26798 --- [           main] o.s.boot.SpringApplication               : Application run failed
java.lang.IllegalStateException: Failed to execute CommandLineRunner
	at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:774) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:755) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:319) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1306) ~[spring-boot-3.1.1.jar:3.1.1]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1295) ~[spring-boot-3.1.1.jar:3.1.1]
	at com.example.springbatch.SpringBatchApplication.main(SpringBatchApplication.java:15) ~[main/:na]
Caused by: org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [SELECT JOB_INSTANCE_ID, JOB_NAME
FROM BATCH_JOB_INSTANCE
WHERE JOB_NAME = ?
 and JOB_KEY = ?]
스키마에 대한 설정이 부족했다. Spring Batch는 메타 데이터에 대한 저장을 위해 6개의 테이블을 필요로 하고 있다.
 
다행히 이 모든 쿼리를 제공해주고 있다.
인텔리제이 기준 파일 검색으로 schema- 로 검색하여 본인의 db에 맞는 것으로 사용하면 된다.
 
 
테이블을 만들었으니 이제 진짜 실행해 보자.
 
 
잘된다.
 
 
3. 마무리
이제 다음 강의에서 spring batch 4로 되어있는 부분을 다시 5로 바꾸면서 알아갈 생각을 하니 벌써부터 블로그 글감이 떨어지지 않을 것 같아 행복하다.
 
 
출처 :
[1] : https://github.com/spring-projects/spring-batch/wiki/Spring-Batch-5.0-Migration-Guide#jobbuilderfactory-and-stepbuilderfactory-bean-exposureconfiguration
[2] : https://github.com/spring-projects/spring-boot/issues/33435
[3] : https://www.baeldung.com/spring-boot-3-migration#spring-batch
[4] : https://docs.spring.io/spring-batch/docs/current/reference/html/schema-appendix.html#metaDataSchemaOverview

정수원님 Springbatch 강의 재정리(8~10강)

댓글