Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C9AE1200C30 for ; Tue, 7 Mar 2017 12:50:42 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C8274160B82; Tue, 7 Mar 2017 11:50:42 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1EE4E160B68 for ; Tue, 7 Mar 2017 12:50:41 +0100 (CET) Received: (qmail 50256 invoked by uid 500); 7 Mar 2017 11:50:41 -0000 Mailing-List: contact issues-help@carbondata.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@carbondata.incubator.apache.org Delivered-To: mailing list issues@carbondata.incubator.apache.org Received: (qmail 50245 invoked by uid 99); 7 Mar 2017 11:50:41 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2017 11:50:41 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id DD762180BB2 for ; Tue, 7 Mar 2017 11:50:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.547 X-Spam-Level: X-Spam-Status: No, score=-1.547 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id kEd99LdAsapT for ; Tue, 7 Mar 2017 11:50:40 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id DBB525FB5B for ; Tue, 7 Mar 2017 11:50:39 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 4BD72E05B1 for ; Tue, 7 Mar 2017 11:50:38 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id F34A02416C for ; Tue, 7 Mar 2017 11:50:37 +0000 (UTC) Date: Tue, 7 Mar 2017 11:50:37 +0000 (UTC) From: "Liang Chen (JIRA)" To: issues@carbondata.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CARBONDATA-745) Does carbondata apply to scenes that need to sort historical and current data? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 07 Mar 2017 11:50:42 -0000 [ https://issues.apache.org/jira/browse/CARBONDATA-745?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 15899315#comment-15899315 ]=20 Liang Chen commented on CARBONDATA-745: --------------------------------------- First, see if i understood it: There is a sorted table, and will generate a new table with real-time data.= the two tables have one same column(eg: name is key), you want to do join = by column "key" to merge two tables into one table, complete sort operatio= n along with joining operation , is it correct ? During loading data, can't do like that. For two different table data, you = must manually do join operation as per your requires. Regards Liang =20 > Does carbondata apply to scenes that need to sort historical and current = data? > -------------------------------------------------------------------------= ----- > > Key: CARBONDATA-745 > URL: https://issues.apache.org/jira/browse/CARBONDATA-745 > Project: CarbonData > Issue Type: Wish > Components: data-load > Affects Versions: 1.0.0-incubating > Reporter: ke xu > Priority: Minor > > Does carbondata apply to scenes that need to sort historical and current = data? > Now there is a new scene that needs to sort the current data and historic= al data in real time according to certain rules,and returns the sorted data= when querying. > It's just like hbase put data sorted by rowkey. > We want to sort the data when we load the data without having to spend ex= tra time to sort=E3=80=82 > Is it suitable for this scene? -- This message was sent by Atlassian JIRA (v6.3.15#6346)