From dev-return-23227-apmail-phoenix-dev-archive=phoenix.apache.org@phoenix.apache.org Fri Dec 4 21:07:13 2015 Return-Path: X-Original-To: apmail-phoenix-dev-archive@minotaur.apache.org Delivered-To: apmail-phoenix-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C83AB18A8B for ; Fri, 4 Dec 2015 21:07:13 +0000 (UTC) Received: (qmail 94263 invoked by uid 500); 4 Dec 2015 21:07:13 -0000 Delivered-To: apmail-phoenix-dev-archive@phoenix.apache.org Received: (qmail 94209 invoked by uid 500); 4 Dec 2015 21:07:13 -0000 Mailing-List: contact dev-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 dev@phoenix.apache.org Received: (qmail 94198 invoked by uid 99); 4 Dec 2015 21:07:13 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 21:07:13 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 0D2F71A5F88 for ; Fri, 4 Dec 2015 21:07:13 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 0.426 X-Spam-Level: X-Spam-Status: No, score=0.426 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.554] autolearn=disabled Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id OLz6pxNEDpwo for ; Fri, 4 Dec 2015 21:07:12 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with SMTP id 5902323061 for ; Fri, 4 Dec 2015 21:07:12 +0000 (UTC) Received: (qmail 91493 invoked by uid 99); 4 Dec 2015 21:07:11 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Dec 2015 21:07:11 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 59D922C0453 for ; Fri, 4 Dec 2015 21:07:11 +0000 (UTC) Date: Fri, 4 Dec 2015 21:07:11 +0000 (UTC) From: "James Taylor (JIRA)" To: dev@phoenix.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (PHOENIX-2411) Allow Phoenix to participate as transactional component 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-2411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] James Taylor reassigned PHOENIX-2411: ------------------------------------- Assignee: James Taylor > Allow Phoenix to participate as transactional component > ------------------------------------------------------- > > Key: PHOENIX-2411 > URL: https://issues.apache.org/jira/browse/PHOENIX-2411 > Project: Phoenix > Issue Type: Improvement > Reporter: James Taylor > Assignee: James Taylor > Fix For: 4.7.0 > > > Frameworks such as Cask's CDAP support a means of individual components to participate in a transaction. To support this, Phoenix would need to: > - Provide a means of passing in the serialized state of a transaction as a connection property. An easy way to do this is to base64 encode the byte[] of the serialized transaction. > - Provide a statement or statements to run and flush any uncommitted data after execution. The caller could use the Statement.addBatch(String sqlStmt) multiple times and call Statement.executeBatch() to run more than one statement at a time. > - Return back the potentially new transaction state (as checkpointing may have been required as a result of running the batch of statements). > In addition, for our query server to remain stateless, we'll need this type of behavior, as it's possible that a load balancer in front of the query server would route an UPSERT or DELETE to a different query server node. -- This message was sent by Atlassian JIRA (v6.3.4#6332)