One way would be to create a copyField containing both the fields and use it
as the dictionary's source.
If you do want to keep separate dictionaries for both the fields then I
guess we can introduce per-dictionary overridable parameters like the
per-field overridden facet parameters. That would be cleaner than json
params. What do you think?
On Wed, Jul 16, 2008 at 6:26 AM, Ryan McKinley <[EMAIL PROTECTED]> 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
>
--
Regards,
Shalin Shekhar Mangar.
