Problem to Solve

At the moment Grakn user of the Docker container may not know how to capture logs from inside a running docker container - especially important when the run has failed.

Current Workaround

There may not be a clean one, but in a case, we could log into the docker container:

$ docker exec -it [container id] /bin/bash
$ cd /path/to/logs
$ [some how upload via 

https://github.com/awslabs/mxnet-model-server/blob/master/plugins/endpoints/src/main/java/software/amazon/ai/mms/plugins/endpoint/ExecutionParameters.java#L26

'max_request_size' seems to refer to bytes, not mb.

There are a bunch of links to the theory of NARs in the readme that link to a google site that is gone:
All links starting with: https://sites.google.com/site/narswang/

Right now, we restrict grammar to disallow statements such as match $x; get. When building with graql, this is still allowed (Graql.match(var("x")).get()) when it should not be.

Further restrictions are currently built into Grakn's match clause validation at runtime, but not checked elsewhere - such as match $x != $y; get; which does a n^2 scan of the database. We could push this into Gra

It is set to use only M/Z and RT as default right now.

• if only one file, more fields (especially sourceID, if given) could be used without problem
• if multiple files should be compared, make choice possible in KNIME (command line has this anyways), also show recommendations for this in the comparison node
• maybe add something to the command line, which will allow an educate gu