From issues-return-5779-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Tue Apr 9 08:17:02 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id CC234180763 for ; Tue, 9 Apr 2019 10:17:01 +0200 (CEST) Received: (qmail 55129 invoked by uid 500); 9 Apr 2019 07:57:23 -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 55027 invoked by uid 99); 9 Apr 2019 07:57:23 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2019 07:57:23 +0000 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 6DDAEE02D1 for ; Tue, 9 Apr 2019 08:17:00 +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 2F0FE2459B for ; Tue, 9 Apr 2019 08:17:00 +0000 (UTC) Date: Tue, 9 Apr 2019 08:17:00 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (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=16813110#comment-16813110 ] Lars Hofhansl commented on PHOENIX-5090: ---------------------------------------- Something is not right. I see partial data sometimes (i.e. when I commit a larger transaction - 50-60k rows in one session - I sometime see some rows first and then the rest of the rows). Only when issuing a commit with autocommit=off. When I see it it's always off by a very small number. I doubt anything is wrong with Omid, so there's a problem with this change in Phoenix. I don't quite understand that, yet, since Phoenix does the very same if you have autocommit off and you do a query after an upsert. In that case it sends all uncommitted data to the server. > 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 > Assignee: Lars Hofhansl > Priority: Major > Attachments: 5090-looksee.txt, 5090-v1.txt, 5090-v2.txt, 5090-v3.txt > > > 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)