[MAGNOLIA-7335] Efficiently publish a large number of nodes Created: 12/Jun/18 Updated: 12/Jun/18 Resolved: 12/Jun/18 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Moritz Kraus | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Description |
|
Hi Magnolia team,
during an action execution we change 1.000 items in different sites/disjunct paths of a workspace. We want to publish these (and only these) 1000 changed items. By now we activate/publish all modified items individually, which results in 1.000 publication HTTP requests and this is quite sloooow. What would you recommend to get these 1000 changes to public more efficiently?
Thanks in advance! Kind regards, Moritz Kraus Lemonize GmbH
Edit: this should be a support ticket. I created another ticket, please link/merge it: https://jira.magnolia-cms.com/browse/SUPPORT-8776 |