Mailing-List: contact dev-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
MIME-Version: 1.0
In-Reply-To: <CAGt6o8mWs2w-SrwU_X87VDxAJ07d-mCbH6ZC+46cj6=8mQ+d1w@mail.gmail.com>
References: <CAJhSPbqBUo7KfQFZQRTTH58kPoo00GcXY_4ZtdBCwoKF3aTOAw@mail.gmail.com>
 <CA+0=VoW6k8F-v2SGDME3P2=c6HAZ96cGN9rMm-i=S2BB3v41eQ@mail.gmail.com>
 <CAJhSPbrgDGHR5O++F5KN9mf42G87_4JOM8xj5nzxHJ91O9nA7g@mail.gmail.com>
 <CA+0=VoXn2L7wLbYOE15wm++UermtVMt8C=G_jodYGG_rNfNjiA@mail.gmail.com>
 <CAJhSPbrQhTM87u+urD0R15=7eFi3Sn__4dFcOaNdj-O_gYo3-A@mail.gmail.com>
 <CAJhSPbqNhxOh9QaShvFxo3r6FsO2bfNsTgcqVqn20XBjGbjEjQ@mail.gmail.com>
 <CAGt6o8=t5qOHWjFdG-m2x59_=TrB7mUA0sp+2Mk+NdgvqjiLdg@mail.gmail.com>
 <CA+0=VoXHUKp4vHyvtzbyjh49C49vCzvhE_s7FZuYT_xfkW88LQ@mail.gmail.com>
 <CAGt6o8nEXj4f_UR2OWVwFuUSHnQJtPaUEjVWtZESWAxMB7K_TA@mail.gmail.com>
 <CA+0=VoXDV3L9xhQjB99B2Tn5zh1FM6rEiXTD2bVadSSQt4o3vQ@mail.gmail.com>
 <CAGt6o8nWztjoWtoATjy_Okxevv6E1W4U0veeR9KUx-xm8yb7Tw@mail.gmail.com>
 <CA+eZwrEzx_Rmpd0hGw4RMPeDXpQSPPvw8m3+9dPaQXFd9HN4ww@mail.gmail.com>
 <CAGt6o8njQ+y4OK9QzbmPU8g6ofE7N=7iqFPrqTMWZFxgGF2XBA@mail.gmail.com>
 <CA+0=VoUO12k1b9vgHzb4j7SoFQae8=Xdkdt=3gw24hmqzqh+ew@mail.gmail.com> <CAGt6o8mWs2w-SrwU_X87VDxAJ07d-mCbH6ZC+46cj6=8mQ+d1w@mail.gmail.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Thu, 16 Feb 2017 13:40:05 -0800
Message-ID: <CA+0=VoU-Nzh8BGdMD9OwrmCiHhM6Py20vGMRkQ9cjtVka=+05Q@mail.gmail.com>
Subject: Re: DML data streaming
To: dev@ignite.apache.org
Content-Type: multipart/alternative; boundary=001a114c977e5f341c0548aca68a
archived-at: Thu, 16 Feb 2017 21:40:49 -0000

--001a114c977e5f341c0548aca68a
Content-Type: text/plain; charset=UTF-8

Vladimir, I am not sure I understand your point. The value type name should
be the table name, no?

On Thu, Feb 16, 2017 at 12:13 AM, Vladimir Ozerov <vozerov@gridgain.com>
wrote:

> Dima,
>
> At this point we require the following additional data which is outside of
> standard SQL:
> - Key type
> - Value type
> - Set of key columns
>
> I do not know yet how we will define these values. At the very least we can
> calculate them automatically in some cases. For "keyFieldName" and
> "valFieldName" things are easier, as we can always derive them from table
> definition.
>
> Example 1 - primitives:
>
> CREATE TABLE (
>     *pk_id* BIGINT PRIMARY KEY,
>     *val*   BIGINT
> )
>
> keyFieldName = "*pk_id*", valFieldName = "*val*"
>
> Example 2 - composites:
>
> CREATE TABLE (
>     *pk_id* BIGINT PRIMARY KEY,
>     val1  BIGINT,
>     val2  VARCHAR
> )
>
> keyFieldName = "*pk_id*", valFieldName = null (because value is complex and
> is composed of two attributes).
>
> Vladimir.
>
>
> On Wed, Feb 15, 2017 at 11:42 PM, Dmitriy Setrakyan <dsetrakyan@apache.org
> >
> wrote:
>
> > On Wed, Feb 15, 2017 at 4:28 AM, Vladimir Ozerov <vozerov@gridgain.com>
> > wrote:
> >
> > > Ok, let's put aside current fields configuration, I'll create separate
> > > thread for it. As far as _KEY and _VAL, proposed change is exactly
> about
> > > mappings:
> > >
> > > class QueryEntity {
> > >     ...
> > >     String keyFieldName;
> > >     String valFieldName;
> > >     ...
> > > }
> > >
> > > The key thing is that we will not require users to be aware of our
> system
> > > columns. Normally user should not bother about existence of hidden _KEY
> > and
> > > _VAL columns. Instead, we just allow them to optionally reference the
> > whole
> > > key and/or val through predefined name.
> > >
> > >
> > Vladimir, how will it work from the DDL perspective. Let's say whenever
> > user wants to create a table in Ignite?
> >
>

--001a114c977e5f341c0548aca68a--