On Wed, May 18, 2011 at 12:58 PM, Grant Ingersoll <[email protected]>wrote:
> > Actually, I think it is core at this point, since we moved the > Vectorization stuff to core. Unfortunately, we need Lucene core in order to > get the baseline definitions of TokenStreams for Vectorization. > Scratch that, yeah it's reasonably embedded. > > Agreed. I'm open to the move, just wanted to hear more about what it would > look like. I think it makes sense that all DataModel implementations move > along with it, other than the base classes, as a MySQLJDBCDataModel is in > the same class of things as a Mongo one (or Cassandra or HBase, etc.) > I don't think most implementations should move, no. Most are "core" to the project. Ones based on backing stores used by some but not many users are not core. I'd like to reiterate I don't think this is specific to collaborative filtering at all. Right? > > Likewise, we could do the same with our classification storage > implementations. (In fact, I wonder if there is duplication going on between > the Taste DataModel and the Classifier ones, at least a very low level) > I strongly doubt it, the DataModel implementations are pretty specific to recommenders for performance. Generalizing them breaks that quickly.
