Return-Path: <dev-return-25611-archive-asf-public=cust-asf.ponee.io@ignite.apache.org>
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 57358200CF6
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Mon,  4 Sep 2017 05:32:40 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 55BE3163B50; Mon,  4 Sep 2017 03:32:40 +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 9CB2D163B4E
	for <archive-asf-public@cust-asf.ponee.io>; Mon,  4 Sep 2017 05:32:39 +0200 (CEST)
Received: (qmail 11132 invoked by uid 500); 4 Sep 2017 03:32:38 -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 11121 invoked by uid 99); 4 Sep 2017 03:32:38 -0000
Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Sep 2017 03:32:38 +0000
Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179])
	by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 08FE11A02CF
	for <dev@ignite.apache.org>; Mon,  4 Sep 2017 03:32:37 +0000 (UTC)
Received: by mail-qt0-f179.google.com with SMTP id x36so18528768qtx.2
        for <dev@ignite.apache.org>; Sun, 03 Sep 2017 20:32:37 -0700 (PDT)
X-Gm-Message-State: AHPjjUi/MbPHSpYz5eq+nJsA/Ux0V+HA6Ke5KvM7eYBa4a694coDZEmV
	bRLFW+qEHUn48fpcoZLJl8njWIL4XD0W
X-Google-Smtp-Source: ADKCNb7APYlKXZ9+P1ta3JSrlYDb5seV84F5cXo+EEQMaztTKUviROG4odN2YmITV50MN2ZjwJ6uiywPAnqsJMVxz2E=
X-Received: by 10.200.3.143 with SMTP id t15mr13138241qtg.293.1504495956522;
 Sun, 03 Sep 2017 20:32:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.34.6 with HTTP; Sun, 3 Sep 2017 20:31:55 -0700 (PDT)
In-Reply-To: <1504188746233-0.post@n6.nabble.com>
References: <1504186335409-0.post@n6.nabble.com> <CANCAXEHX9mwu63Rnas05CSGsAJ9Ou+fC08PTMZbuMcVAUJSJ5g@mail.gmail.com>
 <1504188746233-0.post@n6.nabble.com>
From: Dmitriy Setrakyan <dsetrakyan@apache.org>
Date: Sun, 3 Sep 2017 20:31:55 -0700
X-Gmail-Original-Message-ID: <CA+0=VoV3U7xmeVCVr7Eu9ncXF8PJ90FL_6df_vsts3MB84UKew@mail.gmail.com>
Message-ID: <CA+0=VoV3U7xmeVCVr7Eu9ncXF8PJ90FL_6df_vsts3MB84UKew@mail.gmail.com>
Subject: Re: UPDATE SQL for nested BinaryObject throws exception.
To: user <user@ignite.apache.org>, dev@ignite.apache.org
Content-Type: multipart/alternative; boundary="f4030435a6480e080d055854c34e"
archived-at: Mon, 04 Sep 2017 03:32:40 -0000

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

Cross sending to dev@

Igniters, up until version 1.9, the nested fields were supported by
flattening the names. Do we still support it? I cannot seem to find
documentation for it.

D.

On Thu, Aug 31, 2017 at 7:12 AM, takumi <blaite@kss.biglobe.ne.jp> wrote:

> This is a part of the real code that I wrote.
>
> -----------------------------
>   List<QueryEntity> entities = new ArrayList<>();
>   QueryEntity qe = new QueryEntity(String.class.getName(), "cache");
>   qe.addQueryField("attribute.prop1", Double.class.getName(), "prop3");
>   qe.addQueryField("attribute.prop2", String.class.getName(), "prop4");
>   qe.addQueryField("attribute.prop.prop1", Double.class.getName(),
> "prop5");
>   qe.addQueryField("attribute.prop.prop2", String.class.getName(),
> "prop6");
>
>   BinaryObject bo  =ib.builder("cache").setField("attribute",
>         ib.builder("cache.attribute")
>           .setField("prop",
>                 ib.builder("cache.attribute.prop")
>                    .setField("prop1", 50.0, Double.class)
>                    .setField("prop2", "old", String.class))
>           .setField("prop1", 50.0, Double.class)
>           .setField("prop2", "old", String.class)).build();
>
>   cache.put("key1", bo);
>   cache.query(new SqlFieldsQuery("update cache set prop4 = 'new'  where
> prop3 >= 20.0"));//OK
>   cache.query(new SqlFieldsQuery("update cache set prop6 = 'new'  where
> prop5 >= 20.0"));//NG
> -----------------------------
>
> I can update 'prop4' by SQL, but I do not update 'prop6' by SQL.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

--f4030435a6480e080d055854c34e--