michaeljennings / laralastica Goto Github PK

We've got a use case where we'd need to update multiple indexes with the model data.

I'm not sure if we could extend the listener and write our own or do we need to contribute this as PR and you'd accept it.

@michaeljennings how do you think this should go?

Our use case includes updating entries that are already soft-deleted. In such an instance, when attributes change, they should not be communicated to Elasticsearch. The update should rather be ignored.

The goal is for soft-deleted entries to only be found in the database, not in Elasticsearch.

I guess I could hook in this logic myself, but I wonder what would the proper place be? Is there a sensible way to use a custom observer class, so I can override the created() method?

I've had some issues with this package in combination with Laravel 5.1.
Because of some ServiceProvider changes.

Default, the ServiceProvider is $defer = true.
This means that all the listeners in the serviceprovider are not being loaded by default.

So for instance, if I want to add all say pages to elastic, i want to do something like this:

<?php

Route::get('/', function() {
    foreach(Page::all() as $page) {
       $page->save();
    }
});

Because the service providers defer is true, the events that are being fired from above piece of code arend handled, because the listeners arent initialized.

When I set the defer to false, above piece of code is working.
What can we do about this?

FatalErrorException in Laralastica.php line 8:
Cannot use Elastica\Query\Bool as Bool because 'Bool' is a special class name

this problem solved in
ruflin/Elastica#903

Please upgrade your package.

Could we implement Score query?
requirement: ability to random sort
https://github.com/ongr-io/ElasticsearchDSL/blob/master/src/Query/FunctionScoreQuery.php
@michaeljennings

We are still running 5.x on our production environment, but we will be spending some time on rewriting stuff that is holding us back and will be striving to go up the upgrade tree.

Is there a roadmap/timeline to add support for elasticsearch 7?

In some cases, we might save a model but not wish to sync it to ES.

For example, if we are updating an attribute that is not indexed, this creates an unnecessary overhead.

Is there a preferred method to achieve this?

Allows to add one or more sort on specific fields. Each sort can be reversed as well

reference : https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-sort.html