#946: Bibindex checks for updated_records
-----------------------------+-----------------------
Reporter: adeiana | Owner:
Type: enhancement | Status: assigned
Priority: minor | Component: BibRank
Version: | Resolution:
Keywords: INSPIRE DEPLOYED |
-----------------------------+-----------------------
Changes (by simko):
* status: in_merge => assigned
Comment:
Are you sure the branch does not leak records?
Imagine that the last citation indexer run happened at 10:00, the journal
index was last updated at 10:10, the reportnumber index was last updated
at 10:20, and the citation indexer is waking up again at 10:30. Now if
there is a record R1 updated at 10:05, it will be taken into
consideration; but if there is a record R2 updated at 10:15 or 10:25, then
it won't be taken. So the citation indexer will run well at 10:30, but
only for record R1. When it finishes its run at say 10:40, it will set
its last run-time time stamp to its starting time, which was 10:30. But
upon its next wake-up time at say 11:00, it will not notice that record R2
that was last modified at 10:15 was not citation-indexed at its last run
that happened at 10:30.
So it seems to me that the branch in its current state may be leaking
records, unless you also change the semantics of how
rnkMETHOD.last_updated is being treated, which is something that the
branch does not seem to be doing...
--
Ticket URL: <http://invenio-software.org/ticket/946#comment:3>
Invenio <http://invenio-software.org>
