Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 93368200BD5 for ; Wed, 23 Nov 2016 21:08:11 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 91E50160AEC; Wed, 23 Nov 2016 20:08:11 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DCCDB160AFD for ; Wed, 23 Nov 2016 21:08:10 +0100 (CET) Received: (qmail 578 invoked by uid 500); 23 Nov 2016 20:08:10 -0000 Mailing-List: contact dev-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 dev@ignite.apache.org Received: (qmail 566 invoked by uid 99); 23 Nov 2016 20:08:10 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Nov 2016 20:08:10 +0000 Received: from [10.1.10.15] (c-73-222-138-29.hsd1.ca.comcast.net [73.222.138.29]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id B4A8D1A0046 for ; Wed, 23 Nov 2016 20:08:09 +0000 (UTC) From: Denis Magda Content-Type: multipart/alternative; boundary="Apple-Mail=_64738349-A7FE-45BE-8E5C-2FE0EE8B0396" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Subject: In-Memory SQL Grid Message-Id: Date: Wed, 23 Nov 2016 12:08:08 -0800 To: dev@ignite.apache.org X-Mailer: Apple Mail (2.3251) archived-at: Wed, 23 Nov 2016 20:08:11 -0000 --Apple-Mail=_64738349-A7FE-45BE-8E5C-2FE0EE8B0396 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Community, Frankly speaking, Ignite=E2=80=99s SQL support goes far beyond the = notion of Data Grid starting from Apache Ignite 1.8. SQL in Ignite is no longer about distributed ANSI-99 SELECT queries = only. It will be about the ability to connect to an Ignite Cluster not only = from Java, .NET and C++ sides, that have their own SQL APIs, but, in = general, from your favorite programming language or analytical tool by = the usage of Ignite=E2=80=99s JDBC and ODBC drivers.=20 Even after you=E2=80=99re connected to the cluster from JDBC or ODBC = side you=E2=80=99re no longer limited by distributed SQL queries. You = can freely and easily modify the data with INSERT, UPDATE and DELETE = statements thanks to comprehensive DML supported contributed by = Alexander Paschenko in version 1.8. To prove this, Igor Sapego issued a = guide on how = to start working with an Ignite cluster from PHP side which doesn=E2=80=99= t have its own API implementation on Ignite side. At all, all this means that SQL features set deserved its own component = which I propose to call In-Memory SQL Grid to conform the naming of the = rest of big components like Data Grid, Compute Grid, Service Grid. I=E2=80=99ve already started reworking our documentation and will spend = some time by enriching and expanding it. However, this is a starting = point: https://apacheignite.readme.io/docs/sql-grid = Feel free to share your thoughts regarding the naming or content of the = doc in general. =E2=80=94 Denis [1] https://apacheignite.readme.io/docs/sql-grid= --Apple-Mail=_64738349-A7FE-45BE-8E5C-2FE0EE8B0396--