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 AFAE9200D1E for ; Wed, 18 Oct 2017 11:50:10 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AE55E160BEA; Wed, 18 Oct 2017 09:50:10 +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 CDF031609EE for ; Wed, 18 Oct 2017 11:50:09 +0200 (CEST) Received: (qmail 27314 invoked by uid 500); 18 Oct 2017 09:50:08 -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 27305 invoked by uid 99); 18 Oct 2017 09:50:08 -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, 18 Oct 2017 09:50:08 +0000 Received: from mail-pf0-f179.google.com (mail-pf0-f179.google.com [209.85.192.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id 77E1B1A0185 for ; Wed, 18 Oct 2017 09:50:07 +0000 (UTC) Received: by mail-pf0-f179.google.com with SMTP id b6so3575415pfh.7 for ; Wed, 18 Oct 2017 02:50:07 -0700 (PDT) X-Gm-Message-State: AMCzsaVU+3vMkMvBgwVoqIJ3Az05jWTd5QtqkCVFZtxyqMD7Q12hTpdh aq4dxhJGcDMFlH7DI2q6jJRRnUTlKCwiQCxTUAJu2w== X-Google-Smtp-Source: AOwi7QCrKL3n1TC1GTY751Q+lz/V0zzNkvFx9bUTbbCIJLpYl2IzyWh0VihsGUelcA1LLESrXG3QfOkIKFjB5O3ocIQ= X-Received: by 10.98.67.217 with SMTP id l86mr14237795pfi.92.1508320206917; Wed, 18 Oct 2017 02:50:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.158.99 with HTTP; Wed, 18 Oct 2017 02:50:06 -0700 (PDT) In-Reply-To: References: From: Igor Sapego Date: Wed, 18 Oct 2017 12:50:06 +0300 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: odbc and apache ignite/ c++ clients To: user Content-Type: multipart/alternative; boundary="001a1149a7d624286e055bcf2adc" archived-at: Wed, 18 Oct 2017 09:50:10 -0000 --001a1149a7d624286e055bcf2adc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, ODBC does not have JNI dependency. It only depends on C and C++ standard libraries. If you only need KV and SQL lookups, ODBC driver should be enough for you. Best Regards, Igor On Wed, Oct 18, 2017 at 6:06 AM, Anirudha Jadhav wrote: > i went through this, > > having a JNI dependency is a no-go our our apps. (quoted below from the > link you gave above ). > > hence want to know if the ODBC driver also has ignite JAVA dependency. > > any other C/C++ options are welcome. > > Current we launch ignite clusters as spring-boot managed services, but > need polyglot client acess > > - Ignite =D0=A1++ starts the JVM in the same process and communicates = with > it via JNI > > > > > On Tue, Oct 17, 2017 at 11:00 PM, Alexey Kuznetsov > wrote: > >> Hi, >> >> You can start from docs: https://apacheignite-cpp.readme.io/docs >> >> On Wed, Oct 18, 2017 at 9:54 AM, Anirudha Jadhav >> wrote: >> >>> I need a way to access ignite IMDG/DB from c/c++. >>> >>> The JNI c++ clients is not an option for us. >>> >>> i am currently exploring performance between redis / memchached c/c++ >>> clients >>> >>> Q: does ignite ODBC drivers also have a JNI dependency? >>> >>> Q: what the best approach to access remote ignite grids from c++ with K= V >>> and SQl lookups? >>> >>> >>> thanks a lot, >>> >>> -- >>> Ani >>> >> >> >> >> -- >> Alexey Kuznetsov >> > > > > -- > Anirudha P. Jadhav > --001a1149a7d624286e055bcf2adc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

ODBC does not have JNI dependency. = It only depends on C and C++ standard libraries.

I= f you only need KV and SQL lookups, ODBC driver should be enough for you.

Best Regards,
Igor

On Wed, Oct 18, 2017 at 6:06 AM, Anirudha Ja= dhav <anirudha@nyu.edu> wrote:
i went through this,=C2=A0

having a JNI depende= ncy is a no-go our our apps. (quoted below from the link you gave above ).<= br>
hence want to know if the ODBC driver also has ignite JAVA dependenc= y.

any other C/C++ options are welcome.

Current we launch ign= ite clusters as spring-boot managed services, but need polyglot client aces= s
  • Ignite =D0=A1++ starts the JVM in the same process and commu= nicates with it via JNI



On Tue, Oct 17, 20= 17 at 11:00 PM, Alexey Kuznetsov <akuznetsov@apache.org>= wrote:
Hi,


On Wed, Oct 18, 2017 at 9= :54 AM, Anirudha Jadhav <anirudha@nyu.edu> wrote:
I need a way to access ignite IMDG/= DB from c/c++.=C2=A0

The JNI c++ clients is not an option for us.
i am currently exploring performance between redis / memchached c/c++ = clients

Q: does ignite ODBC drivers also have a JNI dependency?
<= br>Q: what the best approach to access remote ignite grids from c++ with KV= and SQl lookups?


thanks a lot,

--
Ani



--
Alexey Kuznetsov


--
Anirudha P. Jadh= av
--001a1149a7d624286e055bcf2adc--