One query multiple suggesters #59
Merged
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
Closed
hkrishna
added a commit
that referenced
this pull request
Jan 19, 2015
One query multiple suggesters
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.
[DO NOT MERGE] [STILL UNDER TESTING]
Rewriting the /suggest query to contain multiple suggesters in one query rather than having one suggester per query and making multiple query calls in parallel.
Adding queryMixer.json that contains information of each suggester (layers to query, precision, fuzziness etc) - plan is to possibly rip this out into its own module (upto discussion) but for now its nice to have it live in a separate json file instead of being buried in the code. (tests for queryMixer are included)
no separate controllers/tests for suggest_nearby. there is one suggest controller that accepts different queries (see app.js)
Also, #50