community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Dunning <ted.dunn...@gmail.com>
Subject Re: Working on CouchDB or Hadoop
Date Thu, 20 May 2010 18:11:19 GMT
Sean,

Take a look at Cassandra, Hbase and Voldemort as well.  All provide
interesting variants on NOSQL capability.

On Thu, May 20, 2010 at 8:08 AM, Isabel Drost <isabel@apache.org> wrote:

> On 19.05.2010 Sean Bartell wrote:
> > I was looking for something to do over the summer, and the mentoring
> > program looked like a good choice. I've recently developed an interest
> > in filesystems and NoSQL databases, so I'm interested in working on
> > CouchDB or Hadoop. So far, I've messed around with CouchDB and submitted
> > a small patch for a bug. Is one of these projects a better candidate for
> > mentoring, or should I keep looking into both?
>
> I'd say that depends mostly on your own preference - namely in terms of
> programming language, the topics you are interested in. Usually it is
> easiest to
> get active at a project that you are actually using yourself.
>
> From your e-mail I conclude that you have some experience with CouchDB
> already.
> As for Hadoop: Did you have a look at the code base or the open issues in
> JIRA
> already? I guess you might want to have a closer look at the HDFS or HBase
> stuff.
>
>
> > Also, if I decide I want to work on one, is that project's mailing list
> the
> > right place to ask for project ideas?
>
> You might want to have a look at JIRA first - search for open issues you
> are
> interested in working on, there might be some issues marked as suitable for
> GSoC
> students. Those might be interesting for you as well.
>
> Going to the mailing lists and just asking for ideas of course is an idea
> as
> well. However working on Mahout and dealing with students there as well, I
> have
> the impression that students tend to be more successful when not told what
> to do
> but when choosing their tasks themselves.
>
> Isabel
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message