Weave Code
Elastica Bundle Laravel Package
fazland/elastica-bundle
Fazland Elastica Bundle integrates Elasticsearch into Symfony applications via the Elastica client. It offers configurable indexes and mappings, repository services, Doctrine entity persistence, and commands for managing and populating search indexes.
Fazland ElasticaBundle integrates the Elastica Elasticsearch client into Symfony, providing a clean, configuration-driven way to manage indices, types, and mappings. It bundles client setup, index configuration, and persistence listeners so you can index and search documents without boilerplate.
- YAML-based configuration for clients, indices, and mappings
- Automatic index and type creation from mappings
- Doctrine ORM/ODM listeners for keeping indices in sync
- Repositories and finder services for expressive search queries
- Compatible with Symfony's DI container and console commands
Frequently asked questions about Elastica Bundle
- What is fazland/elastica-bundle used for?
- It is a Symfony bundle that wraps the Elastica PHP client to integrate Elasticsearch into Symfony applications. It lets you configure indexes, mappings, and search services through bundle configuration and dependency injection. It is a fork of FOSElasticaBundle with Fazland-specific service wiring, aimed at Symfony 2.8/3.x projects using Elasticsearch 2.x–5.x.
- Does fazland/elastica-bundle work with Laravel?
- No. This package is a Symfony bundle and depends on Symfony 2.x container, config tree, command, and event-dispatcher APIs. It is not designed for Laravel and will not install or run in a standard Laravel application. Laravel developers should use Laravel Scout, the official elasticsearch/elasticsearch PHP client, or a Laravel-specific Elasticsearch package instead.
- Which Symfony versions does fazland/elastica-bundle support?
- The bundle targets Symfony 2.8 and 3.x. It assumes Symfony 2-era service definitions, configuration trees, and event dispatcher behavior. It does not support Symfony 4, 5, 6, or 7, and there are no upstream updates to add compatibility.
- Which Elasticsearch versions are compatible with fazland/elastica-bundle?
- It was built for the Elasticsearch 2.x–5.x era via the Elastica client, and may work with some 6.x clusters only after careful version alignment. It will not work with Elasticsearch 7.x or 8.x without upgrading the Elastica client and rewriting index mappings and analyzers for modern REST API semantics. Always validate the Elastica version against your cluster version before committing.
- How do I install fazland/elastica-bundle?
- You install it with Composer, but only in a project already pinned to Symfony 2.x and a compatible Elastica 3.x–5.x version. Because the bundle is an abandoned fork, you should lock exact versions and forbid automatic Symfony or Elastica updates in that subtree. A version-locked composer.json and a containerized runtime are strongly recommended.
- How do I configure indexes and mappings with this bundle?
- Configuration is done through the bundle's Symfony config tree, where you define indexes, mappings, and service definitions. The bundle wires those settings into Elastica client services and dependency injection aliases. You will need to write Elasticsearch 2–5 era mappings and analyzers, as newer ES mapping semantics are not supported.
- Does fazland/elastica-bundle integrate with Doctrine ORM?
- Yes, the bundle typically hooks Doctrine lifecycle events to keep Elasticsearch indexes in sync with ORM entities. This assumes a Doctrine-heavy persistence layer and Symfony 2-era event dispatcher behavior. You should smoke-test the listener behavior, index populate, and search flow in a staging environment before production.
- Is fazland/elastica-bundle maintained?
- No. The last release was on 2017-12-10, and there are no upstream fixes, PHP 8 compatibility updates, or security advisories triaged. The fork has no active maintainer and zero recorded dependents, so there is no ecosystem validation. Treat it as a legacy-compatibility option with a defined exit path.
- What are the alternatives to fazland/elastica-bundle?
- For maintained Symfony integration, FOSElasticaBundle is the closest alternative and is actively maintained. For decoupled control, use the official elasticsearch/elasticsearch PHP client directly behind a thin repository abstraction. Laravel applications should use Laravel Scout or the official PHP client instead of this Symfony bundle.
- What risks should I validate before using fazland/elastica-bundle in production?
- Validate three compatibility matrices: Symfony minor version against the bundle's service definitions, Elastica version against your cluster's REST API, and Doctrine version against the lifecycle listener expectations. Because there is no post-2017 compatibility documentation, run a smoke test covering index populate, search, and Doctrine listener behavior. Plan a migration to FOSElasticaBundle or the official client from day one, and budget for internal fork maintenance including PHP 8 and CVE backporting.
Weaver
How can I help you explore Laravel packages today?