qlsgroup / elastic-search
An Elastic Search datasource and data mapper for CakePHP 3.0
Installs: 9 197
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 0
Forks: 53
Type:cakephp-plugin
Requires
- cakephp/cakephp: ^4.3.0
- ruflin/elastica: ^7.1
Requires (Dev)
- cakephp/cakephp-codesniffer: ^4.0
- phpunit/phpunit: ^8.5
README
Use Elastic Search as an alternative ORM backend in CakePHP 3.6+.
You can find the documentation for the plugin in the Cake Book.
Installing Elasticsearch via composer
You can install Elasticsearch into your project using
composer. For existing applications you can add the
following to your composer.json
file:
"require": {
"cakephp/elastic-search": "^2.0"
}
And run php composer.phar update
Versions Table
You are seeing the 2.x version.
Connecting the Plugin to your Application
After installing, you should tell your application to load the plugin:
use Cake\ElasticSearch\Plugin as ElasticSearchPlugin; class Application extends BaseApplication { public function bootstrap() { $this->addPlugin(ElasticSearchPlugin::class); // If you want to disable to automatically configure the Elastic model provider // and FormHelper do the following: // $this->addPlugin(ElasticSearchPlugin::class, [ 'bootstrap' => false ]); } }
Defining a connection
Before you can do any work with Elasticsearch models, you'll need to define a connection:
// in config/app.php 'Datasources' => [ // other datasources 'elastic' => [ 'className' => 'Cake\ElasticSearch\Datasource\Connection', 'driver' => 'Cake\ElasticSearch\Datasource\Connection', 'host' => '127.0.0.1', 'port' => 9200 ], ]
As an alternative you could use a link format if you like to use enviroment variables for example.
// in config/app.php 'Datasources' => [ // other datasources 'elastic' => [ 'url' => env('ELASTIC_URL', null) ] ] // and make sure the folowing env variable is available: // ELASTIC_URL="Cake\ElasticSearch\Datasource\Connection://127.0.0.1:9200?driver=Cake\ElasticSearch\Datasource\Connection"
You can enable request logging by setting the log
config option to true. By
default the debug
Log profile will be used. You can also
define an elasticsearch
log profile in Cake\Log\Log
to customize where
Elasticsearch query logs will go. Query logging is done at a 'debug' level.
Getting a Index object
Index objects are the equivalent of ORM\Table
instances in elastic search. You can
use the IndexRegistry
factory to get instances, much like TableRegistry
:
use Cake\ElasticSearch\IndexRegistry; $comments = IndexRegistry::get('Comments');
If you have loaded the plugin with bootstrap enabled you could load indexes using the model factory in your controllers
class SomeController extends AppController { public function initialize() { $this->loadModel('Comments', 'Elastic'); } public function index() { $comments = $this->Comments->find(); } ...
Each Index
object needs a correspondent Elasticsearch index, just like most of ORM\Table
needs a database table.
In the above example, if you have defined a class as CommentsIndex
and the IndexRegistry
can find it, the $comments
will receive a initialized object with inner configurations of connection and index. But if you don't have that class, a default one will be initialized and the index name on Elasticsearch mapped to the class.
The Index class
You must create your own Index
class so it will allow you to define the name of internal index for Elasticsearch, and it mapping type and define any entity properties you could need like virtual properties. As you have to use only one mapping type for each index, you can use the same name for both (the default behavior when type is undefined is use singular version of index name). Index types were removed in ElasticSearch 7.
use Cake\ElasticSearch\Index; class CommentsIndex extends Index { /** * The name of index in Elasticsearch * * @return string */ public function getName() { return 'comments'; } /** * The name of mapping type in Elasticsearch * * @return string */ public function getType() { return 'comments'; } }
Running tests
Warning: Please, be very carefully when running tests as the Fixture will create and drop Elasticsearch indexes for its internal structure. Don't run tests in production or development machines where you have important data into your Elasticsearch instance.
Assuming you have PHPUnit installed system wide using one of the methods stated here, you can run the tests for CakePHP by doing the following:
- Copy
phpunit.xml.dist
tophpunit.xml
- Run
phpunit