Hi,
To avoid any downtime here I would recommend to load the new data set in the
same cache and remove the old entries from there once the preloading is
finished. This approach assumes that both old and new entries can co-exist in
the cache.
—
Denis
> On Oct 23, 2017, at 7:13 AM, blackfield
The use case is similar to OP.
We have a large table that we import/load from a dataset.
This dataset is generated periodically such that we need to re-load this
whole dataset to Ignite.
If we re-load the new dataset against the same Ignite table, the users will
be impacted during that window.
Why do you need cache aliases? Ignite evolved tremendously since the time of
this discussion. Most likely your task is solvable with already existing
capabilities.
—
Denis
> On Oct 19, 2017, at 1:48 PM, blackfield wrote:
>
> Resurrecting this old thread.
>
> What is the current recommendatio
Resurrecting this old thread.
What is the current recommendation for the OP use case?
Does Ignite support/plan to support aliases for cache name?
I think this is really great feature to have to minimize client
interruption/pain to switch to different cache.
--
Sent from: http://apache-ignite-
message in context:
http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-tp2075p2186.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
f I
> correctly understood your proposal, it will not work. I think you should go
> with the solution suggested by Denis.
>
> -Val
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-tp2075p21
ld go
with the solution suggested by Denis.
-Val
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Continuous-update-Data-Grid-Cache-tp2075p2120.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
What I mean by isolation is that they do not try to automatically discover each
other. They only form a cluster manually when triggered.
> Am 01.12.2015 um 13:58 schrieb Denis Magda :
>
> fsapei,
>
> What do you mean under isolation between two different caches?
> All the caches live they own
fsapei,
What do you mean under isolation between two different caches?
All the caches live they own life and don't affect each other.
--
Denis
On 12/1/2015 12:08 PM, Ferry Syafei Sapei wrote:
Thank you for your idea. Your solution should work.
May it be possible to perform the following opera
Thank you for your idea. Your solution should work.
May it be possible to perform the following operation?
- Create a new cache and isolate it from being replicated with the old cache.
- Populate data on new cache
- Shutdown old cache and remove the new cache isolation.
fsapei
> Am 30.11.2015 u
Fsapei,
Ignite neither supports a cache renaming nor has a notion of aliases for
caches.
In general you can support aliases-like functionality by extending
Ignite's JDBC Driver implementation.
The flow should look like this:
- create a new cache and populate it;
- redirect all the queries to
Hi Denis,
Using a database, we can import new data to new tables and then rename the
table.
In ElasticSearch, there is an alias. The client executes queries against index
alias. On the background, the alias will point to the actual index. In my use
case, I just need to create a new index and t
Hi Fsapei,
I don't think that it's feasible or at least easy to implement your
approach without a downtime or changing cache name in queries once the
second cache is fully propagated.
How would you implement your use case if instead of an Ignite cache you
would be using a data base?
--
Denis
Thank you for the reply.
The client uses JDBC Driver to get the data from Ignite.
The swap between new cache and old cache should be hidden from the client.
Would it be possible to do this in Ignite?
My first idea is to create a new cache and fill it with new data data.
Afterwards, within a
Hi Fsapei,
Ignite supports dynamic caches, so you can create and destroy caches on the
fly:
https://apacheignite.readme.io/docs/data-grid#section-jcache
To support your use case, you can:
1. create a new cache and start populating it
2. while the new cache is populated, the queries should go to
Hallo,
I would like to use Ignite as Data Grid. The cache will be initially loaded
with a lot of data (e.g. a CSV file with a size more than 10 GB).
When a new CSV file is available, the current Cache content must be replaced
with the new data from the new CSV. The old cache content must be com
16 matches
Mail list logo
