On 4/20/2014 11:10 AM, Robert Muir wrote: > I think you need to use 2 separate fields here? (one for n=1 and one for n=2) > > You just cant really have "correct positions" for n=1 and n=2, its not > possible.
There may be details to this that I do not understand. I'm fairly clueless about both CJK and writing Lucene code -- Solr does all of that for me. What is "n" in what you wrote above? One problem with two separate fields is that you must know when to use one or the other. This is particularly hard when you have a "simple search" form with just a single text input and no tweakable options. Also, we are searching across half a dozen fields with edismax. Does that mean I need to have two copies of all (or most of) those fields? How do I decide which copy to use? How will the *users* decide which one to use on an advanced search field? A small increase in complexity is OK in the website search code, but we try to avoid any increase in the complexity of the user interface unless it's easy to understand and the user will see a tangible benefit. Thanks, Shawn --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
