Add support for parsing Solr term vectors #22
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
This causes `bundle install` on Ruby 1.9 to fail, as it tries to install RCov, which works only on Ruby 1.8.
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.
The Solr term vector syntax is ridiculously arcane, and since I wrote up some code to parse it for a project of mine, I thought I'd contribute it here.
I've done my best to stick to "house style," let me know if you'd like this patch prepared in a different way. I've got a module to mix into the Response class (as 'termVectors' lives in the response), and a module to mix into each document, which pulls out the term vector arrays from the response and turns them into some actually useful Ruby code.
I've also included a spec test, based on some of my own Solr data.