index without position data confluence error

tousifs

Hello Team,

I have upgraded confluence From 4.3 to 5.1 and then 5.2. 

But for 5.1 i have not checked all the plugins compatibility.

upgradation is successful. But whenever i am searching in confluence search its throwing below error.

Java.lang.IllegalStateException: field "title" was indexed without position data; cannot run SpanTermQuery (term=resource)
    at org.apache.lucene.search.spans.SpanTermQuery.getSpans(SpanTermQuery.java:129)

i have recreated indexes from scracth, Rebild all indexes, disable all custom plugins and but this error is still in system.

please let me know your suggection how i can fix this issue.

 

Thank you,

Tousif

 

Rodrigo Girardi Adami

Hello Tousif,

I do believe that something went wrong with the upgrade after 4.3. Have you tried to revert and upgrade Confluence again, but before that removed the third party plugins from Confluence to make sure that there aren't compatibility issues caused by them?

I recommend to:

1) Backup Confluence database and try to remove all third party plugins from the instance by running the following commands:

•  Shutdown Confluence
•  Make a backup of the database
•  Remove The following folders:
• * <confluence-home>/bundled-plugins folder
• * <confluence-home>/plugin-cache folder
• * <confluence-home>/plugins-osgi-cache folder
• * <confluence-home>/plugins-temp folder
•  Run this query to remove all plugins from *PLUGINDATA*:
• {code}delete from plugindata;{code}
•  Perform a Select from BANDANA to see the state of plugins:
• {code}select BANDANAVALUE from BANDANA where BANDANAKEY = 'plugin.manager.state.Map';{code}
•  Update this to '</map>':
• {code}UPDATE BANDANA SET BANDANAVALUE='<map/>' WHERE BANDANAKEY='plugin.manager.state.Map';{code}
•  This will Enable All plugin.
•  Delete the <confluence-home>/index folder
•  Restart Confluence
•  Rebuild all indexes again and check if the issue persists

2) If the issue persists, there is some corruption caused by the upgrade. Try to restore the 4.3 version into a staging instance and perform a new upgrade without all third party plugins and check if that resolves.

 

Cheers,

Rodrigo