collection.xconf template references AnalyzingQueryParser removed in Lucene 10

[joewiz]

[This issue was co-authored with Claude Code. -Joe]

Problem

The collection.tpl.xconf template in the base10 profile includes:

<parser class="org.apache.lucene.queryparser.analyzing.AnalyzingQueryParser"/>

This class was removed in Lucene 9. On eXist-db 7.0 (which uses Lucene 10), this causes the entire Lucene index configuration to fail silently — ft:query() with field queries returns 0 results, and the TEI Publisher browse page shows no documents.

How to reproduce

1. Generate any app from a Jinks blueprint on eXist-db 7.0 (feature/websocket-eval or similar build with Lucene 10)
2. Open the browse page — "Found 0 items"
3. Remove the <parser> element from the system collection.xconf and reindex — documents appear

Suggested fix

Remove the <parser> element from collection.tpl.xconf, or conditionally include it only when the Lucene version supports it. The AnalyzingQueryParser was used to enable query-time analysis but Lucene 10's ClassicQueryParser handles this by default.

Related

• [enhancement] update Lucene to 10 eXist-db/exist#6146 (Lucene 10 upgrade)
• fix: update to run with eXist dev version tei-publisher-lib#35 (eXist 7 compatibility fix for map:merge)
• exist 7 incompatibility when generating app #107 (eXist 7 incompatibility when generating app)

[duncdrum]

Yup, I m slightly concerned about the Found 0 items. There is a fallback to the default parser that should kick in, log a warning, but leave search essentially working.

Looks like it trips elsewhere...

[tuurma]

fixed with 6b6c240 and 8857bc4