Open lukashornych opened 1 week ago
We will also need to support unsafe mode for evitaQL when querying data. It could be just a parameter in input object when querying data. evitaLab would use by default unsafe mode. There could than be a switch in evitaQL console to switch to safe mode for debugging or something.
There will be new methods in gRPC services:
queryUnsafe
queryOneUnsafe
queryListUnsafe
We want to explicitly distinguish, so the developer using it doesn't accidentally use unsafe mode.
We will need several internal APIs for evitaLab management tooling. Ideally, we would want to use gRPC with gRPC-web for it.
API for backups
API for JFR
API for query recordings