Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Remove methods using Class<?> as indexed type identifier in the engine

Description

Follows up on https://hibernate.atlassian.net/browse/HSEARCH-1404#icft=HSEARCH-1404 and HSEARCH-2768.

Once engine APIs won't be exposed in the ORM integration anymore (https://hibernate.atlassian.net/browse/HSEARCH-2768#icft=HSEARCH-2768), we'll be able to remove the methods in the engine that use Class<?> instead of IndexedTypeIdentifier.

We may want to wait until we'll have an abstraction over the metadata extraction process (https://hibernate.atlassian.net/browse/HSEARCH-1401#icft=HSEARCH-1401), so that we can avoid dodgy conversions from IndexedTypeIdenfier to Class<?> in the engine implementation.

Activity

Show:

Yoann Rodière April 25, 2018 at 10:06 AM

Resolved as part of the Search 6 proof of concept groundwork.

The chosen solution was not to replace classes with some generic type, but rather to move APIs relying on a Class<?> to a specific mapper module (the POJO mapper) and expect them to deal with indexes internally.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created June 9, 2017 at 8:33 AM
Updated November 28, 2018 at 3:43 PM
Resolved April 25, 2018 at 10:06 AM