Skip to content

fix: correct indexing command to correctly reflect whether full update is happening #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
shieldo merged 1 commit into from
May 26, 2017
Merged

fix: correct indexing command to correctly reflect whether full update is happening #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Indexer/CorpusIndexingCommand.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,7 @@ public function __invoke()
if (empty($this->corpusName)) {
throw new \BadMethodCallException('You need to set a corpus name on the corpus indexing command in order to execute it.');
}
$isFullUpdate = null === $this->deleteQuery;
$isFullUpdate = $this->shouldPreDelete;
$this->eventDispatcher->dispatch(SearchEvents::CORPUS_PRE_UPDATE, new CorpusPreUpdateEvent($this->getCorpus(), $isFullUpdate));
$logger = $this->getLogger();
$logger->info(sprintf('Indexing of corpus "%s" started.', $this->getCorpus()->getName()));
Expand Down