Exasol 5.0 now allows you to run Loading...Java code Loading...in-memory and parallel.
Some people just plain don’t like SQL.
OK, maybe they don’t dislike it – it’s just that it’s totally not the way they see the world.
The Loading...Hadoop guys and gals, for example, live and breathe Loading...java/">Loading...Java. To them, life is a class that is loaded into the Loading...virtual machine that we call reality and people are but objects constructed from that class, who run until their internal reference is dropped and they are finally collected by the great Garbage Collector in the sky.
Some problems fit the SQL mindset and some plainly don’t – the “simple” Loading...Hadoop wordcount example is only simple in Loading...Java. In SQL it is a horrid piece of code that looks bad and runs even worse. Anyone who has ever tried to “sessionise” weblogs will also be aware that SQL isn’t the tool for every job.
That’s why in Exasol 5, we’ve introduced the ability to write User-Defined Functions (Loading...UDFs) in Loading...Java. Previously you could have used Lua, Loading...Python or R – and this is would have been fine, except that if you already had a lot of existing Loading...Java code, you would have had to rewrite it in one of these other languages in order to run it on Exasol.
Now that we support Loading...Java Loading...UDFs, you can just cut and paste this existing code into a Loading...Java UDF template, importing any external packages you need without limit.
And then this Loading...Java code will run parallel and Loading...in-memory, just like any SQL function.
And so you don’t need to choose between SQL and Loading...Java – with Exasol 5 you can have both (and Lua and Loading...Python and R too!)