From: Karl K. <ka...@kl...> - 2010-12-09 10:42:39
|
Peter von Kaehne <re...@gm...> writes: > I think this is actually uncovering a bug: > morph:<whatever> should work as should && to do a logical AND. I had a conversation with Troy about exactly this about a month ago. He said that the current lucene indexing keys do not include morph, so this is now on his list of things to add "soon". He intends to add a fairly extreme level of generality for the sake of users of commercial packages like BibleWorks and Accordance, which generate a tokenized internal index markup like this: G2532@CONJ G3056@N-NSM G2258@V-IXI-3S and then they expect their users to understand searches like G2532@* *@N-NSM I think it's somewhat twisted, but it does represent a (perverse) user compatibility generality. Anyhow, the point is, not right now, but in a (relatively) near-term improvement. |