Hi Denis,
Thank you for the information.
Regards,
Shravya.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi Shravya,
The best practice is to have a cache (and SQL table) per a business entity of
your applications. So, my suggestion is not to mix different business entities
in a single cache. Create your data schema as you would do for a relational
database.
The CREATE TABLE creates a new Ignite c
Hi Andrey,
This information will definitely be useful. Thank you.
Regards,
Shravya Nethula.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hi
Seems, you are looking for CacheGroup [1].
You can use same cache group for number of caches [2] via setting
additional parameter in 'Create table' query.
[1] https://apacheignite.readme.io/docs/cache-groups
[2] https://apacheignite-sql.readme.io/docs/create-table
On Tue, Jan 16, 2018 at 9:43
Hi Andrey,
Thank you for the information.
I want to create some tables using cache.query(Create Table ...) statement.
Is there any way in which I can group some of my tables in one cache? Is
there any hierarchy in organizing the caches like a super cache holding some
sub caches?
Regards,
Shravy
Hi Shravya,
This is because of Ignite API allows to run query with having some cache
instance.
We are going to deprecate with API and implement SQL API on higher level to
avoid dummy cache creation,
but anyway old API can't be dropped until next major (3.0) version due to
compatibility requireme