RE: Apache Ignite & unixODBC and truncating text

[Alexey Popov]

Hi Bagsiur,

It is some mono lib error below, not a user-code.

Can you share a simple code reproducer? Just to see the order of actions in 
your code.

Thank you,
Alexey

From: bagsiur
Sent: Tuesday, January 9, 2018 10:36 AM
To: user@ignite.apache.org
Subject: Re: Apache Ignite & unixODBC and truncating text

So, I use Apache Ignite in 2.3.0 version.

Im not C# programmer but I compile attached C# example by mono:

mcs -out:odbcvarchar.exe -r:System.dll -r:System.Data.dll odbcvarchar.cs

And after when I run it I have fallowing errors:

[ERROR] FATAL UNHANDLED EXCEPTION: System.EntryPointNotFoundException:
LocalAlloc
  at (wrapper managed-to-native)
System.Data.Common.SafeNativeMethods:LocalAlloc (int,intptr)
  at System.Data.ProviderBase.DbBuffer..ctor (System.Int32 initialSize,
System.Boolean zeroBuffer) [0x0002f] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.ProviderBase.DbBuffer..ctor (System.Int32 initialSize)
[0x0] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.CNativeBuffer..ctor (System.Int32 initialSize)
[0x0] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.GetStatementHandle () [0x00033] in
<23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteReaderObject
(System.Data.CommandBehavior behavior, System.String method, System.Boolean
needReader, System.Object[] methodArguments, System.Data.Odbc.ODBC32+SQL_API
odbcApiMethod) [0x00019] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteReaderObject
(System.Data.CommandBehavior behavior, System.String method, System.Boolean
needReader) [0x0001c] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteNonQuery () [0xa] in
<23f11074adc346a7bcd76c006d949301>:0
  at OdbcVarchars.Program.Main (System.String[] args) [0x00023] in
<873514a817794f1297b9f0b2be86f821>:0




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDBC thin client load balancing and failover support

[rizal123]

Hi Val,

According to this ticket 'IGNITE-7029'.
How long it will be *Live*?
At least tell me the estimated time?

Because I have the same problem, about failover and Jdbc thin can access
multiple Node (IP Address).
And I need to go to POC.

regards,
-Rizal





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite & unixODBC and truncating text

[bagsiur]

So, I use Apache Ignite in 2.3.0 version.

Im not C# programmer but I compile attached C# example by mono:

mcs -out:odbcvarchar.exe -r:System.dll -r:System.Data.dll odbcvarchar.cs

And after when I run it I have fallowing errors:

[ERROR] FATAL UNHANDLED EXCEPTION: System.EntryPointNotFoundException:
LocalAlloc
  at (wrapper managed-to-native)
System.Data.Common.SafeNativeMethods:LocalAlloc (int,intptr)
  at System.Data.ProviderBase.DbBuffer..ctor (System.Int32 initialSize,
System.Boolean zeroBuffer) [0x0002f] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.ProviderBase.DbBuffer..ctor (System.Int32 initialSize)
[0x0] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.CNativeBuffer..ctor (System.Int32 initialSize)
[0x0] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.GetStatementHandle () [0x00033] in
<23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteReaderObject
(System.Data.CommandBehavior behavior, System.String method, System.Boolean
needReader, System.Object[] methodArguments, System.Data.Odbc.ODBC32+SQL_API
odbcApiMethod) [0x00019] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteReaderObject
(System.Data.CommandBehavior behavior, System.String method, System.Boolean
needReader) [0x0001c] in <23f11074adc346a7bcd76c006d949301>:0
  at System.Data.Odbc.OdbcCommand.ExecuteNonQuery () [0xa] in
<23f11074adc346a7bcd76c006d949301>:0
  at OdbcVarchars.Program.Main (System.String[] args) [0x00023] in
<873514a817794f1297b9f0b2be86f821>:0




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to make full use of network bandwidth?

[Michael Jay]

Thank you, Alexey. I'll try you advice and let you know the result later. 
Thanks again.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Best practice Apache Ignite Data-Grid with Java EE application

[vkulichenko]

Hi Franz,

Running an Ignite client node embedded into an application would be the best
way to interact with the cluster. You will have all the APIs available and
also it's the preferred option from performance standpoint.

Ignite already has thread pool pre configured, there is no need to specify
anything explicitly unless you have specific performance concerns. I would
start with creating a simple setup and running performance tests to see how
it behaves.

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Limit cache size ?

[vkulichenko]

Ignite stores data in off-heap memory, so you can't limit the number of
entries, but you can limit the amount of memory allocated for caches. This
is done via data region configuration:
https://apacheignite.readme.io/docs/memory-configuration

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Why does Ignite de-allocate memory regions ONLY during shutdown?

