Hello!
Why adding a new cache an issue for you? You can add new caches dynamically
in runtime, you know.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
or can I log a feature ticket?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
is there any timeline to release such limit? I have use ignite in production
in my sub-system. it works so far so good, the only one exception is that
every time I add new table I have to define a new cache. I think it's ok
when the system is small. In fact I would like to use ignite in my another
>then we can use `cache group` to share some backend data struct to gain
some
level performance.
It will reduce the overhead for each cache since they will share the same
data structures under the hood.
>Are there any potential issues or potential consideration need to be
takecare of?
Caches in
Thank you reply very much!
If I keep all the caches for my system are created via sql, then all the
backend h2 tables are in public schema.
in this case even all the caches are in the same schema but there are
different cache (one cache per table but all in the same schema)
then we can use
cache and schema is a different things in Ignite. By default, when you
create table with SQL, it will be created in separate cache.
Evgenii
пн, 12 нояб. 2018 г. в 20:00, kcheng.mvp :
> based on my knowledge about ignite, there is a corresponding database
> `schema` for each `cache` in ignite
based on my knowledge about ignite, there is a corresponding database
`schema` for each `cache` in ignite (cache name)
in real case there are always more than one tables in a database `schema`.
that's why I keep more than one tables in a single ignite `cache`
if use one table per cache,
>can you tell me why there is a such limit that new created table via sql
can
not be in the non-public schema?
It is a current restriction, that will be fixed in the future.
>as it's hard to forecast how many tables should be in a caches. If there is
a such limit, then what's the best practice
Thank you very much!
can you tell me why there is a such limit that new created table via sql can
not be in the non-public schema?
I am using ignite with persistent, each `module` in my system is using a
cache, which there are some tables generated via `cfg.setIndexedTypes`
right now for
Hi,
If you want to use pre-defined cache, that already exists in the cluster
for Creating new SQL Tables, it should have configured Public
CacheConfiguration.sqlSchema:
Evgenii
пт, 9 нояб. 2018 г. в 12:53, kcheng.mvp :
> my cache is created via (cache name is 'abc')
>
10 matches
Mail list logo
