Dear Courtney Robinson,
please write if you have any cases to update helper cache with paritions to
better understand the situation.
How and when are you going to clear this helper caches if the alternative
version (as you suggested in the first email) of CacheBased Dataset will be
provided?
Courtney,
The CacheBasedDataset.close() method below only destroys the helper cache
derived from
the original data, and used to train the model. It does not touch the
original data set.
@Override public void close() {
datasetCache.destroy(); // destroy the helper cache derived from the
Hey,
Just seen this reply.
We have Ignite persistence enabled. The caches/tables are the primary
source of the data. That's the use case.
If we build an ML model from the data in a cache, Ignite's behaviour of
deleting the cache means we'll have lost that data.
We were just lucky this showed up in
Dear Courtney Robinson, let's discuss here the possible behaviour of this
CacheBased Dataset closing.
When designed this feature we think, that the all training parts and stuff
should be deleted from Caches ad model should be serialized or exported
somwhere.
What is your use-case& Could you
Hi,
This is the way CacheBasedDataset has been designed.
It has been made w/an eye toward training the implemented ML models:
https://apacheignite.readme.io/docs/model-updating
You are free to create an implementation to fit your needs.
Use these examples to test your design:
Hi all,
The current CacheBasedDataSet destroys the cache and all data along with
it...there is no option to turn this off either.
https://github.com/apache/ignite/blob/master/modules/ml/src/main/java/org/apache/ignite/ml/dataset/impl/cache/CacheBasedDataset.java#L189
/** {@inheritDoc} */
