Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEST: Feat not piped test #844

Merged
merged 1 commit into from
Dec 5, 2024
Merged

Conversation

cheesecrust
Copy link
Collaborator

@cheesecrust cheesecrust commented Dec 5, 2024

🔗 Related Issue

⌨️ What I did

  • 파이프 operation들에 대해서 파이프 연산이 아닌 경우에 동작을 테스트 하였습니다.

CollectionBulkInsertOperationImplasyncBopInsertBulk,
CollectionPipedInsertOperationImplasyncSopPipedInsertBulk,
CollectionPipedUpdateOperationImpl asyncBopPipedUpdateBulk

각각 위에 연산에 대하여 위 연산들을 실행하는 테스트 파일에 테스트를 추가한다.
시나리오는 아이템을 하나씩만 주어 파이프와 벌크 연산의 handleLine 에서 isNotPiped()를 테스트한다.
이때 연산이 성공하는 경우와 연산이 실패하는 경우를 모두 다룬다.

errorList = future.get(5000L,
TimeUnit.MILLISECONDS);
assertEquals(1, errorList.size());
} catch (TimeoutException e) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

전체적으로 timeout exception은 catch하지 않아도 될 것 같습니다.

try {
// UPDATE
future = mc.asyncBopPipedUpdateBulk(KEY, updateElements);
errorList = future.get(5000L,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

개행이 필요 없을 것 같습니다. 전체적으로 확인해주세요.

@jhpark816 jhpark816 merged commit 0822783 into naver:develop Dec 5, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants