ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alexey Kuznetsov <akuznet...@gridgain.com>
Subject Re: Usability Issue: Web Console doesn't give an option to add a primary key to object fields list
Date Thu, 16 Mar 2017 00:42:20 GMT
Dmitriy,

I'm not "disagree" :). I'm "surprised" :)
AFAIK our DML uses "_key" as a MUST, i.e. "insert into T (_key, ....)
values (...)"

On Thu, Mar 16, 2017 at 7:35 AM, Dmitriy Setrakyan <dsetrakyan@apache.org>
wrote:

> Alexey, would should our users even know about the existence of _key and
> _val fields? These fields, if needed, should be completely internal. Do you
> disagree?
>
> On Wed, Mar 15, 2017 at 5:32 PM, Alexey Kuznetsov <akuznetsov@apache.org>
> wrote:
>
> > Dmitriy,
> >
> > Are you sure???
> >
> > AFAIK _key and _val fields will be declared as "invisible" i.e. will be
> not
> > included in "select * from T" queries,
> > but NOT removed and still could be used.
> >
> > Or please give a link to JIRA issue.
> >
> >
> > On Thu, Mar 16, 2017 at 7:27 AM, Dmitriy Setrakyan <
> dsetrakyan@apache.org>
> > wrote:
> >
> > > I completely agree. Moreover, AFAIK the _key and _val fields will be
> > > removed in 2.0, so we must add ID or any other field used for a primary
> > key
> > > to the class.
> > >
> > >
> > > On Wed, Mar 15, 2017 at 5:19 PM, Denis Magda <dmagda@apache.org>
> wrote:
> > >
> > >> Alex K., Igniters,
> > >>
> > >> It’s is stated that an existing JDBC based application that works
> with a
> > >> relation database should be easily migrated to Apache Ignite if we
> used
> > Web
> > >> Console and JDBC driver. So, I decided to prove this.
> > >>
> > >> A simple application was created that issues a bunch of SELECT,
> UPDATE,
> > >> etc. queries.
> > >>
> > >> For instance, the simplest query I had looks like this:
> > >>
> > >> SELECT * FROM city WHERE id = ?
> > >>
> > >> When Web Console is used for the schema importing purposes it doesn’t
> > add
> > >> ‘id’ field to a City POJO and, consequently, doesn’t define index
for
> > this
> > >> field. *From technical perspective*, I do understand why we do this -
> to
> > >> save some memory because cache entries key will be used as ‘id’
> instead.
> > >>
> > >> But this breaks the usability in some sense because my simplest query
> > >> above no longer works.
> > >>
> > >> What if we add a special checkbox to Web Console that will add fields
> > >> like ‘id’ to a POJO? If the checkbox is disabled (default) we should
> > show a
> > >> message at the final importing stage saying that fields like ‘id’ has
> > to be
> > >> replaced with ‘_key’.
> > >>
> > >> Thoughts?
> > >
> > >
> > >
> >
> >
> > --
> > Alexey Kuznetsov
> >
>



-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message