Skip to content
New issue

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

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

Already on GitHub? # to your account

EZP-31517: Refactored Indexer to rely on Doctrine\DBAL #177

Conversation

alongosz
Copy link
Member

@alongosz alongosz commented Mar 25, 2020

Question Answer
JIRA issue EZP-31517 blocking EZP-30921
Requires ezsystems/ezplatform-kernel#10
Type improvement
Target eZ Platform version v3.0
BC breaks yes
Tests pass yes
Doc needed yes

Summary

This PR refactors Solr Search Indexer to rely on Doctrine Connection instead of Database Handler from Zeta Components (see ezsystems/ezplatform-kernel#10 for more details).

Additionally this Indexer code also relied on deprecated SPI ContentInfo::$isPublished property, which was fixed as well during refactoring.

Doc

The service container parameter ezpublish.spi.search.solr.indexer.class has been dropped (no other BC promises here were broken).

QA

  • Sanity for ezplatform:reindex on Solr 7.7.2.

Checklist:

  • PR description is updated.
  • Tests are implemented missing test coverage, indexing itself covered on API.
  • Added code follows Coding Standards (use $ composer fix-cs).
  • PR is ready for a review.

@alongosz
Copy link
Member Author

FYI ping @ezsystems/documentation-team

lib/Indexer.php Show resolved Hide resolved
@tomaszszopinski tomaszszopinski self-assigned this Mar 30, 2020
Copy link

@tomaszszopinski tomaszszopinski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QA approved on eZPlatform EE 3.0 master with diff.

@alongosz alongosz merged commit fef949b into ezsystems:master Mar 31, 2020
@alongosz alongosz deleted the ezp-31301-replace-dbh-with-doctrine-in-indexers branch March 31, 2020 11:59
# for free to join this conversation on GitHub. Already have an account? # to comment
Development

Successfully merging this pull request may close these issues.

5 participants