NXP-30368: Take into account fulltext maxSize during construction #4851
Conversation
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
|
View issue in JIRA: NXP-30368: Take into account fulltext maxSize when computing text in FulltextExtractorWork |
troger
previously approved these changes
Jun 18, 2021
kevinleturc
force-pushed
the
improvement-NXP-30368-limit-fulltext-extraction
branch
from
a6c3b5f
to
399f0b6
Compare
|
I pushed force to remove the Map which was acting as a cache for the same blobs as discussed with @efge . |
efge
approved these changes
Jun 18, 2021
bdelbosc
approved these changes
Jun 21, 2021
troger
approved these changes
Jun 22, 2021
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.
No description provided.