lutece-lucene-indexer

Implement a Lucene index with swap-based lifecycle for Lutece 8 plugins.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/vanhemsj/lutecepowers --skill lutece-lucene-indexer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lutece-lucene-indexer
Source: https://github.com/vanhemsj/lutecepowers/tree/main/skills/lutece-lucene-indexer
Command: npx skills add https://github.com/vanhemsj/lutecepowers --skill lutece-lucene-indexer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a battle-tested pattern for implementing a plugin-internal Lucene search index in a Lutece 8 plugin, enabling custom indexing, per-plugin daemons, and reliable, scalable search capabilities.

Core Features & Use Cases

  • Custom per-plugin Lucene index supporting domain-specific fields and tailored query experience.
  • Full and incremental indexing workflows driven by a daemon, and a lightweight queue.
  • Use Case: Imagine a plugin with dozens of entities; this pattern enables fast reindexing and precise search across those entities.

Quick Start

Configure your plugin to expose a Lucene-based search index, wire it to a per-plugin daemon, and implement the indexer interface to start indexing.

Frequently Asked Questions about lutece-lucene-indexer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a Lucene search index inside a Lutece 8 plugin?

Full and incremental indexing workflows are driven by a per-plugin daemon and a lightweight queued actions system, which processes indexing tasks efficiently across plugin modules.

How does the swap-based index lifecycle work in Lutece?

The swap-based index lifecycle creates a temporary index, validates it, and then atomically replaces the main one, ensuring reliable search availability during reindexing.

Can I use CDI with Lucene to build a custom search for Lutece plugins?

Yes, this pattern relies on CDI and Lucene to build a plugin-internal search index, allowing you to define domain-specific fields and a tailored query experience for your entities.

What is the best way to handle incremental indexing for a Lutece plugin?

The best way to handle incremental indexing is using the lightweight queued actions system alongside a daemon, allowing precise and fast reindexing without rebuilding the entire index.

When should I not use a plugin-internal Lucene index in Lutece 8?

You should avoid a plugin-internal Lucene index if your plugin has very few entities or lacks complex search requirements, as the daemon, indexer interface, and queue add architectural overhead.