and the caveat that all fields would need to be declared in the
solrconfig.xml (or get used for both fields)
this could work... would also need to augment the response with the
name of the dictionary, or assert that something will be written all
the time (so you could know the 2nd would b
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 Qu
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 b
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/i
