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.
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
Removal logic for fuzzy / exact (no class abstraction) #509
Removal logic for fuzzy / exact (no class abstraction) #509
Changes from 23 commits
89b9005
37f6bee
69c8955
de25476
a698bf0
a2e0c42
845cae3
2a1da6b
48bef03
958161d
7275609
cba7fcd
bcb7cea
c929927
0afd1a1
6f1e4d9
1347e37
2e3c908
bc20a5d
6e26edb
8ba196a
8936ac9
e41c5fa
9c7f4bf
fe6f018
7f0da3e
b438c80
f8040b5
82f0c6c
bf5498f
f172c72
2beca67
f8d89da
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Should also include the
perform_removal
option above?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.
Nit, but maybe call them
_identify
and_remove
if they are not intended to be accessed by the user directly.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.
Let's keep them exposed especially since remove won't work at scales where size of duplicate >> host memory, in which case the user will need to break down identify and remove
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.
Yes, that makes sense to me. What about calling it
identify_duplicates
?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.
Sounds good, initially I thought it's slightly verbose, but another argument in favor of
identify_duplicates
would be that in future we might want to exposeidentify_documents_to_keep
in which the distinction might be necessarycc @ayushdg / @ryantwolf / @VibhuJawa
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.
@ayushdg we're doing this here