Another thought that might work:
Declare two separate components, one for each field and then implement
a QueryConverter that takes in the field and only extracts the tokens
for the field or choice.
This is a definite workaround, but I think it might work. Hmm, except
we only have one QueryConverter....
-Grant
On Jul 15, 2008, at 8:56 PM, Ryan McKinley wrote:
I have a use case where I want to spellcheck the input query across
multiple fields:
Did you mean: location = washington
vs
Did you mean: person = washington
The current parameter / response structure for the spellcheck
component does not support this kind of thing. Any thoughts on how/
if the component should handle this? Perhaps it could be in a
requestHandler where the params are passed in as json?
spelling={ dictionary="location",
onlyMorePopular=true}&spelling={ dictionary="person",
onlyMorePopular=false }
Thoughts?
ryan
