Yes, that is correct. Collection 'features' stores mapping between features and their scores. For simplicity, I tried to keep the level of detail about these collections to a minimum.
Both collections contain thousands of records and are updated by (lily) hbase-indexer. Therefore storing scores/weights in the model resource is not feasible. Ideally, I would like to keep these data collection separate and perform cross-collection queries. If such an approach is not feasible, then I could possibly merge the two collections into one. This would make matters simpler but not ideal. Gintas On Tue, Jan 30, 2018 at 5:49 PM, Alessandro Benedetti <a.benede...@sease.io> wrote: > Accordingly to what I understood the feature weight is present in your > second > collection. > You should express the feature weight in the model resource ( not even in > the original collection) > Is actually necessary for the feature weight to be in a separate Solr > collection ? > > > > ----- > --------------- > Alessandro Benedetti > Search Consultant, R&D Software Engineer, Director > Sease Ltd. - www.sease.io > -- > Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html >
