Re: Ignite SQL

Why does spark.sql() take more time than client.sql() when query is same and is made to ignite dataframe only?? Regards On Tue, 18 Jul, 2023, 10:40 pm Stephen Darlington, < stephen.darling...@gridgain.com> wrote: > “Correct” is hard to quantify without knowing your use case, but option 1 > is pr

Re: Ignite SQL

Just an example. I mean to say a part of my data resides in Ignite, not the complete data. Rest data is present in Spark. On Wed, 19 Jul, 2023, 2:07 pm Stephen Darlington, < stephen.darling...@gridgain.com> wrote: > Why you would have Ignite, a horizontally scalable, in-memory database, to > sto

Re: Ignite SQL

Why you would have Ignite, a horizontally scalable, in-memory database, to store 100 records? > On 19 Jul 2023, at 04:37, Arunima Barik wrote: > > I have a huge dataset and I am keeping few (say 100) rows in Ignite and the > entire dataset remains in Spark > > When I query Ignite I want to wr

Re: Ignite SQL

I have a huge dataset and I am keeping few (say 100) rows in Ignite and the entire dataset remains in Spark When I query Ignite I want to write an Sql query to perform the same. Does option 1 still hold good? On Tue, 18 Jul, 2023, 10:40 pm Stephen Darlington, < stephen.darling...@gridgain.com> w

Re: Ignite SQL

“Correct” is hard to quantify without knowing your use case, but option 1 is probably what you want. Spark pushes down SQL execution to Ignite, so you get all the distribution, use of indexes, etc. > On 14 Jul 2023, at 16:12, Arunima Barik wrote: > > Hello team > > What is the correct way ou

Ignite SQL

Hello team What is the correct way out of these? 1. Write a spark dataframe to ignite Read the same back and perform spark.sql() on that 2. Write the spark dataframe to ignite Connect to server via a thin client Perform client.sql() Regards Arunima

Re: Query default Index in Ignite Sql cache

