From 790991aa1007d3271d80bc7e77f5b4f86c9bcef0 Mon Sep 17 00:00:00 2001 From: Christian Mollekopf Date: Sun, 8 Nov 2015 21:07:56 +0100 Subject: Docs --- docs/resource.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/resource.md b/docs/resource.md index 0f3d163..d1b2bbe 100644 --- a/docs/resource.md +++ b/docs/resource.md @@ -100,7 +100,7 @@ To avoid building all indexes initially, and assuming not all indexes are necess Building the index on-demand is a matter of replaying the relevant dataset and using the usual indexing methods. This should typically be a process that doesn't take too long, and that provides status information, since it will block the query. -The indexes status information can be recorded using the latest revisoin the index has been updated with. +The indexes status information can be recorded using the latest revision the index has been updated with. ## Generic Preprocessors Most preprocessors will likely be used by several resources, and are either completely generic, or domain specific (such as only for mail). @@ -109,5 +109,10 @@ It is therefore desirable to have default implementations for common preprocesso The domain types provide a generic interface to access most properties of the entities, on top of which generic preprocessors can be implemented. It is that way trivial to i.e. implement a preprocessor that populates a hierarchy index of collections. +## Preprocessors generating additional entities +A preprocessor, such as an email threading preprocessors, might generate additional entities (A thread entity is a regular entity, just like the mail that spawned the thread). + +In such a case the preprocessor must invoke the complete pipeline for the new entity. + # Pipeline A pipeline is an assembly of a set of preprocessors with a defined order. A modification is always persisted at the end of the pipeline once all preprocessors have been processed. -- cgit v1.2.3