allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <>
Subject [allura:tickets] #8168 Remove TreesDoc usage
Date Mon, 05 Feb 2018 17:00:53 GMT
- **Milestone**: unreleased --> v1.8.0


** [tickets:#8168] Remove TreesDoc usage**

**Status:** closed
**Milestone:** v1.8.0
**Labels:** indexless 
**Created:** Tue Oct 17, 2017 08:40 PM UTC by Dave Brondsema
**Last Updated:** Wed Oct 25, 2017 04:52 PM UTC
**Owner:** Dave Brondsema

I think we can remove the TreesDoc model and its mongo collection which can be quite large.
 [#7828] did some prior analysis.  My current analysis is that some tests & scripts will
have to be updated, but generally everything should keep working.  Proof of concept is in
branch `db/remove_treestuff`.

The TreesDoc model is used in some LastCommitDoc "refresh" logic currently.  Should be able
to remove that and/or replace it with calls to the lazy computation of LastCommitDocs.  The
only sticking point, I think, is that TreesDoc provides a mapping of commit_id to tree_id
so that some cleanup knows what TreeDoc records can be deleted.  So those would likely never
be able to be cleaned up properly.  Maybe ok, removing them is very infrequent - only for
doing full repo refreshes, not even done when projects are removed (esp. since tree info can
be shared across repos/forks)


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message