Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9821C8150 for ; Wed, 10 Aug 2011 05:37:54 +0000 (UTC) Received: (qmail 33411 invoked by uid 500); 10 Aug 2011 05:37:48 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 32868 invoked by uid 500); 10 Aug 2011 05:37:40 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 32860 invoked by uid 99); 10 Aug 2011 05:37:38 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 05:37:38 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of saravana.hadoop@gmail.com designates 209.85.210.43 as permitted sender) Received: from [209.85.210.43] (HELO mail-pz0-f43.google.com) (209.85.210.43) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Aug 2011 05:37:30 +0000 Received: by pzk1 with SMTP id 1so1776597pzk.30 for ; Tue, 09 Aug 2011 22:37:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=P8GKE8CE+V59GA1HgeAqLzLBWzXesTX6qB2Y7mZpmlA=; b=XzvePYn2LXqJ47TdAX8e090bNOEOCIaVHdYOCc9EYrvl+wvJ+/izXaCjJIGDeGf6Lx 58vccymnLQE57wo9Dhl1nmS+GtbvtYgbtzHYi4HEhvN2ohs8OieLIWSP8LcsJtfKRhbo w3gbgOAI2OV+HtZxZQo4kKsmk7BclUXKY/sFQ= MIME-Version: 1.0 Received: by 10.143.67.19 with SMTP id u19mr7256940wfk.158.1312954629287; Tue, 09 Aug 2011 22:37:09 -0700 (PDT) Received: by 10.68.51.37 with HTTP; Tue, 9 Aug 2011 22:37:09 -0700 (PDT) In-Reply-To: References: Date: Wed, 10 Aug 2011 11:07:09 +0530 Message-ID: Subject: Re: Derby with Hadoop --Why? From: Saravana Kumar To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=000e0cd2476448efbe04aa201231 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd2476448efbe04aa201231 Content-Type: text/plain; charset=ISO-8859-1 Thanks For the Explanation but needs some clarity as well Do you mean to say all the Information required to run a map/reduce job is effectively stored in derby. It means hadoop(not Ecosystem) uses Derby? On Tue, Aug 9, 2011 at 5:52 PM, Michael Segel wrote: > > Derby? > > First a little history... > Derby started out long ago as Cloudscape. Cloudscape was bought by > Informix. Informix was bought by IBM. IBM didn't understand Cloudscape and > decided to open source the project under APL. Hence Derby was born. > > Derby is an excellent lightweight 100% java database. So when you have a > Java framework, using Derby makes a lot of sense. Derby is used to persist > some environment information and I believe its used in part of some of the > unit testing. > > Where Derby has been replaced by MySQL is when someone wanted a multi-user > database and they were more comfortable with MySQL than they were with > Derby. (Hint: Derby can be started as an embedded single user database, or > as a multi-user database by changing its invocation at startup. ;-) > > So I would guess the initial reason to go with Derby was that its released > under APL and there were no licensing issues. ;-) > > > > Date: Tue, 9 Aug 2011 15:17:35 +0530 > > Subject: Derby with Hadoop --Why? > > From: saravana.hadoop@gmail.com > > To: general@hadoop.apache.org > > > > Hi > > > > What is the significance of Derby in Hadoop Project. > > Why people are using Derby along with Hadoop > > > > Regards > > Saravana Kumar.J > > --000e0cd2476448efbe04aa201231--