You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by blackfield <ch...@maxpoint.com> on 2017/10/19 20:48:23 UTC
Re: Continuous update Data Grid Cache
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-users.70518.x6.nabble.com/
Re: Continuous update Data Grid Cache
Posted by Denis Magda <dm...@apache.org>.
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 <ch...@maxpoint.com> wrote:
>
>
> 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.
>
> We are looking for ways to minimize the impact, e.g. load the data to
> another table->perform swap, etc.
>
> Let me know if there are existing capabilities to minimize the above
> scenario.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Continuous update Data Grid Cache
Posted by blackfield <ch...@maxpoint.com>.
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.
We are looking for ways to minimize the impact, e.g. load the data to
another table->perform swap, etc.
Let me know if there are existing capabilities to minimize the above
scenario.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Re: Continuous update Data Grid Cache
Posted by Denis Magda <dm...@apache.org>.
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 <ch...@maxpoint.com> wrote:
>
> 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-users.70518.x6.nabble.com/