From issues-return-3794-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Sat Jan 5 20:10:05 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id A200B180645 for ; Sat, 5 Jan 2019 20:10:04 +0100 (CET) Received: (qmail 45893 invoked by uid 500); 5 Jan 2019 19:10:03 -0000 Mailing-List: contact issues-help@phoenix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@phoenix.apache.org Delivered-To: mailing list issues@phoenix.apache.org Received: (qmail 45884 invoked by uid 99); 5 Jan 2019 19:10:03 -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; Sat, 05 Jan 2019 19:10:03 +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 644BC180E85 for ; Sat, 5 Jan 2019 19:10:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] 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 vhdTU3QACj2b for ; Sat, 5 Jan 2019 19:10:02 +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 1383E5F577 for ; Sat, 5 Jan 2019 19:10:02 +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 65B9AE263B for ; Sat, 5 Jan 2019 19:10:01 +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 7183E25448 for ; Sat, 5 Jan 2019 19:10:00 +0000 (UTC) Date: Sat, 5 Jan 2019 19:10:00 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (PHOENIX-5090) Discuss: Allow transactional writes without buffering the entire transaction on the client. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-5090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16734982#comment-16734982 ] Lars Hofhansl edited comment on PHOENIX-5090 at 1/5/19 7:09 PM: ---------------------------------------------------------------- [~yonigo] would it good to have ROW mode? That would reduce the conflict size and also reduce the extra storage requirements. (Tephra has ROW and COLUMN modes) was (Author: lhofhansl): [~yonigo] would it good to have ROW mode? That would reduce the conflict size and also reduce the extra storage requirements. (Tephra has ROW or COLUMN modes) > Discuss: Allow transactional writes without buffering the entire transaction on the client. > ------------------------------------------------------------------------------------------- > > Key: PHOENIX-5090 > URL: https://issues.apache.org/jira/browse/PHOENIX-5090 > Project: Phoenix > Issue Type: Wish > Reporter: Lars Hofhansl > Priority: Major > > Currently it is not possible execute transactions in Phoenix that are too large to be buffered entirely on the client. > Both Tephra and Omid support writing uncommitted data to HBase immediately and at full speed. The client still needs to keep tracks of the rows changes for: > # Conflict detection > # (for Omid) writing the shadow cells > I'd like to do some brainstorming here. > * It should *always* be enough to only hold on to the changed rows (and columns?) only for _conflict resolution_ and free the rest from the client as soon as the uncommitted data is written to HBase. > * For the shadows cells we need only keep the rows changed, right? > * There are situations where we can avoid the client site buffering entirely (perhaps only for Tephra) when we declare a table or upsert not to participate in conflict resolution. > [~tdsilva], [~ohads], [~yonigo], [~jamestaylor], [~vincentpoon], more, better ideas? -- This message was sent by Atlassian JIRA (v7.6.3#76005)