[MGNLMIGRATION-85] Change PersistentMapService to store maps into config workspace instead of the filesystem Created: 01/Oct/12 Updated: 06/Dec/12 Resolved: 06/Dec/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Jozef Chocholacek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
In some deployments, it could be hard (or impossible) to access the filesystem, so the maps should be persisted to the config workspace. |
| Comments |
| Comment by Jan Haderka [ 04/Dec/12 ] |
|
I don't think it's correct to force one way of storage over another. If you think in some installations FS is not accessible you should offer users the choice. OTOH repo files are always in FS so there is always some path that is accessible and can be written to (should use MAGNOLIA_HOME to find it). And on top of it, config workspace is as it's name suggest meant for configuration not for storing logs or anything else. If you need extra workspace, just create it rather then polluting config. If you think it is now too close to release to change this it's ok to push above changes to another ticket, but in such case this new ticket will also have to include migration of persisted reports away from the config workspace. |
| Comment by Jozef Chocholacek [ 06/Dec/12 ] |
|
I'd keep the JCR store, but you're definitely right regarding the workspace. So I've created tickets for that (to be solved later): |