ZStorm provides no mechanism to change the default Cache

Bug #391996 reported by Stuart Bishop on 2009-06-25
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned
Storm
Medium
Unassigned

Bug Description

Neither ZStorm.get nor ZStorm.create allow you to override the Cache being used.

I think both of these methods should be extended to allow an optional Store factory to be passed in, defaulting to storm.store.Store. This allows people who need to to override the default Cache implementation and size, as well as handling any future options the Store might grow in the future.

Related branches

Stuart Bishop (stub) wrote :

Merge proposal is up for review.

Changed in storm:
assignee: nobody → Stuart Bishop (stub)
importance: Undecided → Medium
milestone: none → 0.15
status: New → In Progress
Stuart Bishop (stub) wrote :

Launchpad is currently setting the Cache and detecting Store initialization using non-public apis in canonical/launchpad/webapp/dbpolicy.py

Changed in launchpad-foundations:
importance: Undecided → Low
status: New → Triaged
Stuart Bishop (stub) on 2009-08-04
Changed in storm:
milestone: 0.15 → none
Changed in storm:
milestone: none → 0.16
Curtis Hovey (sinzui) on 2009-10-09
tags: added: tech-debt
Jamu Kakar (jkakar) on 2009-11-29
Changed in storm:
milestone: 0.16 → 0.17
Jamu Kakar (jkakar) on 2010-08-05
Changed in storm:
milestone: 0.17 → 0.18
Gary Poster (gary) on 2010-10-21
Changed in storm:
milestone: 0.18 → 0.19
Stuart Bishop (stub) on 2011-07-04
Changed in storm:
assignee: Stuart Bishop (stub) → nobody
status: In Progress → Triaged
milestone: 0.19 → none
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers