Re: Unable to start 2 server nodes on same machine

2017-01-09 Thread chaitanya kulkarni
Btw this was v 1.4.0 On Jan 10, 2017 07:12, "chaitanya kulkarni" <9...@gmail.com> wrote: > Hi, > > For my topology- I need all nodes to be server nodes - which share data > with each other on demand.I've configured them to use same multicast > address so they can discover each other /

Re: Simple Compute API for SQL returned data.

2017-01-09 Thread Denis Magda
Hi, There is a set of opened tickets that might be related to this topic https://issues.apache.org/jira/browse/IGNITE-4509 -- Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Simple-Compute-API-for-SQL-returned-data-tp9962p9981.html Sent from the Apache

Re: Simple Compute API for SQL returned data.

2017-01-09 Thread vkulichenko
I would recommend to create a ticket with design proposal and share it on dev list. You will get much better feedback there. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Simple-Compute-API-for-SQL-returned-data-tp9962p9980.html Sent from the Apache

Re: Affinity

2017-01-09 Thread Tejashwa Kumar Verma
Hi Val, Did you got the chance to have a look of explain plan? Please provide your comments. It will be great help thanks -Tejas On Mon, Jan 9, 2017 at 11:55 AM, Tejashwa Kumar Verma < tejashwa.ve...@gmail.com> wrote: > Hi Val, > > Please have a look in execution plan of the query and please

Update value in stream transformer

2017-01-09 Thread rishi007bansod
I want to update current value based on previous value in data streamer, so I am using stream transformer. But initially when cache is empty I want to add entries in cache(using same data streamer) as it is without update. In case of stream transformer it provides initial null values. I want to

Re: Trigger query in ignite

2017-01-09 Thread Yakov Zhdanov
You can also use jdk timers. --Yakov 2017-01-06 13:15 GMT+03:00 rishi007bansod : > Is there any way we can trigger query at some fixed time interval in > ignite(So that query is written only single time initially and it gets > called at defined time interval). Is there

Re: Trigger query in ignite

2017-01-09 Thread rishi007bansod
Does ignite have any *time based event(scheduling)* on *ignite data streamer* by which we can trigger some operation on data added by streamer into cache?(Ignite cache have event on get/put operations but there is no time based event) -- View this message in context:

Re: Efficient way to get partial data of a cache entry

2017-01-09 Thread Yakov Zhdanov
I would suggest calling cache.invoke() and return needed result without altering the entry. Or compute.affinityCall() and do local get inside callable and computing and returning the result.

Re: Efficient way to get partial data of a cache entry

2017-01-09 Thread Andrey Mashenkov
Hi Shawn, #1 way is most unefficient way to get entry by the known key, due to SQL parsing and planning overhead. #2 way can cause unwanted deserialization in case of big value objects. #3 way look like the most efficient way if you need the only field or few fields of big value object.

Re: Efficient way to get partial data of a cache entry

2017-01-09 Thread dkarachentsev
Probably 1 and 3 would be the most effective ways if you're getting objects on affinity node [1], not use CacheMemoryMode#OFFHEAP_VALUES mode and CacheConfiguration.setCopyOnRead() is set to false (for query also with Query.setLocal() set to true). But copyOnRead = false flag could be the cause

答复: compute SQL returned data.

2017-01-09 Thread Shawn Du
Thanks, I already figure it out just As you mentioned. -邮件原件- 发件人: dkarachentsev [mailto:dkarachent...@gridgain.com] 发送时间: 2017年1月9日 17:24 收件人: user@ignite.apache.org 主题: Re: compute SQL returned data. Hi Shawn, For map-reduce operations is most suitable ComputeTask [1], which has

Re: compute SQL returned data.

2017-01-09 Thread dkarachentsev
Hi Shawn, For map-reduce operations is most suitable ComputeTask [1], which has map/reduce methods. In map() method you may select nodes on which start processing according to key (refer Ignite.affinity() [2,3]). Result will be reduced and returned to the client. In summary, client invokes SQL