I think we can refer to external datasets in our documentation and load them on demand when we run against them. That way we do not have to store them either.
Jeff Jeff Eastman, Ph.D. Windward Solutions Inc. +1.415.298.0023 http://windwardsolutions.com http://jeffeastman.blogspot.com > -----Original Message----- > From: Isabel Drost [mailto:[EMAIL PROTECTED] > Sent: Sunday, March 30, 2008 1:24 PM > To: [email protected] > Subject: Re: Undergrad stud interested in GSoC > > On Sunday 30 March 2008, Jeff Eastman wrote: > > I'm working with my colleagues at CollabNet who have expressed interest > in > > providing us some EC2 time for this sort of testing. > > Sounds great to me. > > > > They are working on EC2 deployment of Hadoop using their CUBiT machine > > allocation environment and the quid pro quo would be that we help them > > exercise this tool. > > I think that's only fair, for us getting some real world experimental > results. > > > > I also think it is important that we build up some example datasets to > test > > our existing code > > +1 I don't know the exact licensing of existing datasets, maybe we could > use > them for checking as long as we do not ship them as part of our > code/project? > > Isabel > > > > -- > [FORTRAN] will persist for some time -- probably for at least the next > decade. -- T. Cheatham > |\ _,,,---,,_ Web: <http://www.isabel-drost.de> > /,`.-'`' -. ;-;;,_ > |,4- ) )-,_..;\ ( `'-' > '---''(_/--' `-'\_) (fL) IM: <xmpp://[EMAIL PROTECTED]>
