Elasticsearch 6, the latest ES version, requires some things to be done different. Our package still works with this version, but the README is outdated and should address some things better.

I followed the instructions closely and encountered a problem by the time I reach the part where I get to use to upsertToIndex().

I'm using Laravel 5.1 for this example. I have the Searchable interface saved at app\Spatie\SearchIndex\Searchable.php. My Model is as follows:

<?php

namespace App;

use App\Spatie\SearchIndex\Searchable;
use Illuminate\Database\Eloquent\Model;

class Post extends Model implements Searchable
{
    public $fillable = ['title', 'content', 'tags'];

    /**
     * Returns an array with properties which must be indexed
     *
     * @return array
     */
    public function getSearchableBody()
    {
        $searchableProperties = [
            'title' => $this->title,
            'content' => $this->content
        ];

        return $searchableProperties;
    }

    /**
     * Return the type of the searchable subject
     *
     * @return string
     */
    public function getSearchableType()
    {
        return 'post';
    }

    /**
     * Return the id of the searchable subject
     *
     * @return string
     */
    public function getSearchableId()
    {
        return $this->id;
    }
}

My Controller as follows:

class Posts extends Controller
{
    public function index()
    {
        $post = Post::first();

        \SearchIndex::upsertToIndex($post);
    }
}

I'm getting the error:

Argument 1 passed to Spatie\SearchIndex\SearchIndexHandlers\Elasticsearch::upsertToIndex() must be an instance of Spatie\SearchIndex\Searchable, instance of App\Post given, called in /home/vagrant/Code/laravel51/bootstrap/cache/compiled.php on line 5964 and defined

I'm pretty sure I've implemented the interface properly, as removing any of these methods will throw an error reminding to implement the interface properly. The only difference from your README is that the example code uses "Eloquent" instead of "Model".

Hi! TIA for a great package, looking forward to using it.

I didn't see any documentation around reindexing an entire model. I recently added the package, but I now want to get my entire model into the index.

Any suggestions how to do that?

Could we add a private indexExists() method inside the ElasticSearch - handler and adjust clearIndex() like this:

public function clearIndex($indexName = null)
{
    $indexName = $this->resolveIndexName($indexName);

    if (! $this-indexExists($indexName)) {
        return;
    }

    $this->elasticsearch->indices()->delete(['index' => $indexName]);
 }

Cause the underlying ElasticSearch Client just throws an exception if there is no index to clear.

Another possible implementation would be to allow setting an ignore parameter and pass this one along with the index into the delete request.

What do you think?

I have created a Elasticsearch 1.4 inside my homestead php 7 box. This was done from the Forge Recipe. I have successfully added to the index via the SearchIndex::upsertToIndex($model); method. But when I run the following command below its throwing 404 errors when it shouldn't be because I can hit them at localhost:9200/{indexName} without any issues.

<?php

namespace App\Console\Commands;

use App\Models\Site;
use Elasticsearch\Common\Exceptions\Missing404Exception;
use Illuminate\Console\Command;
use Illuminate\Support\Facades\Config;
use Spatie\SearchIndex\SearchIndexFacade as SearchIndex;

class ClearSearchIndex extends Command
{
    /**
     * The name and signature of the console command.
     *
     * @var string
     */
    protected $signature = 'app:search:clear';

    /**
     * The console command description.
     *
     * @var string
     */
    protected $description = 'Clear search index.';

    /**
     * Create a new command instance.
     *
     * @return void
     */
    public function __construct()
    {
        parent::__construct();
    }

    /**
     * Execute the console command.
     *
     * @return mixed
     */
    public function handle()
    {
        $index = Config::get('searchindex.elasticsearch.defaultIndexName');
        $sites = Site::all('full_domain');

        try {
            SearchIndex::clearIndex();
            $this->info("Cleared search index for: {$index}");
        } catch (Missing404Exception $e) {
            $this->comment("Index: {$index} not found.");
        }

        foreach($sites as $site) {
            Config::set('searchindex.elasticsearch.defaultIndexName', $site->full_domain);
            try {
                SearchIndex::clearIndex();
                $this->info("Cleared search index for: {$site->full_domain}");
            } catch (Missing404Exception $e) {
                $this->comment("Index: {$site->full_domain} not found.");
            }
        }
    }
}

Was wondering if this is an issue on my end, or something that is an issue with the library. This is the following output that I get from doing the CLI command: https://www.dropbox.com/s/0t9bur06cl5dxt2/Screenshot%202016-03-31%2015.19.09.png?dl=0

Hi. Nice and easy to use implementation of elasticsearch. How can you implement pagination on the results consistent with laravel ? Do you need to do that in laravel?

In the newest Elastic versions, multiple types per index aren't allowed anymore: https://www.elastic.co/blog/index-type-parent-child-join-now-future-in-elasticsearch

This PR adds optional indexName arguments to make it easier to work with multiple indices.

I use the PHPUnit\Framework\TestCase notation instead of PHPUnit_Framework_TestCase while extending our TestCases. This will help us migrate to PHPUnit 6, that no longer support snake case class names.

Just needed to bump PHPUnit version to 4.8.36, to keep compatibility.

I didn't update to PHPUnit 5 'cause this package still supports PHP 5.5.

Hi, I have a L5.2 application and all seems to be correctly configured.

When I try to SearchIndex::upsertToIndex($createdModel);

With the following use specified

use Spatie\SearchIndex\SearchIndexFacade as SearchIndex;

I get the error: Class searchIndex does not exist

Any suggestions of obvious things I may have missed?

Currently it is possible to set the default index to use (either for Algolia or ES) in the searchindex config. I noticed this block:

/*
 * This index will be used whenever you don't explicitly
 * set one yourself.
 */
'defaultIndexName' => 'main',

There is nothing in the docs explaining how to "explicitly set one yourself" aside from in the config. Is this possible? E.g. \SearchIndex::upsertToIndex($product, 'products');. Could one update the config value at runtime? although I suppose the SearchIndex class in instantiated when the app is booted so will ignore any subsequent config value change.

It would be nice to be able to specify which index to upsert/query to/from. Or would one normally have all records in the same index and filter out the ones not relevant? E.g. products/posts. Ideally this would be driver agnostic (e.g. work the same way for ES and Algolia).

Presently, searchindex does not support the ElasticSearch 2.0 library for PHP. Is there a plan to add support for 2.0 while maintaining backwards compatibility with the 1.0 branch, perhaps via a separate branch in the searchindex project?