http://spark.incubator.apache.org/ https://github.com/amplab/shark/wiki
Shark is a lightning fast SQL implementation built on top of Apache Spark (originating out of the Berkeley AMP Lab) Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Adam Estrada <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Thursday, August 29, 2013 8:41 PM To: "[email protected]" <[email protected]> Subject: Re: Current work: AbstractIdentifiedObject >Interesting about Shark. Can you post the link and how you think it could >be used? > > >On Thu, Aug 29, 2013 at 9:19 PM, Mattmann, Chris A (398J) < >[email protected]> wrote: > >> We should try and integrate with shark from the amp lab... >> >> Sent from my iPhone >> >> On Aug 29, 2013, at 5:26 PM, "Martin Desruisseaux" < >> [email protected]> wrote: >> >> > Le 30/08/13 02:11, Travis L Pinney a écrit : >> >> +1 on the approach you used for GeoTK and what is proposed for SIS. >> Would >> >> it be possible have it work "in memory" without having to write out >>to >> disk >> >> for a use case like Hadoop? >> > >> > Yes, both Derby and HSQL allows "in memory database". However given >>the >> memory consumption for this relatively large database and the cost of >> recreating the tables on system start, I don't know if the advantages >>would >> be greater than the inconvenient... But it would be at user choice >>anyway. >> > >> > Martin >> > >>
