Error message in 5.6 Advanced Search with phrase
On an instance of 5.6 (running PostgreSQL 9.1) when I perform an advanced search using a phrase, I see the following error message in the server log…
Caused by: org.nuxeo.ecm.core.storage.sql.jdbc.QueryMaker$QueryMakerException: Cannot use phrase search in fulltext compatibilty mode. Please upgrade the fullte
xt table: "this is a test phrase"
at org.nuxeo.ecm.core.storage.sql.jdbc.dialect.DialectPostgreSQL.getDialectFulltextQuery(DialectPostgreSQL.java:356)
at org.nuxeo.ecm.core.storage.sql.jdbc.NXQLQueryMaker$WhereBuilder.visitExpressionFulltext(NXQLQueryMaker.java:1742)
at org.nuxeo.ecm.core.storage.sql.jdbc.NXQLQueryMaker$WhereBuilder.visitExpression(NXQLQueryMaker.java:1366)
at org.nuxeo.ecm.core.query.sql.model.Expression.accept(Expression.java:42)
at org.nuxeo.ecm.core.storage.sql.jdbc.NXQLQueryMaker$WhereBuilder.visitMultiExpression(NXQLQueryMaker.java:1334)
at org.nuxeo.ecm.core.query.sql.model.MultiExpression.accept(MultiExpression.java:40)
at org.nuxeo.ecm.core.storage.sql.jdbc.NXQLQueryMaker.buildQuery(NXQLQueryMaker.java:421)
at org.nuxeo.ecm.core.storage.sql.jdbc.JDBCMapper.query(JDBCMapper.java:731)
at org.nuxeo.ecm.core.storage.sql.SoftRefCachingMapper.query(SoftRefCachingMapper.java:100)
at org.nuxeo.ecm.core.storage.sql.SessionImpl.query(SessionImpl.java:1106)
at org.nuxeo.ecm.core.storage.sql.ra.ConnectionImpl.query(ConnectionImpl.java:348)
at org.nuxeo.ecm.core.storage.sql.coremodel.SQLSession$SQLSessionQuery.execute(SQLSession.java:581)
at org.nuxeo.ecm.core.api.AbstractSession.query(AbstractSession.java:1525)
... 91 more
I can't find any reference to this error message so I'm left wondering what it means? I did take a look at the source but the root cause is not obvious (at least not to me :). Is there something further I need to configure?
Thanks, Bruce.
The fulltext storage model in postgresql has changed in 5.5. So, I think you're migrating a nuxeo instance from version prior to 5.5 and you didn't upgraded the indexes. The administration document is giving you the information about that point. Mainly you should follow the instructions given on the NXP-5689 ticket.
Another option is to just drop the indexes from the database, install the optional reindex bundle in your bundles platform folder and ask for a re-indexation.