From dev-return-43890-archive-asf-public=cust-asf.ponee.io@ignite.apache.org  Wed Jan  9 16:52:12 2019
Return-Path: <dev-return-43890-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
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 E9831180669
	for <archive-asf-public@cust-asf.ponee.io>; Wed,  9 Jan 2019 16:52:11 +0100 (CET)
Received: (qmail 82035 invoked by uid 500); 9 Jan 2019 15:52:11 -0000
Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@ignite.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@ignite.apache.org>
List-Post: <mailto:dev@ignite.apache.org>
List-Id: <dev.ignite.apache.org>
Reply-To: dev@ignite.apache.org
Delivered-To: mailing list dev@ignite.apache.org
Received: (qmail 82024 invoked by uid 99); 9 Jan 2019 15:52:10 -0000
Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2019 15:52:10 +0000
Received: from mail-yw1-f49.google.com (mail-yw1-f49.google.com [209.85.161.49])
	by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id 231E32532
	for <dev@ignite.apache.org>; Wed,  9 Jan 2019 15:52:10 +0000 (UTC)
Received: by mail-yw1-f49.google.com with SMTP id h32so3138157ywk.2
        for <dev@ignite.apache.org>; Wed, 09 Jan 2019 07:52:10 -0800 (PST)
X-Gm-Message-State: AJcUukc1LQ1n5xhYgEnfjvsYFeqWhrM+uZOC/9xZawnMk4zK2DkSZplp
	LjPj87LC+uN+ssskiyTWks1gXM+fT+BxD1f9RV5H8Q==
X-Google-Smtp-Source: ALg8bN5LywOI8nrExN64CoHrnflXS+4BM7UG1DDzlmE1Xx/N4+CBMSjizFtSVuDYONnsU4wm0x6XmfsIBjAgy9xqOU8=
X-Received: by 2002:a81:441f:: with SMTP id r31mr6252028ywa.48.1547049129754;
 Wed, 09 Jan 2019 07:52:09 -0800 (PST)
MIME-Version: 1.0
References: <CAN8tF9ewzuLfgJg8Prj9=wiTEdPx_Hg252bpKpXCHxejtu5HrA@mail.gmail.com>
 <CALH+G9prP9vNcEwvefN7ZQL4oicghzL7s=f9MDzCUT8sxLcJxw@mail.gmail.com>
 <CAN8tF9cvb6+=1-LVrdXSPJN_yVKoLZuK0XX4NqQvmGoSas13LQ@mail.gmail.com>
 <CAGt6o8kchYqhAoxseDVHZum0ukAyibQag=qc44W-wOD7f1BjBg@mail.gmail.com>
 <CAN8tF9fQ2xfsEJSpL_3xvj-9OhDP=Hg3g+5oPSe4mBaUbGUrnw@mail.gmail.com> <CAN8tF9fB0OoST_rCJ4QWtprqQx1sfLQg_t_s7=ujGqrS=FFfyg@mail.gmail.com>
In-Reply-To: <CAN8tF9fB0OoST_rCJ4QWtprqQx1sfLQg_t_s7=ujGqrS=FFfyg@mail.gmail.com>
From: Alexey Kuznetsov <akuznetsov@apache.org>
Date: Wed, 9 Jan 2019 22:51:57 +0700
X-Gmail-Original-Message-ID: <CALH+G9qQJjZR6CUy8u+Wu=1kFWpb7F_A_N3d8xWwgaVJ1WquXw@mail.gmail.com>
Message-ID: <CALH+G9qQJjZR6CUy8u+Wu=1kFWpb7F_A_N3d8xWwgaVJ1WquXw@mail.gmail.com>
Subject: Re: Query history statistics API
To: dev <dev@ignite.apache.org>
Content-Type: multipart/alternative; boundary="000000000000d45f88057f087184"

--000000000000d45f88057f087184
Content-Type: text/plain; charset="UTF-8"

Yuriy,

I think, for the sake of code simplicity we can track all queries.
in other case we will need to parse SQL text and detect that current query
is the EXPLAIN one.

-- 
Alexey Kuznetsov

--000000000000d45f88057f087184--