PHPackages kalyabin/yii2-solr - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Search & Filtering](/categories/search) 4. / 5. kalyabin/yii2-solr ActivePackage[Search & Filtering](/categories/search) kalyabin/yii2-solr ================== Solr plugin for the Yii2 framework built ontop of Solarium 37PHP Since Oct 15Pushed 10y ago1 watchersCompare [ Source](https://github.com/kalyabin/yii2-solr)[ Packagist](https://packagist.org/packages/kalyabin/yii2-solr)[ RSS](/packages/kalyabin-yii2-solr/feed)WikiDiscussions master Synced 3w ago READMEChangelogDependenciesVersions (1)Used By (0) yii2-solr ========= [](#yii2-solr) A Yii2 Solr Extension built on top of Solarium. Forked from Essentially this is a Yii2 plugin for Solarium and it is dirt simple to use, all it does is abstract certain parts of Solarium into Yii2. There are only two files you need to pay attention to in this repository: - Client - The Solr client, representing the connection - SolrDataProvider - The data provider you can use with all your widgets etc. Normal querying of Solr is very simple with this extension and I will in fact point you towards the [Solarium Documentation](http://wiki.solarium-project.org/index.php/V3:Manual_for_version_3.x). The only part Yii2 really has is in providing the Solarium client class as a application component, to show an example: ``` $query = Yii::$app->solr->createSelect(); $query->setQuery('edismax&qf=title^20.0 OR description^0.3'); $result = Yii::$app->solr->select($query); var_dump($result->getNumFound()); ``` That is what it takes to query Solarium. As you notice the only part of the Solarium documentation you need to replace is where they use `$client` and instead you should use `Yii::$app->solr` (or whatever you have called the Solr application component in your configuration). To setup the application you merely add it to your configuration. As an example: ``` 'solr' => [ 'class' => 'kalyabin\solr\Client', 'options' => [ 'endpoint' => [ 'solr1' => [ 'host' => '10.208.225.66', 'port' => '8983', 'path' => '/solr' ] ] ] ], ``` The `options` part of the configuration is a one-to-one match to Solariums own constructor and options. Using the data provider for widgets is just as easy, as another example: ``` $query = Yii::$app->solr->createSelect(); $query->setQuery('(alt_subject_mpath:' . $model->path . ' OR alt_subject_mpath:' . $model->path . '.*) AND live:1'); new SolrDataProvider([ 'query' => $query, // an example class which assigns variables to the model(s) // and returns the model(s) 'modelClass' => 'SolrResult', 'sort' => [ 'attributes' => [ 'title', 'sales', 'score' ] ] ]); ``` As you will notice the Solarium query object can go straight into the data providers `query` property. Just like in Yii1 you need to provide a `modelClass` since this extension is not connected to active record directly. The reasoning for not implementing a `QueryInterface` and making the query hook into an active record is because in many cases the Solr index represents many active records all at once as such I wanted to make it free form and give the user the ability to produce a specific Solr model that can return any active record they see fit while the data provider just feeds the multiple classes into a widget. So now the basics are understood, you will see there are two others files: - Solr - A helper that I used in my application and I just added in case it would be useful to others - SolrDocumentInterface - An interface that defines a single function to be used within Solr models The `Solr` class is just a helper that you don't really need if you don't want it so I will move onto the `SolrDocumentInterface`. The interface class just defines a single function `populateFromSolr` which takes one argument: the Solarium document object (from a loop). It returns a single Yii2 model. The `populateFromSolr` function is called every iteration of the data providers `prepareModels()` function and only ever takes a single document. ### Health Score 21 — LowBetter than 18% of packages Maintenance20 Infrequent updates — may be unmaintained Popularity8 Limited adoption so far Community9 Small or concentrated contributor base Maturity41 Maturing project, gaining track record Bus Factor1 Top contributor holds 88.9% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/07607e080febd2bb2830e3b315944ce21b774bcabe00a8a7f5bec5921c2b6561?d=identicon)[mkalyabin](/maintainers/mkalyabin) --- Top Contributors [![Sammaye](https://avatars.githubusercontent.com/u/323996?v=4)](https://github.com/Sammaye "Sammaye (8 commits)")[![cebe](https://avatars.githubusercontent.com/u/189796?v=4)](https://github.com/cebe "cebe (1 commits)") ### Embed Badge ![Health badge](/badges/kalyabin-yii2-solr/health.svg) ``` [![Health](https://phpackages.com/badges/kalyabin-yii2-solr/health.svg)](https://phpackages.com/packages/kalyabin-yii2-solr) ``` ### Alternatives [ircmaxell/filterus A library for filtering variables in PHP 44613.4k6](/packages/ircmaxell-filterus)[awesome-nova/dependent-filter Dependent filters for Laravel Nova 26190.2k](/packages/awesome-nova-dependent-filter) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)