You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When migrating worker-side data in LDA app, we have a problem that model is damaged during migration. It's because some of our apps have also partial models in the input table.
However, ET/EM assumes that worker-side table has only immutable input data. As a result, we design them not to care about worker-side table data consistency.
To resolve this problem, we need to provide a consistency mechanism for worker-side tables.
Or we may change LDA app to not to use local cache or cope with damage in local model.
The text was updated successfully, but these errors were encountered:
When migrating worker-side data in LDA app, we have a problem that model is damaged during migration. It's because some of our apps have also partial models in the input table.
However, ET/EM assumes that worker-side table has only immutable input data. As a result, we design them not to care about worker-side table data consistency.
To resolve this problem, we need to provide a consistency mechanism for worker-side tables.
Or we may change LDA app to not to use local cache or cope with damage in local model.
The text was updated successfully, but these errors were encountered: