Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 3 May 2016 23:33:12 +0000 (UTC)
From: "mck (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12964836.1462318369000.103752.1462318392817@Atlassian.JIRA>
In-Reply-To: <JIRA.12964836.1462318369000@Atlassian.JIRA>
References: <JIRA.12964836.1462318369000@Atlassian.JIRA> <JIRA.12964836.1462318369642@arcas>
Subject: [jira] [Created] (CASSANDRA-11706) Tracing payload not passed
 through newSession(..)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 May 2016 23:33:14 -0000

mck created CASSANDRA-11706:
-------------------------------

             Summary: Tracing payload not passed through newSession(..)
                 Key: CASSANDRA-11706
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11706
             Project: Cassandra
          Issue Type: Bug
            Reporter: mck
            Assignee: mck
            Priority: Minor


Caused by CASSANDRA-10392

There's a small bug in https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/tracing/Tracing.java#L153

{noformat}
    public UUID newSession(UUID sessionId, Map<String,ByteBuffer> customPayload)
    {
        return newSession(sessionId, TraceType.QUERY, Collections.EMPTY_MAP);
    }{noformat}

in that it passes on an {{EMPTY_MAP}} instead of the {{customPayload}}.

I've marked this as "minor" as custom tracing plugins can easily enough workaround it by also overriding the {{newSession(UUID sessionId, Map<String,ByteBuffer> customPayload)}} method.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)