[TR-389] TrecQuerying Cache error Created: 10/May/16  Updated: 10/May/16  Resolved: 10/May/16

Status: Resolved
Project: Terrier Core
Component/s: .querying
Affects Version/s: None
Fix Version/s: 4.2

Type: Bug Priority: Trivial
Reporter: Agustin Marrone Assignee: Craig Macdonald
Resolution: Fixed  
Labels: None


 Description   
In line 670, the class org.terrier.applications.batchquerying.TRECQuerying has this:

((Request)rs).setResultSet(rs);

That is an error. The correct code should be:

((Request)srq).setResultSet(rs);

Otherwise, the application will crash when we try to use a cache strategy.

(Sorry for my English)

 

 Comments   
Comment by Agustin Marrone [ 10/May/16 ]

Line number is 666, not 670 .

Comment by Craig Macdonald [ 10/May/16 ]

I agree, this is a (trivial) bug. As results cache are not used by default, I have dropped the priority. We will fix for the next release. Is this your affiliation: Universidad Nacional de Luján ? As we will credit you for finding the bug in the next release.

Comment by Agustin Marrone [ 10/May/16 ]

Yes Craig, it's Universidad Nacional de Luján, a public university from Argentina.

Than you!

Comment by Craig Macdonald [ 10/May/16 ]

Thanks, committed for the next release.

Generated at Wed Dec 13 11:07:47 GMT 2017 using JIRA 7.1.1#71004-sha1:d6b2c0d9b7051e9fb5e4eb8ce177ca56d91d7bd8.