[TOPOPROCES-16] Ambiguity in same topology aggregation Created: 18/May/15 Updated: 19/Oct/17 Resolved: 01/Jun/15 |
|
| Status: | Resolved |
| Project: | topoprocessing |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Michal Polkorab | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3257 |
| Description |
|
It is unclear if the aggregation should also occur in the same topology. We don't know all possible usecases, but we should cover both functionalities. So the aggregation in the same topology should configurable by some tag. |
| Comments |
| Comment by Michal Polkorab [ 18/May/15 ] |
| Comment by Michal Polkorab [ 26/May/15 ] |
|
merged |
| Comment by Michal Polkorab [ 01/Jun/15 ] |
|
There is also problem when the <aggregate-inside> tag is not used. This task should be mandatory - to clearly express the desire to (not) aggregate inside one topology |