Major Description
This ticket is to add a second type of routed alias in addition to the current time routed aliases. The new type of alias will allow data driven creation of collections based on the values of a field and automated organization of these collections under an alias that allows the collections to also be searched as a whole.
The use case in mind at present is an IOT device type segregation, but I could also see this leading to the ability to direct updates to tenant specific hardware (in cooperation with autoscaling).
This ticket also looks forward to (but does not include) the creation of a Dimensionally Routed Alias which would allow organizing time routed data also segregated by device
Further design details to be added in comments.
Attachments
Attachments
1.
|
Move time based logic into TimeRoutedAlias class |
|
Resolved | Gus Heck |
|
||||||||
2.
|
Implement a basic CategoryRoutedAlias class |
|
Resolved | Unassigned | |||||||||
3.
|
Enforce a max cardinality on category routed aliases |
|
Resolved | Unassigned |
|
||||||||
4.
|
Provide regex based category validation for CategoryRoutedAliases |
|
Resolved | Unassigned |
|
||||||||
5.
|
Update CREATEALIAS to support new parameters for category routed aliases |
|
Resolved | Unassigned |
|
||||||||
6.
|
Investigate Memory Footprint of CategoryRoutedAliasUpdateProcessorTest |
|
Open | Unassigned |
