hi, I have an opinion mining application running solr that serves to retrieve documents and perform some analytics using facet queries. It works great. But I have a big issue. The document has an attribute for opinion that is automatically detected, but users can change it if it´s not correct.
A document may be shared by some users and each user can change the opinion of the document. And the opinion may be different for each user. Opinion value is crucial here because its the main facet field on the analytic view. The thing is that solr does not handle doc updates, right now I need to delete it first and recreate the whole doc index to change it with the new metadata. And of course this is not fast enough. So I´m probably doing this the wrong way. Seams to me that is not a good approach and I should not update the index this way. The index should be more static, otherwise I will be reindexing the whole index to often. I´m running solr with a master/slave topology (2 slaves replication). The master to write and the slaves to read. Solr index is feed by a PostgresSQL database. I was wondering about using a nosql keyvalue database to store this kind of metadata and keep the index untouchable. So this way I could keep the index intact and store the user´s custom data there. It would fit if this value was not used by facet queries. That´s the problem. So my question is, what would be the best approach to handle this kind of use case with solr? If is not a usual use case, consider for example favorite docs. Favorites docs is probably a common use case in information retrieval. How do you handle for example favorite docs between users? I´d be very interested to hear about the best approach here. best Arian
