Hi Weixi, You might have to try describing your use case in more detail. Solr Indices are independent from Riak objects. They are, instead, associated with riak buckets (or bucket types), and an object (key/value) can only be associated with one bucket. Therefore, a Riak object can only be associated with one Solr index. A Solr index can be associated with multiple buckets, but in general the mapping from Riak objects to Solr indices is injective.
Is it possible that you changed the index associated with a bucket at some point in the bucket or bucket type lifecycle? -Fred > On Sep 10, 2016, at 9:27 PM, Weixi Yen <we...@blitzchat.com> wrote: > > Sort of a unique case, my app was under heavy stress and one of my riak nodes > got backed up (other 4 nodes were fine). > > I think this caused Riak.update to create an extra index in Solr for the same > object when users began running .update on that object. > > I have basically 2 questions: > > 1) Is what I'm describing something that is possible? > > 2) Is there a way to tell Solr to re-index one single item and get rid of all > other indexes of that item? > > Considering RiakTS to resolve these issues long term, but have to stick with > Solr for at least the next 3 months, would appreciate any insight into how to > solve this duplicate index problem. > > Thanks, > > Weixi > > _______________________________________________ > riak-users mailing list > riak-users@lists.basho.com > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
