Multidoc tokenize #1466
Merged
Multidoc tokenize #1466
Conversation
This file contains hidden or 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
AngledLuffa
force-pushed
the
multidoc_tokenize
branch
from
e7797e5 to
07c3fe1
Compare
…ntially being added in different orders in the token / word maps Many tests are updated because SpaceAfter etc should now be at the start of a misc column
…o whitespace tokenize it when doing a bulk_process with a pretokenized TokenizeProcessor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a document is already tokenized, and the TokenizeProcessor is set to
pretokenized=True, it is not necessary to try to retokenize the text of the document. In fact, it might not even be possible if the complete document text isn't availableAddresses #1464