Re: slow query performance against berkley db

Thanks Stan for looking into it. Unfortunately, it still takes 23 sec on 240gb RAM system, the corresponding EXPLAIN PLAN [[SELECT ST.ENTRYID, ST.ATTRNAME, ST.ATTRVALUE, ST.ATTRSTYPE FROM "objectclass".IGNITE_OBJECTCLASS T /* "objectclass".OBJECTCLASSNDEXED_ATTRVAL_IDX:

Re: slow query performance against berkley db

Dear all Request you to kindly suggest me if my approach is wrong ? The idea of replacing berkley db with Ignite would not work out if the query is slow , whats the best model to be used with Ignite for my usecase. Thanks, Rajesh On Fri, Feb 9, 2018 at 9:38 AM, Rajesh Kishore <rajesh1

ignite support for multii data center replication

Hi, Does Ignite replication works on Multi Data Center /WAN ? Regards, -Rajesh

Re: slow query performance against berkley db

Igniters any pointers pls. Regards, Rajesh On Wed, Feb 7, 2018 at 9:15 AM, Rajesh Kishore <rajesh10si...@gmail.com> wrote: > Hi Dmitry, > > Thanks a ton. > > What is not convincing to me is with just *.1 M in main table and* *2 M > records in other table * , sql query

Re: code sample for cluster configuration

sistance presented in > https://apacheignite.readme.io/docs/distributed-persistent-store. > > > 2018-02-07 13:14 GMT+03:00 Rajesh Kishore <rajesh10si...@gmail.com>: > >> Hi, >> >> I want to try a two node setup for Ignite cluster with native file based >

code sample for cluster configuration

Hi, I want to try a two node setup for Ignite cluster with native file based persistence enabled . Any samples, or pointer ? -Rajesh

Re: slow query performance against berkley db

formance. If > your query does some level of scanning, then the more nodes you add, the > faster it will get. > > D. > > On Tue, Feb 6, 2018 at 5:02 PM, Rajesh Kishore <rajesh10si...@gmail.com> > wrote: > >> Hi All >> Please help me in getting the pointers,

Re: slow query performance against berkley db

Feb 2018 6:11 p.m., "Rajesh Kishore" <rajesh10si...@gmail.com> wrote: > Further to this, > > I am re-framing what I have , pls correct me if my approach is correct or > not. > > As of now, using only node as local cache and using native persistence > fi

Re: slow query performance against berkley db

ve query takes *24 sec* to retrieve the records which we feel defeats the purpose , our application existing berkley db can retrieve this faster. Question is - a) I have attached my application models & client code , am I doing something wrong in defining the models and cache configuration. Ri

Re: slow query performance against berkley db

her Berkley DB node and continue to work? Ignite is not just SQL DB, Ignite is a distributed data grid, it's strongly consistent and HA database, please make this into account when comparing it with other solutions. Thanks, Mike. 2018-02-05 9:23 GMT-08:00 Rajesh Kishore <rajesh10si...@gmai

Re: slow query performance against berkley db

Any pointers please Thanks Rajesh On 5 Feb 2018 10:53 p.m., "Rajesh Kishore" <rajesh10si...@gmail.com> wrote: > Hi Christos > > Does that mean Ignite cannot scale well against Berkley dB Incase of > single node? > > Regards > Rajesh > > On 5 Feb 201

Re: slow query performance against berkley db

ly not the > way. > > You need to consider having multiple nodes and portion and collocate your > data before. > > Thanks, > C > > On 5 Feb 2018, at 16:36, Rajesh Kishore <rajesh10si...@gmail.com> wrote: > > Hi, > > We are in the process of evaluating

slow query performance against berkley db

Hi, We are in the process of evaluating Ignite native persistence against berkely db. For some reason Ignite query does not seem to be performant the way application code behaves against berkley db Background: Berkley db - As of now, we have berkley db for our application and the data is stored

[Resolved]Re: Issues with sub query IN clause

quot;.IGNITE_DSATTRIBUTESTORE ST__Z2 /* "Ignite_DSAttributeStore".IGNITE_DSATTRIBUTESTORE_ENTRYID_IDX: ENTRYID = T__Z1.ENTRYID */ ON 1=1 WHERE ST__Z2.ENTRYID = T__Z1.ENTRYID ORDER BY 1], [SELECT __C0_0 AS ENTRYID, __C0_1 AS ATTRNAME, THanks, Rajesh __C0_2 AS ATTR

Re: Issues with sub query IN clause

son') AND (ENTRYID IS ?1): ENTRYID = ST.ENTRYID */ ON 1=1 WHERE ST.ENTRYID = T.ENTRYID (1 row, 1 ms) How should I approach that "Ignite_DSAttributeStore".IGNITE_DSATTRIBUTESTORE full scan can be avoided ? Thanks in advance. -Rajesh On Fri, Feb 2, 2018 at 11:10 PM

Re: Issues with sub query IN clause

My bad still I am using the IN clause with variable parameter. I am exploring other queries. Thanks a ton Rajesh On 2 Feb 2018 10:41 p.m., "Rajesh Kishore" <rajesh10si...@gmail.com> wrote: > Hi Andrey, > > This query remains stuck > "EXPLAIN SELECT store.entry

Re: Issues with sub query IN clause

*/]] Thanks -Rajesh On Fri, Feb 2, 2018 at 5:32 AM, Dmitriy Setrakyan <dsetrak...@apache.org> wrote: > Rajesh, can you please show your query here together with execution plan? > > D. > > > On Thu, Feb 1, 2018 at 8:36 AM, Rajesh Kishore <rajesh10si...@gmail.com>

Re: Issues with sub query IN clause

