Renaming configureMetadataRepository to configureBuiltinMetadataRepository
Adding a new function configurePluginMetadataRepository (different api call for ! graph/inmem)
Adding conditional in a new configureMetadataRepository which looks for a repo name of 'xtdb-inmemory'. If set, passes an appropriate configuration body
Mechanism can be extended for persistence
The value used for repository is already externalized by the OS environment variable repositoryType making it easy to use locally & in k8s
No change to default (yet)
This approach was taken instead of adding logic in the configuration notebook so as to limit the scope of changes since the lab notebook only needs to offer an opinionated setup
Testing
Notebooks all start, though a few anomolies noticed (building a data catalog), but these will be followed up separately - due to different xtdb behaviour, not a configuration issue
react UI working ok
See #41 - a subsequent PR will enable a persistent option, and add support in other repos to make this easier. A HA option requires significantly more changes, potentially using the in-development operator
In summary to use
Download or build XTDB connector and ensure it is in LOADER_PATH
export repositoryType=xtdb-inmemory
run jupyter/charts as normal
Little steps towards broader, easier, XTDB use.
@mandy-chessell @dwolfson Does this approach make sense.
If so we can merge, and I'll raise issues on any xtdb anomalies before looking at a simple persistent option
Signed-off-by: Nigel Jones nigel.l.jones+git@gmail.com
This has been implemented by
Testing
See #41 - a subsequent PR will enable a persistent option, and add support in other repos to make this easier. A HA option requires significantly more changes, potentially using the in-development operator
In summary to use Download or build XTDB connector and ensure it is in LOADER_PATH export repositoryType=xtdb-inmemory run jupyter/charts as normal
Little steps towards broader, easier, XTDB use.
@mandy-chessell @dwolfson Does this approach make sense.
If so we can merge, and I'll raise issues on any xtdb anomalies before looking at a simple persistent option