From dev-return-34469-archive-asf-public=cust-asf.ponee.io@ignite.apache.org  Tue May 15 00:49:19 2018
Return-Path: <dev-return-34469-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 AA002180627
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 15 May 2018 00:49:18 +0200 (CEST)
Received: (qmail 10001 invoked by uid 500); 14 May 2018 22:49:17 -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 9990 invoked by uid 99); 14 May 2018 22:49:17 -0000
Received: from mail-relay.apache.org (HELO mailrelay1-lw-us.apache.org) (207.244.88.152)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 May 2018 22:49:17 +0000
Received: from mail-ot0-f170.google.com (mail-ot0-f170.google.com [74.125.82.170])
	by mailrelay1-lw-us.apache.org (ASF Mail Server at mailrelay1-lw-us.apache.org) with ESMTPSA id C79D7C0A
	for <dev@ignite.apache.org>; Mon, 14 May 2018 22:49:16 +0000 (UTC)
Received: by mail-ot0-f170.google.com with SMTP id 15-v6so16217647otn.12
        for <dev@ignite.apache.org>; Mon, 14 May 2018 15:49:16 -0700 (PDT)
X-Gm-Message-State: ALKqPwf4XlN5qqmmSgP9cmEFBJs9v6fL0NpjTJ1S+AEZ7OXHdu9c78OB
	9gGqOC+WmWaEy5mno7WeNd9xJgEwgMTZaZOye1IfGA==
X-Google-Smtp-Source: AB8JxZqkU3NwNpkK2SqHnF40BPFWmelxIKXTcrtiMGMK6chUFNbXAfzO0tD8lU4/22rplOxRQinKLfiB/aUnxTFlPy0=
X-Received: by 2002:a9d:6190:: with SMTP id g16-v6mr8169643otk.4.1526338156116;
 Mon, 14 May 2018 15:49:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.201.58.47 with HTTP; Mon, 14 May 2018 15:48:35 -0700 (PDT)
In-Reply-To: <CAGt6o8kvQvNym=ZGquhJoVhF0M2QiCzqVHmTSL3z5TwSFTeQEw@mail.gmail.com>
References: <CA+0=VoWVUq9XARbZDZUTA3B1UyKEeq5bcqiKKBkYOJ2oYtX9tQ@mail.gmail.com>
 <CAGt6o8kvQvNym=ZGquhJoVhF0M2QiCzqVHmTSL3z5TwSFTeQEw@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Tue, 15 May 2018 01:48:35 +0300
X-Gmail-Original-Message-ID: <CA+0=VoWOcMe2r=EZUZ4CMU55D5Uwh=9khra2Pyd8xrk9Aa=QVw@mail.gmail.com>
Message-ID: <CA+0=VoWOcMe2r=EZUZ4CMU55D5Uwh=9khra2Pyd8xrk9Aa=QVw@mail.gmail.com>
Subject: Re: tracking SQL queries in 2.5
To: Vladimir Ozerov <vozerov@gridgain.com>
Cc: dev <dev@ignite.apache.org>
Content-Type: multipart/alternative; boundary="0000000000009a55b2056c324b96"

--0000000000009a55b2056c324b96
Content-Type: text/plain; charset="UTF-8"

On Mon, May 14, 2018 at 3:55 PM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Hi Dima,
>
> This is not that simple unfortunately. We need to build the whole
> infrastructure for cache-less SQL queries. This is not very complex, but
> require considerable efforts. Let's do that in AI 2.6 scope.
>

Got it, thanks!

--0000000000009a55b2056c324b96--