Thanks Maksim ! On Thu, Jun 23, 2022 at 11:01 AM Maksim Timonin wrote: > Hi, > > > 1. Department object has an id and affinity key on the name(it > doesn't make sense in the real world). Does ignite create an index for > affinity keys as well ? I don't see the affinity key index in the list > be

Re: Query default Index in Ignite Sql cache

Hi, > 1. Department object has an id and affinity key on the name(it doesn't make sense in the real world). Does ignite create an index for affinity keys as well ? I don't see the affinity key index in the list below. You need to configure affinity key with annotations a little bit differently, p

Re: Query default Index in Ignite Sql cache

Thanks for the reply. I have another question on the affinity key index(if any). When we enable sql on ignite, it by default creates an index on the primary key(highlighted in red below). We have created a custom index on deptId(highlighted in red). 1. Department object has an id and affinity key

Re: Query default Index in Ignite Sql cache

SELECT * FROM SYS.INDEXES > 22 июня 2022 г., в 18:38, Surinder Mehra написал(а): > > Hi, > We have defined indexes on sql enabled ignite cache and are able to see > indexes being used while querying. > sqline !indexes also shows those indexes in output. But we cant see default > index created

Query default Index in Ignite Sql cache

Hi, We have defined indexes on sql enabled ignite cache and are able to see indexes being used while querying. sqline *!indexes* also shows those indexes in output. But we cant see default index created by ignite on *primary key *and *affinity key*. We would like to use index on key and affinity ke

Webinar, May 20th: Ignite SQL Essentials (Basics, Memory Quotas, Calcite-powered engine)

Igniters, Some time ago, we united with Igor to produce a webinar about Ignite SQL essentials: https://bit.ly/2WzlCrp Beginners will get a full understanding of our SQL capabilities while experienced Ignite developers will learn more about memory management internals in relation to SQL, will get

Re: 回复: Ignite - SQL Column names Case not preserved.

Hello! I think you should just escape column names properly when using them: SELECT * FROM acc WHERE "accCol1" is null; Regards, -- Ilya Kasnacheev сб, 28 дек. 2019 г. в 23:19, sr.prane...@gmail.com : > Thanks for the suggestion > > I am using Pure SQL to create tables. > I dont know how to

Re: 回复: Ignite - SQL Column names Case not preserved.

Thanks for the suggestion I am using Pure SQL to create tables. I dont know how to use this option on the SQL Create syntax. I tried using the below code. cfg.setCacheConfiguration( new CacheConfiguration().setName("PUBLIC").setSqlSchema("PUBLIC").setSqlEscapeAll(true)

回复: Ignite - SQL Column names Case not preserved.

CacheConfiguration cfg = new CacheConfiguration<>().setSqlEscapeAll(true) This will make sql case sensitive 发送自 Windows 10 版邮件应用 发件人: sr.prane...@gmail.com 发送时间: 2019年12月28日 14:20 收件人: user@ignite.apache.org 主题: Ignite - SQL Column names Case not preserved. Hi Ignite users I have a

Ignite - SQL Column names Case not preserved.

Hi Ignite users I have a simple table created in ignite as below. CREATE TABLE acc ( "accId" VARCHAR PRIMARY KEY, "accCol1" VARCHAR, "accCol2" INT, "accCol3" VARCHAR, "accCol4" BOOLEAN ); On the above table from sqlLine client a simple query like below is also failing without recognisin

Re: Ignite SQL table ALTER COLUMN and RENAME COLUMN

Please check out this note: https://www.gridgain.com/docs/8.7.6/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes There is a hacky way to change the type if you're in development but if you're in prod then you need to add new columns instead. - Denis On Th

Re: Ignite SQL table ALTER COLUMN and RENAME COLUMN

Favas, It’s possible to remove a column and add another one using ALTER COMAND SQL statement, but currently you can't change a column’s type. Note, that removing a column and adding another one with the same name but with a different type can lead to data corruption. Denis On 10 Oct 2019, 09:51

Ignite SQL table ALTER COLUMN and RENAME COLUMN

Hi, Is there a way in ignite to ALTER the column to change the data type/nullable property and also RENAME of column? I saw in ignite documentation that it will add in upcoming releases. Which release it is planning for? Regards, Favas

Re: Ignite SQL table schema metadata

Hello! Ignite does not enforce length of VARCHAR fields, you can store any String in VARCHAR fields, so you should neither expect not use that value. Regards, -- Ilya Kasnacheev вт, 8 окт. 2019 г. в 15:22, Muhammed Favas < favas.muham...@expeedsoftware.com>: > Hi, > > > > Is there a way in ig

Ignite SQL table schema metadata

Hi, Is there a way in ignite to get the table schema details like column name, specific sq. data type (including length in case varchar type), index details etc?. I have tried one of the REST API given in ignite http://host:port/ignite?cmd=metadata&cacheName=partionedCache. Everything returne

Re: Apache Ignite SQL Table Transaction Not Working

adme.io/docs/transactions#section-ignitetransactions Regards, Igor On Mon, Sep 23, 2019 at 10:33 AM Arpit Gadle wrote: > Hi All, > > I want to test transaction with Apache Ignite SQL table. For this I > created a small program. What the program does is > > 1. Start a ignite serv

Apache Ignite SQL Table Transaction Not Working

Hi All, I want to test transaction with Apache Ignite SQL table. For this I created a small program. What the program does is 1. Start a ignite server node from the code itself. 2. Create a JDBC url to local ignite server 3. Get a JDBC connection, create the table 4. Get a JDBC connection, set

Re: updating a composite Key in Ignite SQL Table

Hi Mahesh, It is not planned at the moment. I think you could simply replace this with a DELETE and INSERT as a workaround. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

updating a composite Key in Ignite SQL Table

Hi, We know, currently, a composite key cannot be updated in a SQL table. What would be useful is if an update to a composite key, does not cause a conflict with other keys, then it should be allowed however, if the update causes a duplicate, an exception should be thrown Could this feature b

Re: LIKE operator on Array column in Apache ignite SQL

ov > *Sent:* Saturday, March 16, 2019 05:06 AM > *To:* user@ignite.apache.org > *Subject:* Re: LIKE operator on Array column in Apache ignite SQL > > > > Hi, > > Ignite SQL engine supports only the next types: > > https://apacheignite-sql.readme.io/docs/data-types >

RE: LIKE operator on Array column in Apache ignite SQL

customized function for it. Best Regards, James Wang M/WeChat: +86 135 1215 1134 From: aealexsandrov mailto:aealexsand...@gmail.com>> Sent: Saturday, March 16, 2019 05:06 AM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: Re: LIKE operator on Array column in Apache ig

Re: LIKE operator on Array column in Apache ignite SQL

Hi, Ignite SQL engine supports only the next types: https://apacheignite-sql.readme.io/docs/data-types Also all existed functions you can see here: https://apacheignite-sql.readme.io/docs/sql-reference-overview So there is no way to work with arrays as DataTypes even if you set them as type

LIKE operator on Array column in Apache ignite SQL

Hi, Is there a way we can do like query on array field in ignite sql. Able to retrieve records on exact search using array_contains function like select * from market where array_contains(name,'LACL') - here name is an array object -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Anyone using Apache Ignite SQL as a SOR?

So anyone attempting to use Apache Ignite SQL as system of record?

Re: Ignite SQL : Index on primary Key

Hello! Can you please show cache/table configuration, original query and its EXPLAIN (all rows)? Regards, -- Ilya Kasnacheev ср, 13 февр. 2019 г. в 18:24, mahesh76private : > But we faced index does not exist exception, when joining with a primary > key > into another table on Ignite 2.7.0. >

Re: Ignite SQL : Index on primary Key

But we faced index does not exist exception, when joining with a primary key into another table on Ignite 2.7.0. regards Mahesh -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL : Index on primary Key

Hello! In Apache Ignite 2.7.0 it is now created by default. Regards, -- Ilya Kasnacheev вт, 12 февр. 2019 г. в 08:26, mahesh76private : > looks like a index is not not created automatically on a primary key... > Shouldn't it be automatic? > > faced exceptions while trying to execute join. > >

Ignite SQL : Index on primary Key

looks like a index is not not created automatically on a primary key... Shouldn't it be automatic? faced exceptions while trying to execute join. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

SQL. Two usecases - Big, Data, visualizations with databases, and sheets that shows large tables, where is sure wants to get some quick metric Variance and STDDev is should be good... ML side Dataset class already exposes these right ?... We are okay there for now. -- Sent from: http://a

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

Are you ready to use them as a part of Ignite ML functions (part of stat or math package?) or you need in SQL only? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

Hello! As far as my understanding goes, it's a very non-trivial thing to calculate median across nodes. You end up needing to pull all the data in one place or use some complicated iterative approach. Same thing probably applies to std, though there might be shortcuts. Still it's not as easy as j

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

The simple usecase is as follows In big data visualization, for drawing graphs, one needs to know the standard characteristics of a measure column (numeric column) to draw and plan out graphs. ideally, we need to this support in Ignite itself so that client code does not pull large columns (run

Re: IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

The weird thing about this is that the documentation says they do exist: https://apacheignite-sql.readme.io/docs/aggregate-functions (They don’t.) At the very least we need to update the documentation. Regards, Stephen > On 30 Jan

IGNITE-3180 : please add support for median, stddev, var in Ignite SQL

Looks like these are not supported currently, please add them in Ignite 2.8 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to get the column names(or fieldsNames) of existing ignite sql table

1. Check out this thread to get a list of fields: http://apache-ignite-users.70518.x6.nabble.com/Get-Field-Names-In-Select-Query-td25258.html 2. "Create table..." command creates a cache under the hood. https://apacheignite-sql.readme.io/docs/create-table -- Sent from: http://apache-ignite-user

Re: How to get the column names(or fieldsNames) of existing ignite sql table

From what I understand, the first cache created by getOrCreate, where you will be using to run the SQLFieldsQuery to create your table, is just a dummy.  So name it as anything other than "Persons".  Yes.  It may sound counter intuitive. I'm still learning so may learn the reason behind it late

Re: How to get the column names(or fieldsNames) of existing ignite sql table

Hi , Thank You for Reply, *And for question 2, I think, yes, from my learning, SQL Create Table always create another cache with default naming like SQL_PUBLIC_ . But according to manual, you can override the name by supplying options after "with".* IgniteCache cache = ignite.getOrCreateCache(

Re: How to get the column names(or fieldsNames) of existing ignite sql table

Hi , *And for question 2, I think, yes, from my learning, SQL Create Table always create another cache with default naming like SQL_PUBLIC_ . But according to manual, you can override the name by supplying options after "with".* But For execute a query we should have Ignitecache object which is

Re: How to get the column names(or fieldsNames) of existing ignite sql table

Hello, I don't think you can get all the tables created in a cache by SQL. I'm learning this stuff and hit the same questions and figure I can find it out by the following steps in code (I'm coding c# and don't know if the methods apply in Java). Get all cache names from IIgnite by GetCachename

Re: How to get the column names(or fieldsNames) of existing ignite sql table

Hello. On 17.11.2018 13:25, siva wrote: > Quetions: > === > 1.How to get the existing table columnNames ? > > i am trying to use this query but its throwing exception > > *select COLUMN_NAME from INFORMATION_SCHEMA.COLUMNS where > TABLE_NAME='Person'* You need query with setLocal(true). I don

How to get the column names(or fieldsNames) of existing ignite sql table

Hi, Creating tables using sql api IgniteCache cache = ignite.getOrCreateCache(new CacheConfiguration<>().setSqlSchema("PUBLIC").setName(cacheName)); createtableQuery = create table Person(name varchar ,id int primarykey) with "template ="Replicated". cache.query(new SqlFieldsQ

Re: Apache Ignite SQL- read Only User Creation

Hi, Yes, when you are using ignite advance security (not GridSecurityProcessor interface) then you are able only to manage the password. https://apacheignite.readme.io/docs/advanced-security provides the simple password authentification security. You can only: 1)Create the user - https://apachei

Re: Apache Ignite SQL- read Only User Creation

Thanks Andrei, I ceated user but can't alter user except for changing password, The user is able to delete rows or truncate tables which I dont want except ignite user. Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite SQL- read Only User Creation

Hi, I believe that you said about https://apacheignite.readme.io/docs/advanced-security It will provide the possibility to create/drop/alter the users. Also, it provides the only simple authentification with the password. You can't set the rules like read-only using it. Also, you can try to impl

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

The above error appears to be an issue in org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot in a mismatch between the readExternal() and writeExternal() methods. I've made a change locally and it fixed the error and also the testing so far seems to show that the queries return the c

Apache Ignite SQL- read Only User Creation

Hello Ignite team, We are using Apache Ignite are SQL reporting cluster . Ignite Persistence and authenticationEnabled . We need a read only user role apart from ignite user, is there any role or a way to create user with read only previllages? Thanks -- Sent from: http://apache-ignite-users

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Thanks Vlad / Dmitry, I was able to download the nightly build from teamcity as a guest. However I'm now getting the following error when trying to add data to the cache. Any ideas? class org.apache.ignite.IgniteException: Failed to get affinity mapping from node: TcpDiscoveryNode [id=eeef1e32-db

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Dmitriy, I wanted to suggest this, but looks like we do not have direct links for regular distribution. User can download it from TeamCity, but username/password is needed for this. May be I missing something. On Thu, Aug 16, 2018 at 11:44 AM Dmitriy Setrakyan wrote: > I also want to point out

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

I also want to point out that Ignite has nightly builds, so you can try them instead of doing your own build as well. https://ignite.apache.org/download.cgi#nightly-builds D. On Thu, Aug 16, 2018 at 1:38 AM, Vladimir Ozerov wrote: > Hi, > > There were a lot of changes in the product since 2.3

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Hi, There were a lot of changes in the product since 2.3 which may affect it. Most important change was baseline topology, as already mentioned. I am aware of a case when incorrect result might be returned [1], which is already fixed in *master*. Not sure if this is the same issue, but you may try

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Thanks for getting back, but we do not use Ignite's native persistence. Anything else changed from 2.3 to 2.4 to cause this around SQL Queries? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Hi, Do you use persistence? If so, please check and set up Baseline topology for your cluster which describes a set of server nodes that are used to store data. The reason for this behaviour may be a simple fact that some of your nodes are

Ignite SQL Queries not getting all data back in ignite 2.4 and 2.6

Hi, we have used this query in ignite 2.3 for a while now. But we had some data streamer exceptions that seemed to have been resolved on 2.4, so we decided to upgrade. However, in 2.6 and also downgrading to 2.4 we have been seeing this issue, that a SQL query does not return the data that is in ca

Re: Questions about how Ignite SQL Works

en 2018-07-30 kl. 09:30, skrev Lijun Cao: >> Hi: >> >> I have referenced How Ignite SQL Works document but I still have got 2 >> questions. >> >> The first question is, when I load data to Ignite cluster(3 nodes) in first >> time, the data is stored bot

Re: Questions about how Ignite SQL Works

for the query point of view it's no difference if you have (native) persistence enabled or not, it works the same way. Mikael Den 2018-07-30 kl. 09:30, skrev Lijun Cao: Hi: I have referenced *How Ignite SQL Works *document but I still have got 2 questions. The first question is,

Re: Questions about how Ignite SQL Works

2018, 1:00 PM Lijun Cao <641507...@qq.com > <mailto:641507...@qq.com>> wrote: > Hi: > > I have referenced How Ignite SQL Works document but I still have got 2 > questions. > > The first question is, when I load data to Ignite cluster(3 nodes) in first > time, the

Re: Questions about how Ignite SQL Works

Don't know about the first question but if you have persistence enabled ignite will load the data on startup Regards, Prem On Mon, Jul 30, 2018, 1:00 PM Lijun Cao <641507...@qq.com> wrote: > Hi: > > I have referenced *How Ignite SQL Works *document but I still have got 2

Questions about how Ignite SQL Works

Hi: I have referenced How Ignite SQL Works document but I still have got 2 questions. The first question is, when I load data to Ignite cluster(3 nodes) in first time, the data is stored both on RAM and disk(I enabled local persistence), so which area does Ignite query on in this situation

RE: RDBMS as backend for Ignite SQL

same cache, then probably – you’d have to implement your own CacheStore that would work with multiple DBMS. That might be pretty tricky though. If you’re asking whether you can use another SQL engine for Ignite SQL, then no – Ignite is backed by embedded H2 engine, and SQL queries to Ignite will

Re: RDBMS as backend for Ignite SQL

ersisted backend for Ignite SQL ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > -- Best regards, Andrey V. Mashenkov

RDBMS as backend for Ignite SQL

Is it possible to use various RDBMS as persisted backend for Ignite SQL ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

Yes, it is working. Thanks, Ilya -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

Hello! I believe this is the case! Have you checked? Regards, -- Ilya Kasnacheev 2018-05-23 12:38 GMT+03:00 the_palakkaran : > @ilya So does this mean an SQL field query executed on a cache as "select > custNo from Customer where custId like '%SAM%'" will work and return values > ? > > > > --

Re: LIKE operator in Apache ignite SQL

@ilya So does this mean an SQL field query executed on a cache as "select custNo from Customer where custId like '%SAM%'" will work and return values ? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: LIKE operator in Apache ignite SQL

LIKE in Apache Ignite should work as it is described in SQL standard, where '%' means 'any characters'. Note that indexes can only be used with LIKE if wildcard is not used at first position: foo LIKE '%bar%' - no index. foo LIKE 'bar%' - can use index. Regards, -- Ilya Kasnacheev 2018-05-23

LIKE operator in Apache ignite SQL

Hi, will like operator work in Apache ignite in the same way as in Oracle? I saw somewhere it should be uses as key=%value%. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Why Ignite SQL can not support transactional mode transaction

Hello, In short, Apache Ignite's SQL engine executes DML statements on top of committed data without creating a snapshot. So, in order to provide fully transactional SQL, SQL engine should be built on top of new MVCC protocol. Please take a look at the following Ignite enhancement proposal (IEP):

Re: Why Ignite SQL can not support transactional mode transaction

hi vkulichenko I may not express myself clearly，What I mean is that since KV storage supports transactions, why doesn't SQL support transactional transactions? Dose Transaction impact other session‘s select SQL？ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Why Ignite SQL can not support transactional mode transaction

This is being developed now, here is the ticket you can track: https://issues.apache.org/jira/browse/IGNITE-4191 -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Why Ignite SQL can not support transactional mode transaction

hi I know that Ignite support transactional mode transaction as KV store, then why SQL not support? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Sql query problem using IN clause

There is a suggested workaround in https://apacheignite-sql.readme.io/docs/performance-and-debugging#section-sql-performance-and-usability-considerations, item 2 As a workaround...you can rewrite the query in the following way: select p.name from Person p join table(id bigint = ?) i on p.id = i.i

Re: Ignite Sql query problem using IN clause

Has it been fixed in 2.4 ? Looks like it is not, when I generate the explain plan for a query which has a composite key Here are the queries I ran and explain plan results. When I use IN, it uses the full table scan, otherwise It does look up on primary key explain SELECT * FROM "MapLonglistCach

Re: Ignite Sql Query Execution time is too long

Siva, The execution plan shows, that no indexes are used. If you create an index on *EntityType* field, it should make the performance better. Also if you make all data be stored in memory, then performance of select queries will be better. Otherwise you will be limited by the performance of your

Re: Ignite Sql Query Execution time is too long

Have you tried adding indexes to frequently searched fields ? Indexing can make searching the cache quite faster -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite Sql Query Execution time is too long

Hi, We have 2 nodes(client&server) and using ignite native persistence. In cache we have around 3lakh records. We are querying from Client node and using cursor.getAll() to get the resultset. If we execute a query which needs to returns 10k records (ex:select * from Entity Where EntityType='Igni

Re:Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Thanks D. At 2018-04-01 23:07:25, "Dmitriy Setrakyan" wrote: Hi Fvyaba, In order to avoid memory overhead per table, you should create all tables as part of the same cache group: https://apacheignite.readme.io/docs/cache-groups D. On Mon, Mar 26, 2018 at 7:26 AM, aealexsandrov wrot

Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Hi Fvyaba, In order to avoid memory overhead per table, you should create all tables as part of the same cache group: https://apacheignite.readme.io/docs/cache-groups D. On Mon, Mar 26, 2018 at 7:26 AM, aealexsandrov wrote: > Hi Fvyaba, > > I investigated your example. In your code you are goi

Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Hi Fvyaba, I investigated your example. In your code you are going to create new cache every time when you are going to create new table. Every new cache will have some memory overhead. Next code can help you to get the average allocated memory: try (IgniteCache cache = ignite.getOrCr

Re: Re:Re: Re:Issue about ignite-sql limit of table quantity

Hi Fvyaba, I investigated your example. In your code you are going to create new cache every time when you are going to create new table. Every new cache will have some memory overhead. Next code can help you to get the average allocated memory: try (IgniteCache cache = ignite.getOrCr

Re:Re: Re:Issue about ignite-sql limit of table quantity

Hi Andrei: Thanks for your answer! My laptop run on MacOS(16G RAM),I just ran a simple test, it seems 'table creation' cost much much more memory&time than 'data creation',and we got 'IgniteOutOfMemoryException: Out of memory in data region [name=default, initSize=256.0 MiB, maxSize=3.2 GiB, per

Re: Re:Issue about ignite-sql limit of table quantity

Hi Fvyaba, There is no information about it in documentation but according several places in the code I see that it isn't greater than int32. void ReadTableMetaVector(ignite::impl::binary::BinaryReaderImpl& reader, TableMetaVector& meta) { int32_t metaNum =

Re:Issue about ignite-sql limit of table quantity

any help? At 2018-03-22 16:19:15, "fvyaba" wrote: Hi,I have a question about ignite-sql limit of table quantity: 1.We are design a system might have huge quantity of table,as we understand about ignite-sql table mechanism,all the tables could only be created within so-called '

Issue about ignite-sql limit of table quantity

Hi,I have a question about ignite-sql limit of table quantity: 1.We are design a system might have huge quantity of table,as we understand about ignite-sql table mechanism,all the tables could only be created within so-called 'PUBLIC' schema,which means all the meta-data of table are

Re: Feature request: Ignite SQL Rename table support

i just opened https://issues.apache.org/jira/browse/IGNITE-7051 -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Feature request: Ignite SQL Rename table support

This improvement makes sense, but I doubt there are any plans to implement it at the moment. Feel free to create a ticket in Jira. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Feature request: Ignite SQL Rename table support

Use case is discussed at length: http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-td2075.html#a17641 Currently, we have to load data to second table, the client then has to change their query to query this new table. Drop the old table. The latest suggestion in t

Re: Ignite SQL function questions

nt and going through Ignite source > code for a few while now. > > From the source code I see that Ignite can be a key/value store and the data > is stored in a ConcurrentHashMap for every partition. > So this is one copy of data in memory. > > For Ignite SQL function, it seems

Re: Ignite SQL function questions

Hi Ray, Ignite replaces H2 row object with its own stub. So, when you ask for a field value, ignite get entry represented by the row and get entry field according to configured mapping (via Queryentity [1] or via annotations [2]). Ignite stores data in serialized way, as every field can be accesse

Re: Ignite SQL function questions

So when I run a sql in h2 debug console, how does h2 get results from cache store? In other words, how does the key/value cache entry to h2 entry mapping work? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite SQL function questions

Hi, You will have only one copy of data, tables are needed for correct H2 work. When do some query, H2 builds a query plan that will be delegated to Ignite, which underneath gets data from cache. Thanks! -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite SQL function questions

I've been reading Ignite official document and going through Ignite source code for a few while now. >From the source code I see that Ignite can be a key/value store and the data is stored in a ConcurrentHashMap for every partition. So this is one copy of data in memory. For Ignite SQL

Ignite SQL function questions

I've been reading Ignite official document and going through Ignite source code for a few while now. From the source code, I see that Ignite can be a key/value store and the data is stored in a ConcurrentHashMap for every partition. So, this is one copy of data in memory. For Ignit

Re: Ignite sql queries working transactionally

first client commits and only > then it executes its delete query. > > Rollback functionality is also working on update/delete queries. So does it > mean that ignite now supports fully transactional sql queries? It was > mentioned in many previous ignite users posts that ignite sql que

Re: updating key object field using ignite sql query

ache > key. Now how to update the key fields of cache key using ignite sql queries. > When I try to update I am getting 'Failed to parse query' error. > > > For example my cache stores value in person [fields: id,name,phno] and key > in personpk [fields:id,phno] POJO c

  1   2   >