[John Wilson]

Hi,

I was looking at the UnsafeMemoryProvide and it looks to me that allocated
direct memory regions are deallocated only during shutdown.

https://github.com/apache/ignite/blob/c5a04da7103701d4ee95910d90ba786a6ea5750b/modules/core/src/main/java/org/apache/ignite/internal/mem/unsafe/UnsafeMemoryProvider.java#L80

https://github.com/apache/ignite/blob/c5a04da7103701d4ee95910d90ba786a6ea5750b/modules/core/src/main/java/org/apache/ignite/internal/mem/unsafe/UnsafeMemoryProvider.java#L63

My question:

if a memory region has been allocated and, during execution, all data pages
that are in the region are removed, then why is the memory region
de-allocated?

Thanks,

Limit cache size ?

[Mikael]

Hi!

Is there any way I can limit the number of items in a cache ? I know the 
JCache API does not support it, only the time based expiration, but 
using that mean that a cache can grow a lot if it gets fed a lot of 
items in a short time, something like the LRU eviction but that deletes 
older items instead of moving them from heap to non heap.

Protect Ignite clusters from Meltdown and Spectre

[Denis Magda]

Make sure your Ignite clusters are protected from the fierce vulnerabilities 
that rocked the world:
https://blogs.apache.org/ignite/entry/protecting-apache-ignite-from-meltdown

—
Denis

Best practice Apache Ignite Data-Grid with Java EE application

[Franz Mathauser]

hello @all,

i'm currently evaluating some data-grid solutions to replace my
data-backend. i want to use apache ignite as backend data-grid to serve
data within a javaee application.

is the apache ignite native client sutable to integrate the data-grid with
the javaee application?

which threadpool do i need to configure in order to tune parallelism for
incoming requests? What is the best way to set timeouts for the data-grid
operation on apache ignite native client side?

if the native client is not recommended for my usecase, what is a better
approach for integration (like invoking the apache ignite rest-interface
from the javaee app, for example)?

thx, best regards

franz

Re: Ignite work directory usage?

[ilya.kasnacheev]

Hello Denis!

There seems to be cases where matching workDir for different nodes
(including client nodes) will cause problems:

http://apache-ignite-users.70518.x6.nabble.com/MarshallerContextImpl-Failed-to-write-class-name-to-file-td18439.html

There, on Windows, two nodes try to update binary marshaller cache on disk
at the same time, but, this being on Windows, one of them fails to open file
for writing.

On other OSes there also exists case where one instance would open file for
writing, and other one, seeing that there is already a file present, tries
to read it, reads zero bytes and fails at that.

WDYT about this case?

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Exception when connecting to cache / table.

[Thomas Isaksen]

Hi Ilya!

Thank you that was it. I can connect now. Awesome product!

Regards

--
Thomas Isaksen

From: Ilya Kasnacheev [mailto:ilya.kasnach...@gmail.com]
Sent: mandag 8. januar 2018 15.07
To: user@ignite.apache.org
Subject: Re: Exception when connecting to cache / table.

Hello Thomas!
You should not supply cache configuration to access caches created by DDL. It's 
neither required nor useful.
Just use ignite.cache("testCache"); - by name.
You can always invoke CREATE IF NOT EXISTS to ensure that cache indeed exists.
Regards,

--
Ilya Kasnacheev

2018-01-08 16:32 GMT+03:00 Thomas Isaksen 
>:
I have created my first TABLE in Ignite and I am trying to connect to it but I 
am getting this error message:

class org.apache.ignite.IgniteException: Cache configuration mismatch (local 
cache was created via Ignite API, while remote cache was created via CREATE 
TABLE

I’m not exactly sure what this means.

My table def:

CREATE TABLE IF NOT EXISTS TestTable
(
   username VARCHAR,
   password VARCHAR,
   PRIMARY KEY (username, password)
)
WITH "template=partitioned,backups=1,cache_name=testCache";

My connect code:

Ignition.setClientMode(true);
CacheConfiguration myCacheConfiguration = new CacheConfiguration("testCache");
myCacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
myCacheConfiguration.setBackups(1);
//
IgniteConfiguration igniteConfig = new IgniteConfiguration();
igniteConfig.setMetricsLogFrequency(0);
igniteConfig.setCacheConfiguration(myCacheConfiguration);
igniteConfig.setPeerClassLoadingEnabled(true);

Ignite ignite = Ignition.getOrStart(igniteConfig);
IgniteCache cache = 
ignite.getOrCreateCache(myCacheConfiguration);
…

--
Thomas Isaksen

Re: Exception when connecting to cache / table.

[Ilya Kasnacheev]

Hello Thomas!

You should not supply cache configuration to access caches created by DDL.
It's neither required nor useful.

Just use ignite.cache("testCache"); - by name.

You can always invoke CREATE IF NOT EXISTS to ensure that cache indeed
exists.

Regards,

-- 
Ilya Kasnacheev

2018-01-08 16:32 GMT+03:00 Thomas Isaksen :

> I have created my first TABLE in Ignite and I am trying to connect to it
> but I am getting this error message:
>
>
>
> class org.apache.ignite.IgniteException: Cache configuration mismatch
> (local cache was created via Ignite API, while remote cache was created via
> CREATE TABLE
>
>
>
> I’m not exactly sure what this means.
>
>
>
> My table def:
>
>
>
> *CREATE* *TABLE* *IF* *NOT* *EXISTS* TestTable
>
> (
>
>username *VARCHAR*,
>
>password VARCHAR,
>
>*PRIMARY* *KEY* (username, password)
>
> )
>
> *WITH* "template=partitioned,backups=1,cache_name=testCache";
>
>
>
> My connect code:
>
>
>
> Ignition.*setClientMode*(true);
>
> CacheConfiguration myCacheConfiguration = new
> CacheConfiguration("testCache");
> myCacheConfiguration.setCacheMode(CacheMode.*PARTITIONED*);
> myCacheConfiguration.setBackups(1);
> //
> IgniteConfiguration igniteConfig = new IgniteConfiguration();
> igniteConfig.setMetricsLogFrequency(0);
> igniteConfig.setCacheConfiguration(myCacheConfiguration);
> igniteConfig.setPeerClassLoadingEnabled(true);
>
> Ignite ignite = Ignition.*getOrStart*(igniteConfig);
> IgniteCache cache = ignite.getOrCreateCache(
> myCacheConfiguration);
> …
>
>
>
> --
>
> Thomas Isaksen
>

Re: Date type field in select query is returning wrong value when Time zones of Ignite Client and Server are different

[Ilya Kasnacheev]

Hello!

I was able to reproduce the behaviour that you are describing. I have
suspicion that it has to do with separate handling of date types in H2,
which is used in Ignite for SQL queries. I will investigate this further,
see if there are work-arounds.

Regards,


-- 
Ilya Kasnacheev

2018-01-02 13:31 GMT+03:00 kotamrajuyashasvi :

> Hi
>
> In my sample Demo Ignite java program, Initially a Person entry is inserted
> from the Ignite Client into the Ignite cache. The Person Pojo has  a "dob"
> field which is of java.util.Date type. Now when the Person Object is
> obtained using _val in query, the getTime() on dob field of Person Object
> gives same milliseconds that was used during the cache insert/put . But
> when
> querying for dob field in select query it returns a java.sql.Timestamp
> Object in QueryCursor and when getTime() on that Timestamp is called it
> returns different milliseconds value. This milliseconds value obtained from
> query will be used in other queries hence its crucial that correct
> milliseconds value is obtained in query result. This behavior is observed
> when Ignite Client and Server are in different TimeZones. The milliseconds
> value in the Date Object is independent of Timezone.
>
> Following is a sample reproducer:
>
> ** DemoProgram  *
> package com.IgniteDemo;
>
> import java.util.*;
> import javax.cache.Cache.Entry;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.IgniteException;
> import org.apache.ignite.Ignition;
> import org.apache.ignite.cache.query.QueryCursor;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.cache.query.SqlQuery;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
>
> public class DemoMain {
>
> public static void main(String[] args){
>
>
> System.setProperty("user.timezone", "EST");//to change
> timezone of the
> ignite client program
>
> String ConfigPath = "default-config.xml";
>
> Ignite ignite = Ignition.start(ConfigPath);
>
> IgniteCache cache =
> ignite.cache("Person");
>
> System.out.println("cache size "+cache.size());
>
> long dob = 77146560L;
>
> Person p1 = new Person(1,"yash",22,"124345","addr",new
> Date(dob));
> cache.put(p1.getPK(),p1);
>
> System.out.println("cache size "+cache.size());
>
> System.out.println("case 1: Obtaining dob from Person
> Object");
> SqlFieldsQuery sql = new SqlFieldsQuery(
> "select _val from Person where dob = ?");
> try (QueryCursor> cursor =
> cache.query(sql.setArgs(new
> Date(7714656001000L {
> for (List row : cursor){
>dob = (((Person)row.get(0)).getDob().getTime());
>System.out.println(" getTime of dob from Person
> Object : " + dob);
> }
> }
>
> sql = new SqlFieldsQuery(
> "select name from Person where dob = ?");
> try (QueryCursor> cursor =
> cache.query(sql.setArgs(new
> Date(dob {
> for (List row : cursor){
>System.out.println(" name of person in query
> result  : " +
> row.get(0));
> }
> }
>
> System.out.println("case 2: Obtaining dob from Select
> query field ");
> sql = new SqlFieldsQuery(
> "select dob from Person where dob = ?");
> try (QueryCursor> cursor =
> cache.query(sql.setArgs(new
> Date(7714656001000L {
> for (List row : cursor){
>dob = (((Date)row.get(0)).getTime());
>System.out.println(" Object Type of dob from select
> query result
> object: " + row.get(0).getClass().getName());
>System.out.println(" getTime of dob from select
> query result field
> object  : " + dob);
> }
> }
>
>
> sql = new SqlFieldsQuery(
> "select name from Person where dob = ?");
> try (QueryCursor> cursor =
> cache.query(sql.setArgs(new
> Date(dob {
> for (List row : cursor){
>System.out.println(" name of person in query result
> : " +
> row.get(0));
> }
> }
>
> }
>
> *** OUTPUT ***
> cache size 0
> cache size 1
> case 1: Obtaining dob from Person Object
>  getTime of dob from Person Object : 77146560
>  name of person in query result  : yash
> case 2: Obtaining dob from Select query field
>  Object Type of dob from select query result object: 

Exception when connecting to cache / table.

[Thomas Isaksen]

I have created my first TABLE in Ignite and I am trying to connect to it but I 
am getting this error message:

class org.apache.ignite.IgniteException: Cache configuration mismatch (local 
cache was created via Ignite API, while remote cache was created via CREATE 
TABLE

I'm not exactly sure what this means.

My table def:

CREATE TABLE IF NOT EXISTS TestTable
(
   username VARCHAR,
   password VARCHAR,
   PRIMARY KEY (username, password)
)
WITH "template=partitioned,backups=1,cache_name=testCache";

My connect code:

Ignition.setClientMode(true);

CacheConfiguration myCacheConfiguration = new CacheConfiguration("testCache");
myCacheConfiguration.setCacheMode(CacheMode.PARTITIONED);
myCacheConfiguration.setBackups(1);
//
IgniteConfiguration igniteConfig = new IgniteConfiguration();
igniteConfig.setMetricsLogFrequency(0);
igniteConfig.setCacheConfiguration(myCacheConfiguration);
igniteConfig.setPeerClassLoadingEnabled(true);

Ignite ignite = Ignition.getOrStart(igniteConfig);
IgniteCache cache = 
ignite.getOrCreateCache(myCacheConfiguration);
...


--
Thomas Isaksen

Re: How to make full use of network bandwidth?

[Alexey Popov]

Hi Michael,

Did you try non-default parameters for 
1) socketSendBuffer and socketReceiveBuffer [1] in JDBC connection string?
2) socketSendBufferSize and socketReceiveBufferSize [2] in Ignite server
node configuration for SqlConnectorConfiguration?

Please change them to 128k and make a try.

JDBC thin driver works in a single thread in one-by-one request-by-response
SQL statement execution. I am not sure you can fully utilize a network here. 
Probably, you could use an IgniteDataStreamer to achieve better results.
Please have a look at [3].
Or you should create multiple JDBC connections and parallel your inserts in
multiple threads.

[1]
https://apacheignite-sql.readme.io/docs/jdbc-driver#section-jdbc-thin-driver
[2]
https://apacheignite-sql.readme.io/docs/jdbc-driver#section-cluster-configuration
[3] https://apacheignite.readme.io/docs/data-loading

Thank you,
Alexey



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Force flush of IGFS to secondary file system in DUAL_ASYNC mode

[ilya.kasnacheev]

Hello!

After reviewing IGFS code, I think that you can do the following:

You should save all file paths that are being migrated, and then call
await(collectionWithAllFilePaths) on IgfsImpl. If it's a huge number of
files, I imagine you can do this in batches.

It will do the same synchronous wait that DUAL_SYNC would do, just from a
different entry point. After await() returns you are safe to close IgfsImpl
and shutdown your cluster.

Note that I would like to have the same behaviour for IgfsImpl.close(cancel:
false), but it's NOT there yet. I have filed
https://issues.apache.org/jira/browse/IGNITE-7356 - do not hesitate to
comment.

Regards,



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: off heap memory usage

[Alexey Popov]

Hi Colin,

Unfortunately, you can't get the exact off-heap size.

There are several tickets here 
https://issues.apache.org/jira/browse/IGNITE-6814
https://issues.apache.org/jira/browse/IGNITE-5583
http://apache-ignite-users.70518.x6.nabble.com/Cache-size-in-Memory-td17226.html

You are using (pages * pageSize * pagesFillFactor) correctly (if you have
only one memory region).

BTW, pagesFillFactor is calculated using FreeLists [1] buckets. FreeLists
has a limited amount of buckets (for instance, approx 25% free, ~50% free,
~75% free).
In this case (pages * pageSize * pagesFillFactor) will give you an approx
value of memory usage (based on buckets) and you can see drops in the usage
when a page is moved from one bucket to another.

[1]
https://apacheignite.readme.io/docs/memory-architecture#section-free-lists

Thanks,
Alexey




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction operations using the Ignite Thin Client Protocol

[kotamrajuyashasvi]

Hi

In Ignite ODBC all operations are sql based and as you mentioned sql
transactions feature is not available yet. So cannot use it. So just
exploring all light weight C++ client  options available which support
Ignite Transactions.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction operations using the Ignite Thin Client Protocol

[Evgenii Zhuravlev]

Right now, this client implemented only for .NET, but it's not even
released yet.

I'm not sure about transactions since design document doesn't contain any
information about it.

BTW, why you don't want to use ODBC from C++?


2018-01-08 13:13 GMT+03:00 kotamrajuyashasvi :

> Hi
>
> according to
> https://cwiki.apache.org/confluence/display/IGNITE/IEP-
> 9+Thin+Client+Protocol
>
> we can perform cache operations like get(),put() etc using thin client
> protocol which uses tcp socket communication with the Ignite server. I
> would
> like to know if similarly we can send a request to start a transaction or
> committing / rolling back transaction.
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: java.lang.IllegalStateException: Cache has been closed:

[Alexey Popov]

Hi Raj,

IgniteCache implements AutoCloseable interface. [1]
You can't access it once IgniteCache.close() is called (implicitly via
try-with-resource or explicitly).

[1]
https://docs.oracle.com/javase/tutorial/essential/exceptions/tryResourceClose.html

Thanks,
Alexey




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Connection problem between client and server

[Jeff Jiao]

Hi Denis,

We think the problem is when a client connect to an existing cluster, server
node will send the attributes of all the nodes in the cluster(Servers &
Clients) to that new client. it will be a lot of data here... 
We may also have problems for our network configuration, we are still
investigating.

For our system, it needs a lot of jars, we cannot avoid these infos...

Does Ignite dev team give any feedback for this?



Thanks,
Jeff



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction operations using the Ignite Thin Client Protocol

[kotamrajuyashasvi]

Hi

according to 
https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol

we can perform cache operations like get(),put() etc using thin client
protocol which uses tcp socket communication with the Ignite server. I would
like to know if similarly we can send a request to start a transaction or
committing / rolling back transaction.  




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction operations using the Ignite Thin Client Protocol

[Evgenii Zhuravlev]

Could you tell, what do you understand as ignite Thin Client Protocol?

Evgenii

2018-01-08 12:39 GMT+03:00 kotamrajuyashasvi :

> Hi
>
> Thanks for your response.
> I would like to know if Transaction operations on Ignite cache at key-value
> level(not SQL) can be performed using the Thin Client Protocol.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Re: Transaction operations using the Ignite Thin Client Protocol

[kotamrajuyashasvi]

Hi

Thanks for your response. 
I would like to know if Transaction operations on Ignite cache at key-value
level(not SQL) can be performed using the Thin Client Protocol.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite & unixODBC and truncating text

[Alexey Popov]

Hi Bagsuir,

What Ignite version are you using?

Could you please share a reproducible example of the issue you have?
Or can you try the C# example attached (VS 2017)?

Thank you,
Alexey

odbcvarchar.cs
  



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Transaction operations using the Ignite Thin Client Protocol

[Evgenii Zhuravlev]

Hi,

Transactional SQL is not available yet, it will be fully available when
this ticket will be implemented:
https://issues.apache.org/jira/browse/IGNITE-3478

Evgenii

2018-01-08 12:12 GMT+03:00 kotamrajuyashasvi :

> Hi
>
> I would like to perform Ignite Transaction operations from a C++ program
> using the Ignite Thin Client Protocol. Is it possible to do so ? If this
> feature is not available now, will it be added in future ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>

Transaction operations using the Ignite Thin Client Protocol

[kotamrajuyashasvi]

Hi

I would like to perform Ignite Transaction operations from a C++ program
using the Ignite Thin Client Protocol. Is it possible to do so ? If this
feature is not available now, will it be added in future ? 



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/