- Can I use nqxcode/zendsearch with Laravel 8.x or 9.x?
- No, this package is PHP 5.x-only and won’t work with Laravel 8.x/9.x (PHP 8.x). You’d need a Docker container with PHP 5.6 + Laravel 5.x for isolation, or rewrite the wrapper for PHP 8.x compatibility.
- What are the hardware requirements for Zend_Search_Lucene?
- Lucene indexes are file-based and require server write access to a directory (e.g., `/var/lucene`). Avoid serverless or shared hosting—performance degrades with >100K documents, and no sharding/replication exists.
- How do I sync database changes with Lucene indexes?
- There’s no built-in sync. You’ll need custom observer events or queue listeners (if retrofitted) to trigger index updates. Example: `Model::observe(LuceneIndexObserver::class)` in a service provider.
- Is this package secure for production use?
- The BSD-3-Clause license is permissive, but the package lacks modern security audits. Malicious index corruption risks exist, and no built-in backups or recovery tools are provided—manual handling is required.
- Can I integrate this with Eloquent models?
- No native integration exists. You’d need custom repositories, traits, or a Facade wrapper to bridge Lucene with Eloquent. Async operations (queues) aren’t supported—indexing is blocking.
- What’s the best alternative if I need modern search in Laravel?
- For Laravel 8.x+, consider Laravel Scout (with Algolia/Meilisearch) for SaaS scalability or PostgreSQL’s `tsvector` for full-text search. These avoid Lucene’s PHP 5.x limitations and offer better performance.
- How do I test this package in a CI/CD pipeline?
- The package lacks modern testing support (PHPUnit 4.x max). Manual testing is required, especially for edge cases like Unicode search or large payloads. Mock Lucene in tests via a wrapper Facade.
- Will this package break if I upgrade PHP or Laravel?
- Yes—it’s abandoned since 2015 with no PHP 8.x support. Upgrades may break dependencies. Plan for a rewrite or isolation (e.g., Docker) if stuck with PHP 5.x.
- How do I handle index backups and corruption?
- No built-in tools exist. You’ll need custom scripts to backup Lucene directories (e.g., `tar /var/lucene`) and manual recovery procedures. Corruption risks are high without replication.
- Can I use this for high-traffic or real-time search?
- No—Lucene isn’t designed for distributed or real-time search. It’s suited only for low-volume, self-hosted use cases (e.g., admin panels). For scalability, use Elasticsearch or OpenSearch instead.