Forum: Ferret doing a join between two ferret indexes?

2a321daf565791ad30ac5ee945abf59a?d=identicon&s=25 Izidor Jerebic (Guest)
on 2008-05-09 11:06
(Received via mailing list)
Hello, everybody,

we have a situation where there are two sets of information about
documents - slow changing and fast changing properties. We index
documents by slow changing properties (content) using Ferret directly,
and it works rather well. But now we would like to filter the searches
by a fast-changing property, that is calculated separately, e.g.
"isBookAvailable".

The idea is to put this property in another Ferret index (which gets
rebuilt very frequently really fast), together with unique document id
(we have external unique id for each document) and then somehow "join"
the original index with this index to provide final results (there are
even more nuances, but this description is enough for start).

The problem is we need the correct paging behaviour and search result
count. If we could somehow "join" the two indexes, the paging and
result count would be provided by Ferret. If not, we must go through
*all* ferret result documents from the query on the first index and
apply filter on them (i.e. remove from result set if not available),
to get correct result count and paging behaviour.

At the first look this "joining" is not possible with Ferret. Or is it?

Please, can somebody enlighten me,


izidor
6ac61630880576ab7c9539ec4ab6c510?d=identicon&s=25 Mickael Zabrane (zab)
on 2010-09-05 06:28
Hi Izidor,

Did you find a solution to your indexes merge problem?
As you, I'm wondering how to merge 2 (ore more) indexes in one.

Thanks
Zab

Izidor Jerebic wrote:
> Hello, everybody,
>
> we have a situation where there are two sets of information about
> documents - slow changing and fast changing properties. We index
> documents by slow changing properties (content) using Ferret directly,
> and it works rather well. But now we would like to filter the searches
> by a fast-changing property, that is calculated separately, e.g.
> "isBookAvailable".
>
> The idea is to put this property in another Ferret index (which gets
> rebuilt very frequently really fast), together with unique document id
> (we have external unique id for each document) and then somehow "join"
> the original index with this index to provide final results (there are
> even more nuances, but this description is enough for start).
>
> The problem is we need the correct paging behaviour and search result
> count. If we could somehow "join" the two indexes, the paging and
> result count would be provided by Ferret. If not, we must go through
> *all* ferret result documents from the query on the first index and
> apply filter on them (i.e. remove from result set if not available),
> to get correct result count and paging behaviour.
>
> At the first look this "joining" is not possible with Ferret. Or is it?
>
> Please, can somebody enlighten me,
>
>
> izidor
This topic is locked and can not be replied to.