Fix #2274: update NewMemOnly to use DefaultIndexType; added regression test for change#2355
Open
Vishhh03 wants to merge 1 commit into
Open
Fix #2274: update NewMemOnly to use DefaultIndexType; added regression test for change#2355Vishhh03 wants to merge 1 commit into
Vishhh03 wants to merge 1 commit into
Conversation
…d regression test for the change
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes 2274
Description:
bleve.NewMemOnly()was using the olderupside_downindex format, which does not support features like Synonym Search. I updated it to useConfig.DefaultIndexTypeinstead so it defaults toscorchand supports in-memory usage.Testing Performed:
As requested in the issue thread, I wanted to make sure switching
NewMemOnlyto usescorchwouldn't break anything.go test ./...across the entire workspace. All tests passed successfully.TestSynonymInMemtest cases now successfully pass with the new in-memoryscorchindex behavior.