Re: Get client node instance

Arthi, I don't see how it currently possible to use shared memory to shared Ignite instance among different processes. What I propose is to not start different process on user request but maybe start separate thread instead so you will have single address space among all clients. Is it possible

Re: Client Connection to Ignite takes time

Sure, I'm going to do that. I've created ticket for that - [1]. [1] - https://issues.apache.org/jira/browse/IGNITE-3150. Best Regards, Igor On Tue, May 17, 2016 at 3:20 AM, Dmitriy Setrakyan wrote: > The documentation currently does not look complete for the upcoming

Re: Get client node instance

Arthi, Well, there would be significant performance gain if you would not start new client process for every request and then terminate it but rather start node once in the same process that currently starts new process. I'm not sure if it's possible for you. What is the language of the

Re: Get client node instance

Arthi, It seems to me like we have some misunderstanding here. Let me provide my understanding of your usecase so you could correct me if I'm wrong. You have the client application which is written in C++ and has to handle multiple concurrent requests from multiple users. Now, do you invoke the

Re: Get client node instance

Arthi, Why do you create one client node per user request? Can you create a node on application start and then just use this node instance when you need to make a request? Best Regards, Igor On Mon, May 16, 2016 at 6:41 PM, arthi wrote: > Hi Igor, > > this

Re: Get client node instance

I mean startup of the client application. Best Regards, Igor On Mon, May 16, 2016 at 7:18 PM, Igor Sapego <isap...@gridgain.com> wrote: > Arthi, > > Why do you create one client node per user request? Can you create > a node on application start and then just use this node i

Re: Get client node instance

Hi Arthi, In current implementation, node instance (i.e. Ignite instance) can not be shared between different processes. Can you describe your use case a bit more? Which start up time would be acceptable in your case? Are you starting client node on the startup of the application or are you

Re: ODBC Driver?

Hi Arthi, In new release you should not run libtolize, aclocal and other autotools for every directory. Now you only should do that once in the root directory i.e. $IGNITE_HOME/platforms/cpp. Please refer to DEVNOTES.txt for detailed instructions. Best Regards, Igor On Thu, May 12, 2016 at 5:16

Re: ODBC Driver?

Hi guys, I confirm, ODBC driver is already in master branch. It can also be found in the last nightly build [1]. It can be found in platforms/cpp/odbc. [1] - https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/211/ Best Regards, Igor On Fri, May 6, 2016 at 11:18 AM, Denis Magda

Re: ODBC Driver?

Hi Arthi, ODBC driver supports rowset binding though currently only fetching of a single row per call is supported, i.e. SQL_ATTR_ROW_ARRAY_SIZE attribute can only be set to 1 right now. Best Regards, Igor On Wed, Apr 27, 2016 at 1:56 PM, arthi wrote: >

Re: Compute Grid API in C++/Scala

Hello Arthi, There is no yet Compute API in C++ client, but we are planning to add it soon. Best Regards, Igor On Fri, Apr 22, 2016 at 4:50 PM, arthi wrote: > Hi Team, > > Is there a C++/Scala API for the compute grid? > > Thanks > Arthi > > > > -- > View

Re: Error running nodes in .net and c++

is not suitable for you. Best Regards, Igor On Tue, Apr 19, 2016 at 1:06 PM, Murthy Kakarlamudi <ksa...@gmail.com> wrote: > Thank You. > On Apr 19, 2016 6:01 AM, "Igor Sapego" <isap...@gridgain.com> wrote: > >> Hi, >> >> It looks like a bug for m

Re: C++ Distributed cache for caching files

Hi, Can you share the code of your test so we can investigate it? Best Regards, Igor On Tue, Apr 19, 2016 at 12:45 PM, rajs123 wrote: > Hi, > > I changed 1024 to 2048 and recompiled the module. > I get the following error: > > terminate called after throwing an instance

Re: Error running nodes in .net and c++

Hi, It looks like a bug for me. I've submitted an issue for it - [1]. [1] - https://issues.apache.org/jira/browse/IGNITE-3025. Best Regards, Igor On Mon, Apr 18, 2016 at 1:35 AM, Murthy Kakarlamudi wrote: > The client node itself starts after making the change, but getting

Re: Host Arrays in C++ API

Arthi, How much time does it take? What is the speed of fetching in rows per second? Guys, can someone who is more familiar with Ignite's SQL queries take a look? Best Regards, Igor On Mon, Apr 11, 2016 at 5:17 PM, arthi wrote: > Hi Igor, > > the SQL query

Re: C++ Client - Accessing Ignite Grid as Pointer

Hello Kannan, I can't reproduce the issue you have described. Which compiler do you use? Also I'm not sure if the code you have provided is exactly the code that fails in your case or are you trying to access "pGrid" pointer from the another thread/process? Also, please properly subscribe to

Re: Host Arrays in C++ API

Arthi, I've run some profiling over the code that you have provided and it seems like there is almost no time spent in the client (C++) code. So I believe host arrays would not help you much as your code spends the most of the execution time on the query itself and not on the C++ calls. Best

Re: Host Arrays in C++ API

Hi Arthi, Host arrays is not something that we have planned for the nearest release. However, I have reproduced and investigated the issue that you have provided and it is very likely that we are going to optimize cursor operations in the nearest future which should fasten your code a lot. You

Re: Host Arrays in C++ API

Hi Arthi, I need more time. I have enough info for now. Best Regards, Igor On Wed, Mar 30, 2016 at 1:06 PM, arthi wrote: > Hi Igor, > > Were you able to get to something? Pls let me know if you need more info. > > Thanks, > Arthi > > > > -- > View this

Re: C++ Client for SQL Queries

Arthi, It is known issue [1]. It has been fixed already and this fix is going to be included to the next release. You can try using code from master brach or as a workaround you can try using no-throw method version instead i.e. QueryFieldsRow::GetNext(IgniteError& err). [1] -

Re: C++ Client for SQL Queries

Arthi, You can just put your additional libraries to $IGNITE_HOME/libs directory. Best Regards, Igor On Thu, Mar 10, 2016 at 7:56 AM, arthi wrote: > Thanks Igor. > > Well, I tried using a cache config in the XML to start my C++ client. but, > the factory

Re: C++ Client for SQL Queries

Well, in short, you do not need to do any additional steps if you has not explicitly set any other marshaller for your grid. Ignite uses marshaller to serialize and de-serialize objects. There are different marshallers that Apache Ignite supports. They define format of the serialized objects. In

Re: C++ Client for SQL Queries

Arthi, The short answer to all your questions is "yes" - C++ client is able to de-serialize Java objects if you are using BinaryMarshaller and it is also able to trigger read-through requests to Java factory store if there are cache misses. Best Regards, Igor On Wed, Mar 9, 2016 at 2:35 PM,

Re: C++ Client for SQL Queries

Hello, Arthi Your assumption is correct, in order to run queries you need to use proper configuration with "queryEntities" property defined for the cache as described in documentation [1]. For the "Organization" type that you mentioned it should contain at least the following:

Re: Apache Ignite vs BI tools

Hi Andrzej, We are currently working on the ODBC driver for Ignite that will allow users to use even more BI tools. In particular right now we are working on Tableu integration and it's going to be part of the 1.6 release. You can find related ticket here:

<    1   2   3   4