Getting started

35 views
Skip to first unread message

Christoffer Nilsson

unread,
Apr 12, 2017, 4:27:40 AM4/12/17
to notaql
Hello!

How do you specify the in/out engines to get started? For example the mongodb engine is reported as unsupported with this error:

Exception in thread "main" notaql.model.EvaluationException: Unsupported engines: mongodb
at notaql.engines.EngineService.getEngine(EngineService.java:63)
at notaql.parser.TransformationParser.getEngineEvaluator(TransformationParser.java:159)
at notaql.parser.TransformationParser.<init>(TransformationParser.java:62)
at notaql.parser.NotaQLExpressionParser.lambda$0(NotaQLExpressionParser.java:46)
at notaql.parser.NotaQLExpressionParser$$Lambda$1/1824835605.apply(Unknown Source)
at java.util.stream.ReferencePipeline$3$1.accept(Unknown Source)
at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(Unknown Source)
at java.util.stream.AbstractPipeline.copyInto(Unknown Source)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(Unknown Source)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(Unknown Source)
at java.util.stream.AbstractPipeline.evaluate(Unknown Source)
at java.util.stream.ReferencePipeline.collect(Unknown Source)
at notaql.parser.NotaQLExpressionParser.parse(NotaQLExpressionParser.java:47)
at notaql.NotaQL.evaluate(NotaQL.java:106)
at notaql.NotaQL.main(NotaQL.java:74)

It was run through Eclipse on Windows with the following arguments as found in one of the test files:
IN-ENGINE:mongodb(database_name <- 'test', collection_name <- 'test'), OUT-ENGINE:mongodb(database_name <- 'test', collection_name <- 'test'), OUT._id <- IN._id, OUT.$(IN.*.name()) <- IN.@

Thomas Lottermann

unread,
Apr 14, 2017, 12:46:51 PM4/14/17
to Christoffer Nilsson, notaql, Johannes Schildgen
Hi Christoffer!

It appears like you are not loading the MongoDB engine in your run. I'll look up my bash history once I am back from my business travel - haven't worked on this for 2 years now (since I graduated :D).
Please keep in mind that NotaQL is mostly a research prototype from the TU Kaiserslautern and will not receive much more maintanence in the future.
If you are just interested in getting it running and trying to run it for a single batch job it should work fine though, just don't build anything on it that needs to still work in a year or so - unless you want to be the one maintaining this project :)

--
You received this message because you are subscribed to the Google Groups "notaql" group.
To unsubscribe from this group and stop receiving emails from it, send an email to notaql+un...@googlegroups.com.
To post to this group, send email to not...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/notaql/f455f64b-ec6e-48e7-a7ce-c24b14b9b274%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Johannes

unread,
Apr 14, 2017, 3:21:31 PM4/14/17
to notaql
Hi Christoffer,

although NotaQL is a research prototype, we're happy about the future of the project. We extended the prototype by incremental computations and by supporting graph databases and data streams. I'm the contact person for the NotaQL project. So feel free to send me an email about your projects and what you want to use NotaQL for.

Regarding your problem: I never executed the tool on Windows. Which Java version do you have? I guess, it's a problem with the ServiceLoader. Look in the constructor method of notaql.engines.EngineService. It should find the Engine classes like MongoDBEngine because they are annotated with @AutoService(Engine.class). 

You're NotaQL script is correct.

Did you try the NotaQLGUI (in gui package)? Is the mongodb Engine shown in the Input-Engine list?

Best,
Johannes
Reply all
Reply to author
Forward
Message has been deleted
0 new messages