Computation in-memory is much faster than in-database. But recommender_similary_classical() only supports in-memory computation when missing data is treated as zero. In-memory computation is needed for cases where missing data is treated as 'none' or 'adjusted' like the in-database operation.

This is a low priority code task because the full functionality is already implemented in in-database approach. The in-memory feature is just an optional feature rather than a necessary one.

Comments

danithaca’s picture

Version: » 6.x-1.1
Priority: Minor » Normal
Status: Postponed » Active

will work on it soon in the OO paradim.

danithaca’s picture

Version: 6.x-1.1 » 6.x-2.x-dev
Status: Active » Fixed

not implemented for the 'adjusted' though

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.