- Can I use mdiyakov/doctrine-solr-bundle in a Laravel application?
- Not directly. It is a Symfony 2/3 bundle built around Symfony's DI container, Doctrine ORM entity lifecycle events, and annotations, and it provides no Laravel service provider, Scout driver, or Eloquent integration. Installing it would require a fork or a substantial bridge to Laravel's container and event dispatcher. For most Laravel apps, Laravel Scout with a Solr driver or Solarium used directly is a better fit.
- Does mdiyakov/doctrine-solr-bundle work with Laravel Scout?
- No. Laravel Scout expects a Scout driver that integrates with Eloquent models, while this package is annotation-driven for Doctrine ORM entities inside Symfony. Scout has no built-in support for this bundle. You would need to build a custom Scout Solr driver on top of Solarium instead.
- How do I install mdiyakov/doctrine-solr-bundle with Composer?
- Composer can download the package because it is a normal Composer package, but Laravel will not auto-discover or register the Symfony bundle. You would have to manually wire Symfony services, configuration, and event dispatcher integration, which is not a simple installation. For a Laravel project, treat installation as a research step only unless you plan to fork and refactor.
- Is mdiyakov/doctrine-solr-bundle compatible with PHP 8 and modern Laravel?
- Compatibility is unlikely. The package targets Symfony 2/3, which are end-of-life, and its PHP constraints are likely PHP 5.6/7.x with no evidence of PHP 8 support or dependency upgrades. Modern Laravel requires current PHP versions and has dependency conflicts with old Symfony components. Production use would be high risk without a maintained fork.
- What Laravel versions does mdiyakov/doctrine-solr-bundle support?
- None officially. It does not target Laravel at all; it is a Symfony bundle for Doctrine ORM and Apache Solr. There is no Laravel service provider, Artisan command, or Eloquent support. You should not expect Laravel version support or framework compatibility.
- Can I index Eloquent models with this Doctrine Solr bundle?
- No. The bundle maps Doctrine ORM entities via annotations and works with Doctrine's lifecycle events and EntityManager. Eloquent models, model events, and Laravel's database layer are not supported. Indexing Eloquent records would require a custom indexing layer or Laravel Scout driver.
- What are the best alternatives to this bundle for Solr search in Laravel?
- Use Laravel Scout with a custom Solr driver built on solarium/solarium, or use Solarium directly inside queued indexing services. If you already use Doctrine via laravel-doctrine, you can borrow mapping and lifecycle-listener patterns but should not install the Symfony bundle. The maintained path is Scout plus a current Solr client, with Eloquent observers or model events driving index updates.
- How does mdiyakov/doctrine-solr-bundle index and query Solr?
- It uses annotation-based field mapping on Doctrine entities and integrates the Solarium client to build and execute Solr queries. Search results are hydrated back into managed Doctrine entities, keeping search logic close to the domain model. The bundle also supports configurable field types, boosts, and custom query building through Symfony's service container.
- Is mdiyakov/doctrine-solr-bundle maintained and safe for production?
- It shows signs of limited maintenance, including a v1.1.1 update with tests and functional additions, but it has only about 12 stars and zero dependents and appears near-abandoned. There is no evidence of PHP 8 compatibility work, dependency upgrades, or a security support policy. Using it in production without a fork and maintenance plan is not advisable.
- Can I reuse the bundle's rollback-on-flush-failure pattern in Laravel?
- Yes, the pattern itself is worth reimplementing. In Laravel, queue indexing after the database commit and use model events or observers to enqueue compensating deletes if a flush fails, so Solr does not diverge from the database. The Symfony-specific EntityManager wrapper and Doctrine Registry integration should be replaced with Laravel jobs, transactions, and Eloquent events.