tion-sql-performance-and-usability-considerations > [2] https://apacheignite.readme.io/docs/affinity- > collocation#section-collocate-data-with-data > > On Thu, Feb 1, 2018 at 3:44 PM, Rajesh Kishore <rajesh10si...@gmail.com> > wrote: > >> Hi All, >> >> As of now,

Issues with sub query IN clause

Hi All, As of now, we have less than 1 M records , and attribute split into few(3) tables with index created. We are using combination of join & IN clause(sub query) in the SQL query , for some reason this query does not return any response. But, the moment we remove the IN clause and use just

RE: default location for ignite file db

ill be created in > the standard system location (e.g. /tmp on Linux) > > to store Ignite’s DB and other files such as logs. > > > > Stan > > > > *From: *Rajesh Kishore <rajesh10si...@gmail.com> > *Sent: *29 января 2018 г. 15:18 > *To: *user@ignite.apache

Re: cache configuration without Key

Thanks Ilya it answers my question On 29 Jan 2018 3:34 p.m., "ilya.kasnacheev" wrote: > Hello Rajesh! > > In Ignite, cache (and SQL table) maps not to one object but to two - key > and > value. > > Keys are unique per cache per cluster. They act as primary key in SQL

Re: default location for ignite file db

covers this topic in details. > > > > Stan > > > > *From: *Rajesh Kishore <rajesh10si...@gmail.com> > *Sent: *29 января 2018 г. 15:04 > *To: *user@ignite.apache.org > *Subject: *default location for ignite file db > > > > Hi All. > > How do we de

Re: starting Ignite server in embedded mode

However, you generally shouldn't need two instances of ignite in the same > application. If you want your application to natively use Ignite and > > have server running alongside it, you can just make API calls on the > server instance, no need to create an additional client for

default location for ignite file db

Hi All. How do we determine the default location for ignite file based DB Thanks in advance -Rajesh

starting Ignite server in embedded mode

Hi All, We have requirement to manage Ignite server and client by the same application in embedded mode. Whats the way forward? Thanks, Rajesh

cache configuration without Key

Hi All, I have a requirement to define a cache class, for which its instance qualifies only for value. public class EntryIndexedAttributes { @QuerySqlField( orderedGroups = { @QuerySqlField.Group( name = "generic_attr_idx", order = 0) , @QuerySqlField.Group( name =

Re: Ignite Index - unique or non unique

any pointers please Thanks, Rajes On Thu, Jan 25, 2018 at 10:07 AM, Rajesh Kishore <rajesh10si...@gmail.com> wrote: > Hi All, > > Wanted to know - what does ignite supports unique or non -unique index. > I have requirement to create non unique index on a field / group

Ignite Index - unique or non unique

Hi All, Wanted to know - what does ignite supports unique or non -unique index. I have requirement to create non unique index on a field / group of field. Whats the way? Also, with the EXPLAIN plan , we can get to know the index used for a query, sometimes my log is not getting generated

Re: query on BinaryObject index and table

t table name should I specify - I did not create table explicitly, do I need to that? How would I create the index? Thanks, Rajesh On Sun, Jan 21, 2018 at 12:25 PM, Denis Magda <dma...@apache.org> wrote: > > > > On Jan 20, 2018, at 7:20 PM, Rajesh Kishore <rajesh10si...@gmail.

query on BinaryObject index and table

Hi, I have requirement that my schema is not fixed , so I have to use the BinaryObject approach instead of fixed POJO I am relying on OOTB file system persistence mechanism My questions are: - How can I specify the indexes on BinaryObject? - If I have to use sql query for retrieving objects ,

index for like criteria

Hi All, My query is on substring index working for Ignite. I am using - data grid , default file system persistence enabled. Let us say, I have Organization POJO and index defined on its field as defined below: public class Organization { /** */ private static final AtomicLong ID_GEN =

Re: how to create Index for binary or byte type value

Hi Val, Would indices be possible on binary data value , I dont think so. I think I will stick with the POJO for now. I have queries on indices and l am not relying on external persistence system. a) What are the different indices type Ignite supports apart from equality i.e does it support the

Re: how to create Index for binary or byte type value

Yes, correct object is stored as byte array As my attribute name is not fixed. I want to have index on different attributes which is not directly visible as the pojo instance variable Rajesh On 19 Jan 2018 3:56 a.m., "vkulichenko" wrote: > Hi Rajesh, > > It's not

how to create Index for binary or byte type value

Hi All, The problem statement is in context of "In-Memory Data Grid" persistence enabled. I have requirement/limitation to store the value of a class's object as byte [] , understood by the application in certain format. IgniteCache cache =

Re: usage of Apache ignite as Key value DB

ersistence SQL quesries work on the entire cache even if items not > in RAM, if you use 3rd party persistence SQL queries will only work on > items in RAM. > > Hope that helps a little. > Mikael > > > Den 2018-01-17 kl. 13:30, skrev Rajesh Kishore: > > Hello Mikael,

Re: usage of Apache ignite as Key value DB

put and so on. > > > Den 2018-01-17 kl. 12:44, skrev Rajesh Kishore: > > This is much informative. Further I want to use key value apis instead of > sql apis which is only given in the example. > The idea is that it should ease my migration process from Berkley dB based > code

Re: usage of Apache ignite as Key value DB

an embed it in your > application), you can't just use the key value store on it's own, a LOCAL > cache would be the closest to a Berkeley DB store. > > Docs at : https://apacheignite.readme.io/docs/data-grid > > > > Den 2018-01-17 kl. 11:05, skrev Rajesh Kishore: > >> H

usage of Apache ignite as Key value DB

need for Ignite. The idea is to replace berkley db apis to Ignite apis to use Ignite as key value DB. I could not find any docs for the usage of ignite libraries to be used in the application. Any pointers please Thanks & Regards, Rajesh Kishore