Github user LosD commented on the issue:
https://github.com/apache/metamodel/pull/120
Yeah, that might make sense, though I'd only see an advantage in the
non-Docker case (which is of course an entirely valid case... Easy to get
Docker-tunnel-vision these days ð). But in many cases I think there's often
advantages to keeping datastores separate. For the Docker case, there is likely
performance improvements to using Kubernetes or Swarm clustering.
It would be super nice if the API could somehow make multiple datastores
possible (and I guess de/registering datastores, though I'd love to cut that
lard as well and just register it/them on startup or image create/run in the
Docker case), and still making single datastore access as simple as possible.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
