From issues-return-4003-archive-asf-public=cust-asf.ponee.io@phoenix.apache.org Mon Jan 14 13:31:04 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 27A95180608 for ; Mon, 14 Jan 2019 13:31:03 +0100 (CET) Received: (qmail 10185 invoked by uid 500); 14 Jan 2019 12:31: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 10176 invoked by uid 99); 14 Jan 2019 12:31: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; Mon, 14 Jan 2019 12:31: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 D173D180C0D for ; Mon, 14 Jan 2019 12:31:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, 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 dK0OE32b__JZ for ; Mon, 14 Jan 2019 12:31:01 +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 309CE5FBE6 for ; Mon, 14 Jan 2019 12:31:01 +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 ADD19E263B for ; Mon, 14 Jan 2019 12:31: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 46BC925590 for ; Mon, 14 Jan 2019 12:31:00 +0000 (UTC) Date: Mon, 14 Jan 2019 12:31:00 +0000 (UTC) From: "Yonatan Gottesman (JIRA)" To: issues@phoenix.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (PHOENIX-3623) Integrate Omid with Phoenix MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/PHOENIX-3623?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D16= 742003#comment-16742003 ]=20 Yonatan Gottesman commented on PHOENIX-3623: -------------------------------------------- Added a new patch to fix master (fixMaster.patch). I removed an unused file= "BaseRegionObserver.java" that omid used instead of using its own version = of this file. It seems unused but please say if this is bad. [~lhofhansl] Ill take a look at your issue > Integrate Omid with Phoenix > --------------------------- > > Key: PHOENIX-3623 > URL: https://issues.apache.org/jira/browse/PHOENIX-3623 > Project: Phoenix > Issue Type: New Feature > Reporter: Ohad Shacham > Assignee: Yonatan Gottesman > Priority: Major > Fix For: 4.15.0, 5.1.0 > > Attachments: 4.x-HBase-1.2.patch, 4.x-HBase-1.3.patch, 4.x-HBase-= 1.4.patch, batchResult.patch, fixMaster.patch, master.patch > > > The purpose of this Jira is to propose a work plan for connecting Omid to= Phoenix. > Each task of the following will be handled in a seperate sub Jira. Subtas= ks 4.* are related to augmenting Omid to support features required by Phoen= ix and therefore, their corresponding Jiras will appear under Omid and not = under Phoenix.=20 > Each task is completed by a commit. > Task 1: Adding transaction abstraction layer (TAL) - Currently Tephra cal= ls are integrated inside Phoenix code. Therefore, in order to support both = Omid and Tephra, we need to add another abstraction layer that later-on wil= l be connected to both Tephra and Omid. The first tasks is to define such a= n interface. > Task 2: Implement TAL functionality for Tephra.=20 > Task 3: Refactor Phoenix to use TAL instead of direct calls to Tephra. > Task 4: Implement Omid required features for Phoenix: > Task 4.1: Add checkpoints to Omid. A checkpoint is a point in a transacti= on where every write occurs after the checkpoint is not visible by the tran= saction. Explanations for this feature can be seen in [TEPHRA-96]. > Task 4.2: Add an option to mark a key as non-conflicting. The motivation = is to reduce the size of the write set needed by the transaction manager up= on commit as well as reduce the conflict detection work. > Task 4.3: Add support for transactions that never abort. Such transaction= s will only make other inflight transactions abort and will abort only in c= ase of a transaction manager failure.=20 > These transactions are needed for =E2=80=98create index=E2=80=99 and the = scenario was discussed in [TEPHRA-157] and [PHOENIX-2478]. Augmenting Omid = with this kind of transactions was also discussed in [OMID-56]. > Task 4.4: Add support for returning multiple versions in a scan. The use = case is described in [TEPHRA-134]. > Task 4.5: Change Omid's timestamp mechanism to return real time based tim= estamp, while keeping monotonicity. > Task 5: Implement TAL functionality for Omid. > Task 6: Implement performance tests and tune Omid for Phoenix use. This t= ask requires understanding of common usage scenarios in Phoenix as well as = defining the tradeoff between throughput and latency.=20 > Could you please review the proposed work plan? > Also, could you please let me know whether I missed any augmentation need= ed for Omid in order to support Phoenix operations? > I opened a jira [OMID-82] that encapsulates all Omid related development = for Phoenix. -- This message was sent by Atlassian JIRA (v7.6.3#76005)