Ticket #9557 (closed PLIP: wontfix)
TextIndexNG3 integration
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | Future |
Component: | General | Version: | |
Keywords: | Cc: |
Description
http://plone.org/products/plone/roadmap/165
Ship Plone 3.0 with TextIndexNG3 as default text index
Proposed by
Andreas Jung
Proposal type
Architecture
State
being-discussed
Motivation
TextIndexNG 3 provides a much more powerful fulltext indexing story to Plone (compared to ZCTextIndex). TXNG
provides a more flexible configuration, much better i18n support, more powerful query support etc. ZCTextIndex
lacks a lot of high-level functionalities to provide a better fulltext indexing support to Plone. Proposal
ZCTextIndex should be replaced with TextIndexNG 3.
Implementation
TXNG already supports Plone directly with adapter, quickinstaller support, migration etc.
Deliverables
TXNG needs some minor extensions:
- better support for ATFile (in order to index both Description + binary content) (will be added in TXNG 3.2.X later this year)
- review of the ranking performance
- review of the integration with Linguaplone
Perhaps it makes sense to make TXNG an option as part of GenericSetup profile (either create a site with ZCTextIndex or TXNG)
Risks
- TXNG 3 uses its own converter framework and therefore does not and will not use PortalTransforms. It might be confusing having two converter frameworks with different configurations.
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.