I'm positive that you should define the same URL that you use to write to Solr. I have noted that our current documentation on curator component [0] [1] falls somewhat short of explaining this in detail though. It is missing Solr implementation and is overly complex.
[0] http://oodt.apache.org/components/maven/curator/user/basic.html [1] https://cwiki.apache.org/confluence/display/OODT/Using+CAS+Curator On Jun 16, 2014 8:59 PM, "Mike Vogel" <[email protected]> wrote: > 1. Only the built in product fields, listed below, are displayed > in the curator UI. I believe that previously the actual metadata was > displayed but I can’t determine what I changed to cause this to happen. > Arghh. I know the feeling. 2. If I edit these fields they changes are not saved. > You mean if you edit them in curator? No exceptions that I can find in the curator log or the file manager log. > When I step through the code with the debugger I don’t see the metadata > fields coming back from the call to the filemanager in > MetadataResource.getCatalogMetadata. I just see the product level fields > listed above. When I make the same call that the XmlRpcFileManager makes > to SolrCatalog.getMetadata in a standalone junit test the full metadata > fields are returned. > Mmmm.... this is strange indeed.
