Return-Path: Delivered-To: apmail-hadoop-hbase-user-archive@minotaur.apache.org Received: (qmail 24629 invoked from network); 3 Apr 2009 14:25:42 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Apr 2009 14:25:42 -0000 Received: (qmail 57720 invoked by uid 500); 3 Apr 2009 14:25:42 -0000 Delivered-To: apmail-hadoop-hbase-user-archive@hadoop.apache.org Received: (qmail 57693 invoked by uid 500); 3 Apr 2009 14:25:42 -0000 Mailing-List: contact hbase-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hbase-user@hadoop.apache.org Delivered-To: mailing list hbase-user@hadoop.apache.org Received: (qmail 57683 invoked by uid 99); 3 Apr 2009 14:25:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 14:25:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com designates 74.125.44.29 as permitted sender) Received: from [74.125.44.29] (HELO yx-out-2324.google.com) (74.125.44.29) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 14:25:35 +0000 Received: by yx-out-2324.google.com with SMTP id 3so658152yxj.29 for ; Fri, 03 Apr 2009 07:25:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=b+OaSxPFL6k1KkHXvmQmQw6IkkzUsNSGKewnViYqO6E=; b=E37N7ePb0OiD8JuuY9Eo6ZbroxeFQE8PjzrBTyR/DTWprMoJYXQOTFjq7wuMmbdYqi 5N1MJ8eStt2baDITsO/GmCgSxB8uz9RNBmVvBzZ3UFLB/1GXL0rp/HVbvJPZfS0bBZjI SwPRlWu6Q19Yb494LRXrdTTrE9zYEjW3Uq49g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=T28k6AJLiix/sFnirfs/W1/2zeEjvPiZGhvrupZDv721aao+3aOUIu2lzDgmlmtZ9r z04PkF1Jsh5Ha9jJ56WemVIXbphFCj1FIcUYgRDwhRrcGC94YtmjnZhWowpUKV+6bLGt m9LTThedqENtGm0DLvrFRfM+zlWYYSybRFkdo= MIME-Version: 1.0 Sender: saint.ack@gmail.com Received: by 10.100.8.17 with SMTP id 17mr1287024anh.108.1238768714197; Fri, 03 Apr 2009 07:25:14 -0700 (PDT) In-Reply-To: <9148E2AE-8836-4AA6-82BE-03BE330CC7BE@s7labs.com> References: <7c962aed0904020012g281e3200sbb7c83ce039dc05f@mail.gmail.com> <7c962aed0904020013i9aa8e1avabd7c067497d5090@mail.gmail.com> <9148E2AE-8836-4AA6-82BE-03BE330CC7BE@s7labs.com> Date: Fri, 3 Apr 2009 16:25:14 +0200 X-Google-Sender-Auth: d3fb457c489cb211 Message-ID: <7c962aed0904030725r612ae0eeh134df9477bd52ec6@mail.gmail.com> Subject: Re: financial time series database From: stack To: hbase-user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001485f86f4e2b3fd40466a7511e X-Virus-Checked: Checked by ClamAV on apache.org --001485f86f4e2b3fd40466a7511e Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On Thu, Apr 2, 2009 at 9:53 PM, Wesley Chow wrote: > > Are there technical limitations to the number of different timestamps per > cell? If it's the case that you're doing to be dealing with tens of > thousands to millions of entries all at one cell, perhaps you should check > that to make sure it's a reasonable use case. The examples in the HBase docs > number the timestamps in single digits, and I don't recall any mention of > very large numbers. Agreed. I'd imagine that tens of thousands of versions currently would suffer in same manner as tens of thousands of columns -- hbase running increasingly slower as count went up, at least until we address HBASE-867 "If millions of columns in a column family, hbase scanner won't come up " St.Ack --001485f86f4e2b3fd40466a7511e--