RE: Over clause in ignite

I am not the intended recipient of this email From: Sriveena Mattaparthi [mailto:sriveena.mattapar...@ekaplus.com] Sent: Wednesday, October 24, 2018 11:14 AM To: user@ignite.apache.org Subject: Over clause in ignite Do we support over() clause in ignite SQL queries like select count(*) over()

Over clause in ignite

Do we support over() clause in ignite SQL queries like select count(*) over() totalrecords from EMPLOYEE; please confirm. Thanks & Regards, Sriveena "Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain

RE: OVER() clause in ignite

Do we support over() clause in SQL in ignite like select count(*) over() totalrecords from EMPLOYEE; please confirm. Thanks & Regards, Sriveena "Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential

OVER() clause in ignite

Do we support over() clause in SQL in ignite like select count(*) over() totalrecords from EMPLOYEE; please confirm. Thanks & Regards, Sriveena "Confidentiality Notice: The contents of this email message and any attachments are intended solely for the addressee(s) and may contain confidential

remote filter for ContinuousQuery on C#

hi, how i can subscribe to just 1 object? The documentation is not clear about how to create Remote Filters/Scan Filters. Below is is my code. i just need to be notified to 1 particular object(id = 1), not all. using Apache.Ignite.Core; using Apache.Ignite.Core.Binary; using

Re: Is there a provision to apply predicate on values in cache?

If you adjust your data model to be a more traditional 1:M relationship it would Just Work. But you still don’t have to do it on the client side. If you use ignite.compute().broadcast(…) you can send the query out to your cluster, have the scans happen on the server side and only send the

Is there a provision to apply predicate on values in cache?

Hi, My cache is like : key vs list of models. (key, ArrayList) I know that we have ScanQuery to apply filter conditions on keys. Is there a provision to apply this on values against a particular key at ignite server node? Otherwise I will have to pull these list of values to my client side and

Re: Total Size seems to keep growing

Hi. No, I did not try to increase the data region. But as you also specified that will not fix the current problem I guess. -- Alper Tekinalp Software Development Team Lead Evam Streaming Analytics www.evam.com

Re: Total Size seems to keep growing

Hello! Have you tried increasing size of your data region? I have tried it on master with 300M region, increase is still there but very slight. I'm not entirely sure what causes it. Regards, -- Ilya Kasnacheev вт, 23 окт. 2018 г. в 15:05, Alper Tekinalp : > Also my Ignite version is 2.6. >

RE: Ignite Query Slow

Any help on this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Total Size seems to keep growing

Hi. After running more than an hour, the results are as in the attached file. It seems to growing constantly. On Tue, Oct 23, 2018 at 2:31 PM Ilya Kasnacheev wrote: > Hello! > > Does it keep growing indefinitely or it will taper off at some point? Did > you check that? > > Regards, > -- > Ilya

Re: Total Size seems to keep growing

Also my Ignite version is 2.6. On Tue, Oct 23, 2018 at 3:02 PM Alper Tekinalp wrote: > Hi. > > After running more than an hour, the results are as in the attached file. > It seems to growing constantly. > > On Tue, Oct 23, 2018 at 2:31 PM Ilya Kasnacheev > wrote: > >> Hello! >> >> Does it keep

Re: Ignite default partition to node mapping is not balanced

Hello! It was removed as part of https://issues.apache.org/jira/browse/IGNITE-3477 Regards, -- Ilya Kasnacheev вт, 23 окт. 2018 г. в 14:46, kotamrajuyashasvi : > Hi > > can you provide more info on why fair affinity was removed . If its not a > critical problem and can compromise on we would

Re: Ignite default partition to node mapping is not balanced

Hi can you provide more info on why fair affinity was removed . If its not a critical problem and can compromise on we would like to use it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Total Size seems to keep growing

Hello! Does it keep growing indefinitely or it will taper off at some point? Did you check that? Regards, -- Ilya Kasnacheev вт, 23 окт. 2018 г. в 13:40, Alper Tekinalp : > Hi. > > Actually they are not same records. > > Run code on java 1.8.0_111 on a MacBook Pro. > > On Tue, Oct 23, 2018

Re: Total Size seems to keep growing

Hi. Actually they are not same records. Run code on java 1.8.0_111 on a MacBook Pro. On Tue, Oct 23, 2018 at 1:31 PM Alper Tekinalp wrote: > Hi all. > > I have a code attached. Basically I keep adding and deleting same records > to/from cache. But getTotalAllocatedSize from DataRegionMetrics

Total Size seems to keep growing

Hi all. I have a code attached. Basically I keep adding and deleting same records to/from cache. But getTotalAllocatedSize from DataRegionMetrics seems to keep growing. Are there any comments? -- Alper Tekinalp Software Development Team Lead Evam Streaming Analytics www.evam.com

Re: Ignite default partition to node mapping is not balanced

Hello! No, it is not possible. There was Fair Affinity in 1.x which tried to do that, but had other problems. When using Rendezvous affinity, the distribution will always be somewhat random. Regards, -- Ilya Kasnacheev пн, 22 окт. 2018 г. в 17:06, kotamrajuyashasvi : > Hi > > Apart from

Re: GridMergeTable

Hello! GridMergeTable is H2 table which is stored on Java heap. This means you have to plan carefully and make sure that you always have enough heap for merge/sort/group. Regards, -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Quering with PHP PDO returns null for all column values except the 1st one

Hello, PHP PDO returns null for all column values except the 1st one. Using PHP odbc_connect returns all column values. array(10) {  ["ORGID"]=>  string(1) "2"  [0]=>  string(1) "2"  ["FIRSTNAME"]=>   NULL  [1]=>  NULL  ["LASTNAME"]=>  NULL  [2]=>  NULL  ["RESUME"]=>  NULL  [3]=>   NULL  

Re: npe: Failed to reinitialize local partition

Tks! I applyed the patch from the issue.And the NPE was fixed. But another problems happen: As the issue says: Steps to reproduce: Ignite server region1 (with persistence) region2 (without persistence) client cache1a from region1 – with custom affinity cache2a fom region2 – with custom affinity

Automated cache generation to clone a SQL schema?

Currently using the Web Console to export Ignite cache definitions (XML) and Java model objects, and the resulting caches are loaded using .load(). Since the DB schema changes on a regular basis, I would like to automate this process somehow. Short of extricating this code directly from within