Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EF8E2181C8 for ; Mon, 18 Apr 2016 21:24:21 +0000 (UTC) Received: (qmail 17597 invoked by uid 500); 18 Apr 2016 21:24:21 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 17547 invoked by uid 500); 18 Apr 2016 21:24:21 -0000 Mailing-List: contact user-help@ignite.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.apache.org Delivered-To: mailing list user@ignite.apache.org Received: (qmail 17537 invoked by uid 99); 18 Apr 2016 21:24:21 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Apr 2016 21:24:21 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 4E2961804AD for ; Mon, 18 Apr 2016 21:24:21 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.173 X-Spam-Level: ** X-Spam-Status: No, score=2.173 tagged_above=-999 required=6.31 tests=[DKIM_ADSP_CUSTOM_MED=0.001, NML_ADSP_CUSTOM_MED=1.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.972] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id y00MOILlHuFv for ; Mon, 18 Apr 2016 21:24:19 +0000 (UTC) Received: from mbob.nabble.com (mbob.nabble.com [162.253.133.15]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 820455F23C for ; Mon, 18 Apr 2016 21:24:18 +0000 (UTC) Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id 7BF8425875BD for ; Mon, 18 Apr 2016 14:10:57 -0700 (PDT) Date: Mon, 18 Apr 2016 14:10:18 -0700 (PDT) From: vkulichenko To: user@ignite.apache.org Message-ID: <1461013818224-4298.post@n6.nabble.com> In-Reply-To: <1460979191706-4281.post@n6.nabble.com> References: <1460979191706-4281.post@n6.nabble.com> Subject: Re: SQL Aliases are not interpreted correctly MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Aliases are supported by Ignite, but you have to use Java names when running in-memory queries, not DB names. You should refer to the CacheConfig class for mappings. For example, here is the entry for activity_id field: vals.add(new JdbcTypeField(Types.BIGINT, "ACTIVITY_ID", long.class, "activityId")); Java field name (the one used in the object) is activityId, so the query should start like this: SELECT DISTINCT activity0.activityId, ... Please let me know if it helps. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4298.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.