-
Notifications
You must be signed in to change notification settings - Fork 47
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
REFACTOR: remove unused getMaxPipeCount. #853
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
CollectionPipedInsert.MAX_PIPED_ITEM_COUNT 외에도
CollectionPipedUpdate.MAX_PIPED_ITEM_COUNT 값이 있습니다.
테스트 로직에서 두 값 중 어떤 값을 사용해야 하는 지도 검토해 보시죠.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
셋 다 동일하게 500으로 설정되어있습니다.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
위의 이유가
CollectionPipedInsert.MAX_PIPED_ITEM_COUNT 값을 모든 경우에서 사용하는 이유가 되지 못합니다.
언제가 CollectionPipedUpdate.MAX_PIPED_ITEM_COUNT 값이 700으로 변경될 수도 있습니다.
이 값이 변경되더라도, 테스트 코드는 정상적으로 동작해야 합니다.
따라서, 코드 로직을 확인하고 그 로직에 맞는 값을 사용해야 합니다.
코드를 모두 확인해 보았고,
CollectionPipedInsert.MAX_PIPED_ITEM_COUNT 값을 사용하는 것이 맞다라고 하면,
충분한 설명이 될 수 있을 것입니다.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pipe max count 값이 변경 시, 고려할 수 있는 두 가지 경우입니다.
현재 구현 상의 Insert / Update MAX_PIPED_ITEM_COUNT의 시멘틱을 안다면
두 가지 값의 변경은 함께 이루어질 것이라고 예상합니다.
언젠가
CollectionPipedUpdate.MAX_PIPED_ITEM_COUNT
값이700으로 변경된다면
CollectionPipedInsert.MAX_PIPED_ITEM_COUNT
도 함께700으로 변경될 가능성이 더 높지 않나요?
결론적으로 변수의 의미와 내부 로직을 살펴보니 Insert의 MAX_PIPED_ITEM_COUNT를 사용해도 상관 없다고 생각합니다.