Hello Vincent and Michael, Thank you for the question and answer here.
I have added an 'Applying changes' section to https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank and changed https://cwiki.apache.org/confluence/display/solr/Managed+Resources to cross-reference to the reload API pages. Regards, Christine ----- Original Message ----- From: solr-user@lucene.apache.org To: solr-user@lucene.apache.org At: 03/08/17 15:23:20 Hey Vincent, The feature store and model store are both Solr Managed Resources. To propagate managed resources in distributed mode, including managed stopwords and synonyms, you have to issue a collection reload command. The Solr reference guide of Managed Resources has a bit more on it in the Applying Changes section. https://cwiki.apache.org/confluence/display/solr/Managed+Resources https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-RELOAD:ReloadaCollection The Managed Resource page and LTR page should be updated to be more explicit about it. Hope that helps, Michael On Wed, Mar 8, 2017 at 5:01 AM, Vincent <vincent.s...@openindex.io> wrote: > Hi all, > > It seems that the curl commands from the LTR wiki ( > https://cwiki.apache.org/confluence/display/solr/Learning+To+Rank) to > post and/or delete features from and to the feature store only affect one > shard instead of the entire collection. For example, when I run: > > |curl -XDELETE 'http://localhost:8983/solr/[C > OLLECTION]/schema/feature-store/currentFeatureStore' < > http://localhost:8983/solr/techproducts/schema/feature-stor > e/currentFeatureStore%27>| > > the feature store still exists on one of my two shards. Same goes for the > python HTTPConnection.request-function ("POST" and "DELETE"). > > Is this a mistake on my end? I assume it's not supposed to work this way? > > Thanks a lot! > Vincent >
