You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue probably started since v1.1.0.
When a single page is published and yes the queued job is created to send the document.
However even if the queued job is completed successfully, upon further investigation the document is not posted to Elastic endpoint. It turned out that the $batch_size is null as a 3rd parameter to array_splice which does not change the original array and returns an empty array.
I have come up a solution using the same strategy with ReindexJob class to apply a default batch size from configuration if the value is empty. See PR here #74
The text was updated successfully, but these errors were encountered:
This issue probably started since
v1.1.0
.When a single page is published and yes the queued job is created to send the document.
However even if the queued job is completed successfully, upon further investigation the document is not posted to Elastic endpoint. It turned out that the
$batch_size
is null as a 3rd parameter toarray_splice
which does not change the original array and returns an empty array.silverstripe-search-service/src/Service/BatchProcessor.php
Line 36 in ee62b42
silverstripe-search-service/src/Jobs/IndexJob.php
Line 91 in ee62b42
I have come up a solution using the same strategy with
ReindexJob
class to apply a default batch size from configuration if the value is empty. See PR here #74The text was updated successfully, but these errors were encountered: