mirror of
https://github.com/datahub-project/datahub.git
synced 2025-12-04 06:33:05 +00:00
Update aspect.md
This commit is contained in:
parent
0ec3cdb64c
commit
8f120f15e3
@ -11,9 +11,9 @@ It is also possible to apply the retention based on time, e.g. only keeps the me
|
||||
|
||||
While a metadata aspect can be arbitrary complex document with multiple levels of nesting, it is sometimes desirable to break a monolithic aspect into smaller independent aspects.
|
||||
This will provide the benefits of:
|
||||
1. **Faster read/write**: As metadata aspects are immutable, every `update` will lead to the writing the entire large aspect back to the underlying data store.
|
||||
1. **Faster read/write**: As metadata aspects are immutable, every "update" will lead to the writing the entire large aspect back to the underlying data store.
|
||||
Likewise, readers will need to retrieve the entire aspect even if it’s only interested in a small part of it.
|
||||
2. **Ability to independently version different aspects**: For example, one may like to get the change history of all the `ownership metadata` independent of the changes made to `schema metadata` for a dataset.
|
||||
2. **Ability to independently version different aspects**: For example, one may like to get the change history of all the "ownership metadata" independent of the changes made to "schema metadata" for a dataset.
|
||||
3. **Help with rest.li endpoint modeling**: While it’s not required to have 1:1 mapping between rest.li endpoints and metadata aspects,
|
||||
it’d follow this pattern naturally, which means one will end up with smaller, more modular, endpoints instead of giant ones.
|
||||
|
||||
@ -48,4 +48,4 @@ The [relationship](relationship.md) section explains how this relationship can b
|
||||
}
|
||||
]
|
||||
}
|
||||
```
|
||||
```
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user