Added track info to json response and make API thread safe #34
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
danicuki
commented
Dec 30, 2013
danicuki
commented
- There is no reason to not return track info the in the API json
- tyrant client is not thread safe, so lock is required to avoid problems
- Implemented delete behavior in API
- When first and second place have same score means that probably it is the same track. Return first then
The war file was pulled from wget http://www.gtlib.gatech.edu/pub/apache//lucene/solr/3.5.0/apache-solr-3.5.0.tgz ls apache-solr-3.5.0/dist/apache-solr-3.5.0.war
…e name * updated Hashr.jar with hashr-2.0.jar
…3.5.0/example/solr/conf
… the same track. return the first then
…rray and save new array size to disk
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.