Closed aalexandrov closed 8 years ago
There are some classpath problems with ToolBox
and macros: SI-6636, that might be causing the issue of macro implementations not being found.
In the macro tests I did it the same way it's done in async (actually I took their package object). The surefire-plugin now has a parameter that sets the toolbox-classpath. Where else are macro implementations not being found?
@fschueler: @FelixNeutatz was having similar issues when testing on Spark standalone yesterday. We might have to initialize the toolbox in the runtime object with a -cp
parameter as you did for the tests.
@fschueler, that's a really good idea! I had a similar problem with Flink's createTypeInformation
in the Zeppelin interpreter, and I believe this will solve it. Will comment here after I try it out.
It solved this particular problem, but unfortunately there are still other classpath problems, (org.apache.flink.api.common.operators.util.UserCodeObjectWrapper
not being found). I'll investigate further. It also helps to initialize the ToolBox
as late as possible, if you want to add extra classpath entries in the mean time.
Unfortunately both emma.org
as well as emma-lang.org
are registered domains, so we're stuck with emma-language
(and the alias emmalanguage
). I'll rename the root package from eu.stratosphere.emma
to org.emmalanguage
once we approach the first release.
emma.la
would be free as well
TODOs:
org.emma???
,org.peel???
)