From issues-return-95106-archive-asf-public=cust-asf.ponee.io@ignite.apache.org Thu Apr 11 13:27: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 BB624180763 for ; Thu, 11 Apr 2019 15:27:01 +0200 (CEST) Received: (qmail 75472 invoked by uid 500); 11 Apr 2019 13:27:01 -0000 Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ignite.apache.org Delivered-To: mailing list issues@ignite.apache.org Received: (qmail 75441 invoked by uid 99); 11 Apr 2019 13:27:01 -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; Thu, 11 Apr 2019 13:27:01 +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 829ECE2909 for ; Thu, 11 Apr 2019 13:27: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 1E1502459B for ; Thu, 11 Apr 2019 13:27:00 +0000 (UTC) Date: Thu, 11 Apr 2019 13:27:00 +0000 (UTC) From: "Ignite TC Bot (JIRA)" To: issues@ignite.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (IGNITE-11314) JDBC Thin: add transaction-scoped flag to JdbcHandler's responses. 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/IGNITE-11314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815415#comment-16815415 ] Ignite TC Bot commented on IGNITE-11314: ---------------------------------------- {panel:title=--> Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity *--> Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3562248&buildTypeId=IgniteTests24Java8_RunAll] > JDBC Thin: add transaction-scoped flag to JdbcHandler's responses. > ------------------------------------------------------------------ > > Key: IGNITE-11314 > URL: https://issues.apache.org/jira/browse/IGNITE-11314 > Project: Ignite > Issue Type: Task > Components: jdbc > Reporter: Alexander Lapin > Assignee: Alexander Lapin > Priority: Major > Labels: iep-23 > Time Spent: 10m > Remaining Estimate: 0h > > Within the context of best effort affinity, and particular, multi-connections, it's necessary to use "sticky" connections in case of "next page" requests, transactions, streaming and copy. > In order to implement transaction-based-sticky use case we need to know whether we are in transnational scope or not. So JdbcRequestHandler ought to retrieve query execution plan, analyse whether transaction exists and propagate corresponding flag to the client. -- This message was sent by Atlassian JIRA (v7.6.3#76005)