From user-return-14173-apmail-hbase-user-archive=hbase.apache.org@hbase.apache.org Wed Dec 01 08:24:40 2010 Return-Path: Delivered-To: apmail-hbase-user-archive@www.apache.org Received: (qmail 70041 invoked from network); 1 Dec 2010 08:24:40 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 1 Dec 2010 08:24:40 -0000 Received: (qmail 31086 invoked by uid 500); 1 Dec 2010 08:24:38 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 30951 invoked by uid 500); 1 Dec 2010 08:24:38 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 30228 invoked by uid 500); 1 Dec 2010 08:24:37 -0000 Delivered-To: apmail-hadoop-hbase-user@hadoop.apache.org Received: (qmail 30115 invoked by uid 99); 1 Dec 2010 08:24:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Dec 2010 08:24:37 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.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 futureha@gmail.com designates 209.85.213.48 as permitted sender) Received: from [209.85.213.48] (HELO mail-yw0-f48.google.com) (209.85.213.48) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Dec 2010 08:24:29 +0000 Received: by ywo32 with SMTP id 32so262352ywo.35 for ; Wed, 01 Dec 2010 00:24:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=9r/hYRTf8LyADsAizcai7w4D62ztQdP4DcLlJNKB6zM=; b=dWxvt3ESe9Ir8GZMDOMVhpEHruxcBHWBHGuRhGhFj6Wx9X3j0kL3QVfmJ7OwuXgrmg k/Evwdraa7sEDSXXXkDsJ2Xw4o37HmStMOtNJk2z6zbgwWbY4+ROT14WzhTN8oe3WFHF SwwQ1uWO+H/ABlqMUsiPKxLmZOHUmgsw6h/qs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=j3T1Ta16kyXZZLPLj9K2cCf24AvpKSTtepPX1IjnXq00KCLe9ia/CpPs4kUl7lQVSf DgEuSqHoEraN3XgkL9aJPC8sF0/3+2kGpqxlc0qGBieOcikhjeHguUxCRz18af5qlaK7 Ggyo+l2I0dKrQSqZsDgjj2feGapnX1RZRL9UM= MIME-Version: 1.0 Received: by 10.101.81.15 with SMTP id i15mr2546767anl.206.1291191848837; Wed, 01 Dec 2010 00:24:08 -0800 (PST) Received: by 10.100.255.11 with HTTP; Wed, 1 Dec 2010 00:24:08 -0800 (PST) In-Reply-To: References: Date: Wed, 1 Dec 2010 16:24:08 +0800 Message-ID: Subject: Re: something wrong with hbase mapreduce From: =?UTF-8?B?5qKB5pmv5piO?= To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001636ed67767ca18f04965507eb X-Virus-Checked: Checked by ClamAV on apache.org --001636ed67767ca18f04965507eb Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable i found that if i didnt control timestamp of the put mapreduce can run, otherwise just one time mapreduce. the question is i scan by timestamp to get my data so to put timestamp is my scan thing. any ideas ? thanks. 2010/12/1 =E6=A2=81=E6=99=AF=E6=98=8E > Hi,i found a problem in my hbase mapreduce case. > > when first running mapreduce TableMapReduceUtil runs ok. > > and i use hbase shell to delete some data from the table that mapreduce o= ne > . > > then ran mapreduce to insert some new data. > > no thing data changed, mapreduce didnt work. > > after that i drop the table and recreate it > > run mapreduce again ,data inserted successful. > > what happen to mapreduce . > > Is it only can insert table just one time? > --001636ed67767ca18f04965507eb--