[TYPO3-dev] Zend search Lucene as the new Indexed Search ?

[Ernesto Baschny [cron IT]]

Patrick Gaumond wrote: on 03.12.2007 14:23:
> Dmitry Dulepov [typo3] wrote:
> 
>> Patrick Gaumond wrote:
>>> I'm curious to know if anyone ever tried to use "Zend_Search_Lucene"
>>> as a TYPO3 search engine instead of Indexed Search.
>>
>> Why don't you want to use mnoGoSearch? There is a TYPO3 extension
>> already.
> 
> Hi to Masi, Ingo, Peter, Dmitri and others,
> 
> As stated I was just curious since Lucene is an Apache project and the
> product is used in a lot of Java CMSes.
> 
> I don't have plan to do it or ask someone to do it. Maybe it was more an
> "english-list" question asked in the wrong ML...
> 
> I never said Indexed Search was reinventing the wheel because when
> Kasper came with it there was no wheel... ;)
> 
> I was just recently made aware that > 1000 pages is a bit time
> consumming operation for Indexed Search and was starting to look for
> alternative. Zend stuff coupled with a well known Apache product just
> sound like a good starting point.

The huge-page-tree-problem with indexed_search for searching doesn't
necessarily comes from the fact the indexed_search is "slow", but
because it does very nasty calculations for which PIDs are currently
accessible while respecting the "extendToSubpages" flag that you can set
on any page (so that an access limitation for user-group will expand for
a whole page-tree). This can (and is) very time consuming and a HUGE
join with all PIDs will be made on every indexed_serach query in a large
page tree.

So if you don't need the "extendToSubpages" feature and you have a huge
page tree in TYPO3 you can tell indexed_search to skip this additional
join. In the past you would have to tweak that in the source code
(join_pages = 1 in some .php file), in 4.2 you will be able to configure
that from TypoScript.

Try it out if it makes any difference in your case.

See:
http://lists.netfielders.de/pipermail/typo3-team-core/2007-November/010946.html


Cheers,
Ernesto