On Saturday, March 08, 2008, SNake! wrote:
> Could it be done by return the field as array and declare that field
> as keyword , like:
I am working on an elegant way to do this. Eventually the plugin will resolve
the foreign relationships automatically. So, if you have a 1:m::book:author,
the p
On Saturday, March 08, 2008, SNake! wrote:
> Actually I am using Luke to check my index, I found it seems to index
> the field without the number (in the case using text type).
>
> And then I try to give the field like "[1],[2],[10]" as keyword type.
> I try to query as authorIDs:"\[1\]" but retu
Could it be done by return the field as array and declare that field
as keyword , like:
In search.yml:
...
Books:
fields:
authorids: keyword
...
and in the model:
function getAuthorIds(){
// mock result
return array(1,2,10);
}
...
Or I have to do a customized indexer
Actually I am using Luke to check my index, I found it seems to index
the field without the number (in the case using text type).
And then I try to give the field like "[1],[2],[10]" as keyword type.
I try to query as authorIDs:"\[1\]" but return no result
On 3月8日, 下午5時18分, wissl <[EMAIL PROTEC
Also, check out: http://www.nabble.com/Lucene-and-n:m-td12695579.html
On Saturday, March 08, 2008, wissl wrote:
> So indexing works so far (what you can tell), but your search does not
> return the results you want? Or are you not sure about the correct
> indexing process itself?
>
> What looks a
So indexing works so far (what you can tell), but your search does not
return the results you want? Or are you not sure about the correct
indexing process itself?
What looks a little bit strange to me is that you index the field
"authorIDs" as a keyword, but your query searches for tokenized
valu
