Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4C5111882D for ; Thu, 29 Oct 2015 16:05:33 +0000 (UTC) Received: (qmail 50173 invoked by uid 500); 29 Oct 2015 16:05:28 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 50137 invoked by uid 500); 29 Oct 2015 16:05:28 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 50096 invoked by uid 99); 29 Oct 2015 16:05:28 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Oct 2015 16:05:28 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D6C7C2C1F5D for ; Thu, 29 Oct 2015 16:05:27 +0000 (UTC) Date: Thu, 29 Oct 2015 16:05:27 +0000 (UTC) From: "Adam Holmberg (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CASSANDRA-10513) Update cqlsh for new driver execution API 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/CASSANDRA-10513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14980443#comment-14980443 ] Adam Holmberg edited comment on CASSANDRA-10513 at 10/29/15 4:04 PM: --------------------------------------------------------------------- In addition to the issues Sam mentioned, there are the linked issues CASSANDRA-7645 -(which this resolves)-, and CASSANDRA-9813 (which depends on these changes). The urgency of the 2.2 patch here would be the same as the dependent tickets mentioned here and above. I don't see any issue waiting for the driver release to integrate for Cassandra 2.2. We will need to patch 3.0 sooner in support of CASSANDRA-10365 (this may be applied at the same time as the driver is updated for that ticket). was (Author: aholmber): In addition to the issues Sam mentioned, there are the linked issues CASSANDRA-7645 (which this resolves), and CASSANDRA-9813 (which depends on these changes). The urgency of the 2.2 patch here would be the same as the dependent tickets mentioned here and above. I don't see any issue waiting for the driver release to integrate for Cassandra 2.2. We will need to patch 3.0 sooner in support of CASSANDRA-10365 (this may be applied at the same time as the driver is updated for that ticket). > Update cqlsh for new driver execution API > ----------------------------------------- > > Key: CASSANDRA-10513 > URL: https://issues.apache.org/jira/browse/CASSANDRA-10513 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Adam Holmberg > Assignee: Paulo Motta > Priority: Minor > Labels: cqlsh > Fix For: 2.2.x, 3.0.x > > Attachments: 10513-2.1.txt, 10513-2.2.txt, 10513.txt > > > The 3.0 Python driver will have a few tweaks to the execution API. We'll need to update cqlsh in a couple of minor ways. > [Results are always returned as an iterable ResultSet|https://datastax-oss.atlassian.net/browse/PYTHON-368] > [Trace data is always attached to the ResultSet|https://datastax-oss.atlassian.net/browse/PYTHON-318] (instead of being attached to a statement) -- This message was sent by Atlassian JIRA (v6.3.4#6332)