Re:Crunch – Go-based toolkit for ETL and feature extraction ...
by jondot on Wednesday November 19, 2014 @02:06PM
(#8631934)
Unfortunately the standard Java map/reduce interface will win out because the IPC is more efficient.
But then doing ETL that way becomes clumsy and painfully slow.
The idea is the use rapid tools to do the same job.
Streaming is then one step higher across the happiness factor because you just use
Unix pipes to test your solution (and you can keep piping other tools as well as pipe Crunch processors over and over again)
Re:Crunch – Go-based toolkit for ETL and feature extraction ...
by jondot on Wednesday November 19, 2014 @12:26PM
(#8631290)
Actually yes!
Because I'm using Pig to "abstract" I/O you can use Pig to load data from anywhere (any format), it streams it into Crunch, and then again, Pig to save data to anywhere (any format).
https://crunch.apache.org/
https://github.com/jondot/hog
Eventhough streaming is 30% slower, Go's speed makes up for that and gives me up to 6x speed than the JRuby based solution.
The Ruby/JRuby solution has its place though, you have tens of thousands of valid ruby gems to use and it makes a very rapid development experience.
Unix pipes to test your solution (and you can keep piping other tools as well as pipe Crunch processors over and over again)