[allura:tickets] #4745 Use new artifact session extension in webapp

[Dave Brondsema <br...@users.sf.net>]

- **status**: open --> closed
- **Comment**:

BatchIndexer has already been moved to the Allura codebase and is used during improt tasks.  Using it in web requests is not going to help much since not my artifacts are added in a normal request, and there are not normally multiple session flush() calls anyway.



---

** [tickets:#4745] Use new artifact session extension in webapp**

**Status:** closed
**Milestone:** forge-backlog
**Created:** Mon Aug 20, 2012 03:13 PM UTC by Tim Van Steenburgh
**Last Updated:** Mon Oct 08, 2012 06:02 PM UTC
**Owner:** nobody

[#4577] introduced the BatchIndexer extension for the artifact session, specifically for use in migrations. Next step is to use the new extension in the Allura webapp.

1. Move `BatchIndexer` and the `substitute_extensions` context manager into the Allura code base.
2. Instantiate `artifact_orm_session` with `BatchIndexer` instead of `ArtifactSessionExtension`.
3. Subclass or otherwise modify `MingMiddleware` to flush `BatchIndexer` at the end of a web request.
4. Modify base script command to flush `BatchIndexer` at the end of a script run.


---

Sent from sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.