[TR-307] PostingIndex.getPostings(POINTERTYPE extends Pointer lEntry) becomes PostingIndex.getPostings(Pointer lEntry) Created: 08/Apr/14  Updated: 16/Jun/14  Resolved: 22/May/14

Status: Resolved
Project: Terrier Core
Component/s: None
Affects Version/s: 3.6
Fix Version/s: 4.0

Type: Task Priority: Major
Reporter: Richard McCreadie Assignee: Richard McCreadie
Resolution: Fixed  
Labels: None

The move to the use of generic PostingIndex structures for the Direct and Inverted indices causes errors in the DependenceScoreModifier.openPostingLists() method, since the POINTERTYPE or index.getInvertedIndex().getPostings() is not known a priori. The assumption that DependenceScoreModifier.openPostingLists() makes is that POINTERTYPE is LexconEntry or extends LexconEntry, e.g. MemoryLexiconEntry. However, getInvertedIndex() returns a PostingIndex<Pointer>, i.e. is more generic.

Since when an index calls PostingIndex.getPostings() POINTERTYPE is generic (type Pointer), the method should only type check for '? extends Pointer' rather than 'is POINTERTYPE that extends Pointer'.

Comment by Richard McCreadie [ 22/May/14 ]

This change API change seems to have been accepted. Resolving.

Generated at Mon Mar 25 12:28:52 GMT 2019 using JIRA 7.1.1#71004-sha1:d6b2c0d9b7051e9fb5e4eb8ce177ca56d91d7bd8.