Lucene index fires during import of person and staff records

Bug #791663 reported by Chad Heuschober
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Sahana Agasti
Status tracked in Mayon

Bug Description

Currently lucene indexing of staff and person records is triggering during import actions. This is not desirable behaviour as it significantly slows the bulk import process.

Supposedly this behavior was remedied for facility import, however the process for disabling indexes was not well documented and has not been successfully backtraced.

Revision history for this message
Chad Heuschober (chad-heuschober) wrote :

Bug triaged. Still looking for means to execute post-import indexing.

Revision history for this message
Usman A (usmonster) wrote :

Does this get past line 28 in apps/frontend/lib/packages/agStaffPackage/lib/model/doctrine/PluginagStaff.class.php
 when you debug? The postSave() action will still be fired, but updateLucene() should return null without doing any of the heavy duty stuff if the constructor passes FALSE for the isAutoIndexed boolean. This has not been applied to agPerson since I don't think it has an updateLucene function (right?).

All the actual indexing should be happening at the end of the entire processImportEvent in agImportNormalization (it fires an event), which is still a slowish process, but it reindexes all staff at once instead of at each save, which is where the real speed-up happens. Optionally, you can make this part of a separate action.

[It's also worth noting that the public CUNY LP trunk doesn't have the most recent internal CUNY code. (Missing last 2+ days of work, I think?) I think sometime on Monday the auto pushes/mirroring stopped happening, or something? Can you investigate and verify?]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers