Deleting an object via the API and delayed indexing

Next topic

Author	Message
Jim Thaxton	Wednesday 09 December 2009 11:11:59 am Our site is setup with delayed indexing that is updated after an import runs each night. We have started to implement a feature to delete inactive objects throughout the day. The delete script runs the ->purge() and ->expireAllCache() methods on the object. I assume this does not remove the object from the Solr search index. Would we need to run updatesearchindexsolr.php as a cron job after deletes to remove these objects? Is there an API call we can make to have the object removed from the Solr index on delete? The eZ Find extension classes do not have any delete methods as far as I can tell. Web Developer Coupon Cabin Chicago, IL
Paul Borgermans	Saturday 12 December 2009 4:59:00 am Yes, there is an API in eZ Find (or any search plugin): Before you actually remove the objects from eZ Publish, use something like this: $searchEngine = new eZSolr(); .... //loop over objets to delete $searchEngine->removeObject( $contentObject, false ); And call a commit at the end: $searchEngine->commit(); eZ Publish, eZ Find, Solr expert consulting and training http://twitter.com/paulborgermans
Bertrand Dunogier	Saturday 12 December 2009 6:20:12 am Running eZContentObject::expireAllCache() is unnecessary, and actually a bit dangerous ! It completely expires all content-cache and cache-blocks... I don't feel like it is what you need. What you could do instead is use eZContentObjectTreeNode::removeSubtrees() with the $moveToTrash parameter set to false: eZContentObjectTreNode::removeSubtrees( $nodeIDArray, $moveToTrash = false, $infoOnly = true ); It will take care of everything for you, including clearing appropriate caches and removing the object from the search engine index. Bertrand Dunogier eZ Systems Engineering, Lyon http://twitter.com/bdunogier http://gplus.to/BertrandDunogier

Author

Message

Wednesday 09 December 2009 11:11:59 am

Our site is setup with delayed indexing that is updated after an import runs each night. We have started to implement a feature to delete inactive objects throughout the day. The delete script runs the ->purge() and ->expireAllCache() methods on the object.

I assume this does not remove the object from the Solr search index. Would we need to run updatesearchindexsolr.php as a cron job after deletes to remove these objects? Is there an API call we can make to have the object removed from the Solr index on delete? The eZ Find extension classes do not have any delete methods as far as I can tell.

Web Developer
Coupon Cabin
Chicago, IL

Paul Borgermans

Saturday 12 December 2009 4:59:00 am

Yes, there is an API in eZ Find (or any search plugin):

Before you actually remove the objects from eZ Publish, use something like this:

$searchEngine = new eZSolr();
....
//loop over objets to delete
$searchEngine->removeObject( $contentObject, false );

And call a commit at the end:

$searchEngine->commit();

eZ Publish, eZ Find, Solr expert consulting and training
http://twitter.com/paulborgermans

Bertrand Dunogier

Saturday 12 December 2009 6:20:12 am

Running eZContentObject::expireAllCache() is unnecessary, and actually a bit dangerous ! It completely expires all content-cache and cache-blocks... I don't feel like it is what you need.

What you could do instead is use eZContentObjectTreeNode::removeSubtrees() with the $moveToTrash parameter set to false:

eZContentObjectTreNode::removeSubtrees( $nodeIDArray, $moveToTrash = false, $infoOnly = true );

It will take care of everything for you, including clearing appropriate caches and removing the object from the search engine index.

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

eZ debug

Timing:	Jan 18 2025 02:09:34
Script start
Timing:	Jan 18 2025 02:09:34
Module start 'layout'
Timing:	Jan 18 2025 02:09:34
Module start 'content'
Timing:	Jan 18 2025 02:09:35
Module end 'content'
Timing:	Jan 18 2025 02:09:35
Script end

Main resources:

Total runtime	0.7979 sec
Peak memory usage	4,096.0000 KB
Database Queries	61

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0059	589.6172	152.6563
Module start 'layout'	0.0059	0.0045	742.2734	39.5078
Module start 'content'	0.0104	0.7863	781.7813	582.7031
Module end 'content'	0.7968	0.0011	1,364.4844	12.1016
Script end	0.7979		1,376.5859

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0035	0.4384	16	0.0002
Check MTime	0.0013	0.1644	16	0.0001
Mysql Total
Database connection	0.0008	0.0991	1	0.0008
Mysqli_queries	0.7490	93.8679	61	0.0123
Looping result	0.0006	0.0779	59	0.0000
Template Total	0.7582	95.0	2	0.3791
Template load	0.0021	0.2668	2	0.0011
Template processing	0.7560	94.7488	2	0.3780
Template load and register function	0.0002	0.0237	1	0.0002
states
state_id_array	0.0011	0.1333	1	0.0011
state_identifier_array	0.0015	0.1886	2	0.0008
Override
Cache load	0.0018	0.2291	18	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0006	0.0701	3	0.0002
Fetch class attribute name	0.0012	0.1519	5	0.0002
XML
Image XML parsing	0.0012	0.1510	3	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0014	5	0.0000
General
dbfile	0.0009	0.1161	23	0.0000
String conversion	0.0000	0.0014	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 15 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs