Re: Simple GETs/PUTs which one is better - Rest API, Thin , Thick OR Java API

Note: It's better to use DataStreamer for a large data sets. In case if you want to work with very small data sets from 1 to 5 it's better to use just key value api 2017-12-28 9:37 GMT+03:00 Evgenii Zhuravlev : > Hi, > > From a performance perspective, I would recommend using Java API. For > exa

Re: Simple GETs/PUTs which one is better - Rest API, Thin , Thick OR Java API

Hi, >From a performance perspective, I would recommend using Java API. For example, for data inserting data, DataStreamer will show better performance: https://apacheignite.readme.io/v2.3/docs/data-streamers Evgenii 2017-12-28 8:49 GMT+03:00 Naveen : > Hello Igniters > > AM using 2.3 > > My use

Simple GETs/PUTs which one is better - Rest API, Thin , Thick OR Java API

Hello Igniters AM using 2.3 My use case is, I have around 20 tables, each of them will have around 500 to 1000 million (1 trillion) records and need to retrieve one to 5 records at a time and insert one to 5 records at one go. Which approach works better for this requirement REST API Thin dr

Re: Problem with creating table and insert data

Thank you very much. This is the answer. So, I understend that in ODBC best equivalent of TEXT type is LONGVARCHAR? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

H2 console - GridH2QueryContext is not initialized

Hi, I was trying to explore H2 console in my application, but when I was trying to query a cache I got below error. can you please tell me how to configure or fix it ? SELECT * FROM "tradingMembersCache".TRADINGMEMBERS; General error: "java.lang.IllegalStateException: GridH2QueryContext is not

Re: Ignite Grid is in invalid state

Finally saw this message SEVERE: Failed to send message: null java.io.IOException: Failed to get acknowledge for message: TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage [sndNodeId=null, id=695a4a99061-22773fcd-a690-4be4-8415-c9bb471b3089, verifierNodeId=null, topVer=0, p

Re: Ignite Grid is in invalid state

thanks After I did that. I stopped my remote cluster and restarted the remote cluster and then the client node in the spring code. and now its sitting here after calling this line ignited = Ignition.start(System.getProperty(IGNITE_CONFIG_FILE_PROP)); has not returned from this line - should I have

Re: Ignite Grid is in invalid state

You used try-with-resources block when starting the instance: try(Ignite ignited = Ignition.start(System.getProperty(IGNITE_CONFIG_FILE_PROP))){ ignited.active(true); ctIgnite = ignited; } When this block is completed, instance is closed, therefore you get exceptions afterwards. Get r

Re: Ignite Grid is in invalid state

the actual failure is happening here which is after ignite instance is returned. Should this be in try block or why whold it go nuts. here is the stack trace. /this.labelCache = this.igniteInstance.getOrCreateCache(IGNITE_LABEL_CACHE);/ Caused by: org.springframework.beans.BeanInstantiati

Ignite Grid is in invalid state

I am seeing following error when I enable persistence mode. [main] - ERROR - Failed to get Ignite Grid is in invalid state to perform this operation. It either not started yet or has already being or have stopped [igniteInstanceName=null, state=STOPPED] Some background My servernode is runningon

Re: Problem with creating table and insert data

Hello, It looks like 'text' data type is not supported by ODBC driver [1]. Please try the following DDL command 'CREATE TABLE test_md5 (id int PRIMARY KEY, userkey varchar(255), server varchar(255), tsession varchar(255), tpost varchar(255), tget varchar(255), adddate int)'; [1] https://apacheig

Problem with creating table and insert data

Hi, I have problem with creating table and insert example data. I use PHP, ODBC and Apache Ignite. I create simple script to do it: // create table: $sql = 'CREATE TABLE test_md5 (id int PRIMARY KEY, userkey varchar(255), server text, tsession text, tpost text, tget text, adddate int)'; $ignite-

Re: Rest API PUT command syntax

Hi Alexey, Yes, you are absolutely correct. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Rest API PUT command syntax

Yes, its getting stored as string, not as individual fields or properties of an object. Thanks naveen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Rest API PUT command syntax

Slava, I think what you suggested would add the "{" partyId":"P10002",...}" value as a String. My guess was Naveen had a value of a custom type. My understanding is Ignite currently does not try to cast provided value to a custom type before invoking cache.put.

Re: Rest API PUT command syntax

Hi Naveen, Yes, PUT command can be used in order to update a record. In accordance with the spec https://apacheignite.readme.io/docs/rest-api#put it requires 3 mandatory parameters: - key - key - val - new value. you need to provide all properties. unfortunately, there is no capa

Re: Rest API PUT command syntax

Thin Client protocol (coming in 2.4) is a faster and more feature-rich binary alternative to REST. It supports arbitrary objects as well. See https://cwiki.apache.org/confluence/display/IGNITE/IEP-9+Thin+Client+Protocol . For now you can try nightly builds or build Ignite from sources. Thanks, Pa

Re: Rest API PUT command syntax

I quickly looked at ignite REST implementation and it seems you can only use it to add string keys and values only. You might contact Ignite developers on the DEV list and ask to extend REST API to support keys and values of arbitrary types.

Re: ComputeTask is including Nodes for ComputeJobs prematurely

Continuation of this thread is here: http://apache-ignite-users.70518.x6.nabble.com/ignite-compute-ClusterGroup-is-broken-td18655.html пн, 27 нояб. 2017 г. в 3:30, Chris Berry : > Affinity is not affected by IgniteCompute. My mistake. > I get a hold of an IgniteCompute _before_ the Affi

Rest API PUT command syntax

Hi Am using 2.3 Trying to use Rest API to put a record into cache, but not finding the correct syntax and logs also does not show anything. Here is the REST url for GET, http://10.144.114.115:8080/ignite?cmd=get&key=P10002&cacheName=EDIF-CUSTOMER Here is the data {"successStatus":0,"af

Re: Implementing security for Rest API

You need to develop a security plugin yourself or look for existing implementation outside Apache Ignite. The is a blog post on how to develop a security plugin. Ignite docs provide some basic info on plugins

Implementing security for Rest API

Hello All I am using Ignite 2.3 Planning to expose rest API for end users for doing GETs and PUTs, how can we secure the cluster, only authorized users should be able to connect to the cluster not every one. Thanks Naveen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/