Rebuild Unified Search Index failed: Identifier name too long
- Status
- Open
- Subject
- Rebuild Unified Search Index failed: Identifier name too long
- Version
- 12.x
- Category
- Error
- Feature
- Search
- Resolution status
- Confirmed
- Submitted by
- Xavier de Pedro
- Volunteered to solve
- Nelson Ko
- Lastmod by
- Xavier de Pedro
- Rating
- Description
Rebuild Unified Search Index (with MYSQL FTS) failed: Identifier name too long:
Copy to clipboardIndexing failed while processing "5528" (type trackeritem) with the error "Could not perform index modification: Identifier name 'tracker_field_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long" ... (dozens of times a similar error) ... Indexing failed while processing "4" (type sheet) with the error "Could not perform index modification: Identifier name 'tracker_field_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long" Search index could not be rebuilt. Could not perform index modification: Identifier name 'tracker_field_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long No index available.
However, this message is shown below, as if the index was rebuilt:Your index was last fully rebuilt on Viernes 15 de Noviembre, 2013 20:02:48 CET.
UPDATE:
credentials:
u: admin
p: 12345- Reproduced in the associated show.t.o instance, also using Mysql FTS as the unified search engine.
- The "priority" field permanent name was renamed to "tracker_field_trac_as_cal_priority_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB", and rebuilding the index shows:
Copy to clipboardIndexing failed while processing "1" (type trackeritem) with the error "Could not perform index modification: Identifier name 'tracker_field_trac_as_cal_priority_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long" Indexing failed while processing "2" (type trackeritem) with the error "Could not perform index modification: Identifier name 'tracker_field_trac_as_cal_priority_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long" Indexing failed while processing "3" (type trackeritem) with the error "Could not perform index modification: Identifier name 'tracker_field_trac_as_cal_priority_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long" Search index could not be rebuilt. Could not perform index modification: Identifier name 'tracker_field_trac_as_cal_priority_losContenidosDistintosBloquesGuardanCoherenciaMPMMUAB' is too long No index available. - And
Your index was last fully rebuilt on Monday 18 of November, 2013 17:33:04 CET.
UPDATE: Something similar showed up in a 12.x production site when I changed the unified search engine from "Lucene" to "Mysql Full Text Search".
- Solution
- Maybe there should be some limit in the amount of characters taken for the permanent name on tracker fields? (whatever max size is there for the fields in order to have MysqlFTS work?)
- Importance
- 8
- Easy to solve?
- 8
- Priority
- 64
- Demonstrate Bug on Tiki 19+
-
This bug has been demonstrated on show2.tiki.org
Please demonstrate your bug on show2.tiki.org
- Demonstrate Bug (older Tiki versions)
-
This bug has been demonstrated on show.tikiwiki.org
Please demonstrate your bug on show.tikiwiki.org
Show.tiki.org is currently unavailableUnable to connect to show.tikiwiki.org. Please let us know of the problem so that we can do something about it. Thanks.
- Ticket ID
- 4941
- Created
- Sunday 17 November, 2013 07:43:57 UTC
by Xavier de Pedro - LastModif
- Sunday 13 July, 2014 09:59:40 UTC