I am also trying with something like - java -Durl=http://domainname.com:1981/solr/web/update-Dtype=application/json -jar /solr4RA/example1/exampledocs/post.jar /root/Desktop/web/*.json
but it is giving error - 19:06:22 ERROR SolrCore org.apache.solr.common.SolrException: Unknown command: subDomain [12] org.apache.solr.common.SolrException: Unknown command: subDomain [12] at org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.processUpdate(JsonLoader.java:152) at org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.load(JsonLoader.java:101) at org.apache.solr.handler.loader.JsonLoader.load(JsonLoader.java:65) at org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:92) at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74) at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135) at org.apache.solr.core.SolrCore.execute(SolrCore.java:1859) at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:703) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:406) at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:195) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1419) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1075) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:384) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1009) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:368) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.BlockingHttpConnection.handleRequest(BlockingHttpConnection.java:53) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:953) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1014) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:861) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.BlockingHttpConnection.handle(BlockingHttpConnection.java:72) at org.eclipse.jetty.server.bio.SocketConnector$ConnectorEndPoint.run(SocketConnector.java:264) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543) at java.lang.Thread.run(Thread.java:722) On Thu, Oct 17, 2013 at 6:31 PM, Chris <christu...@gmail.com> wrote: > Wow thanks for all that, i just upgraded, linked my plugins & it seems > fine so far, but i have run into another issue.... > > while adding a document to the solr cloud it says - > org.apache.solr.common.SolrException: Unknown document router > '{name=compositeId}' > > in the clusterstate.json i can see - > > "shard5":{ > "range":"4ccc0000-7fffffff", > "state":"active", > "replicas":{"core_node4":{ > "state":"active", > "base_url":"http://64.251.14.47:1984/solr", > "core":"web_shard5_replica1", > "node_name":"64.251.14.47:1984_solr", > "leader":"true"}}}}, > "maxShardsPerNode":"2", > "router":{"name":"compositeId"}, > "replicationFactor":"1"}, > > I am using this to add - > > > CloudSolrServer solrCoreCloud = new > CloudSolrServer(cloudURL); > > solrCoreCloud.setDefaultCollection("web"); > > UpdateResponse up = solrCoreCloud.addBean(resultItem); > UpdateResponse upr = solrCoreCloud.commit(); > > Please advice. > > > > > > On Wed, Oct 16, 2013 at 9:49 PM, Shawn Heisey <s...@elyograg.org> wrote: > >> On 10/16/2013 4:51 AM, Chris wrote: >> > Also, is there any easy way upgrading to 4.5 without having to change >> most >> > of my plugins & configuration files? >> >> Upgrading is something that should be done carefully. If you can, it's >> always recommended that you try it out on dev hardware with your real >> index data beforehand, so you can deal with any problems that arise >> without causing problems for your production cluster. Upgrading >> SolrCloud is particularly tricky, because for a while you will be >> running different versions on different machines in your cluster. >> >> If you're using your own custom software to go with Solr, or you're >> using third-party plugins that aren't included in the Solr download, >> upgrading might take more effort than usual. Also, if you are doing >> anything in your config/schema that changes the format of the Lucene >> index, you may find that it can't be upgraded without completely >> rebuilding the index. Examples of this are changing the postings format >> or docValues format. This is a very nasty complication with SolrCloud, >> because those configurations affect the entire cluster. In that case, >> the whole index may need to be rebuilt without custom formats before >> upgrading is attempted. >> >> If you don't have any of the complications mentioned in the preceding >> paragraph, upgrading is usually a very simple process: >> >> *) Shut down Solr. >> *) Delete the extracted WAR file directory. >> *) Replace solr.war with the new war from dist/ in the download. >> **) Usually it must actually be named solr.war, which means renaming it. >> *) Delete and replace other jars copied from the download. >> *) Change luceneMatchVersion in all solrconfig.xml files. ** >> *) Start Solr back up. >> >> ** With SolrCloud, you can't actually change the luceneMatchVersion >> until all of your servers have been upgraded. >> >> A full reindex is strongly recommended. With SolrCloud, it normally >> needs to wait until all servers are upgraded. In situations where it >> won't work at all without a reindex, upgrading SolrCloud can be very >> challenging. >> >> It's strongly recommended that you look over CHANGES.txt and compare the >> new example config/schema with the example from the old version, to see >> if there are any changes that you might want to incorporate into your >> own config. As with luceneMatchVersion, if you're running SolrCloud, >> those changes might need to wait until you're fully upgraded. >> >> Side note: When upgrading to a new minor version, config changes aren't >> normally required. They will usually be required when upgrading major >> versions, such as 3.x to 4.x. >> >> If you *do* have custom plugins that aren't included in the Solr >> download, you may have to recompile them for the new version, or wait >> for the vendor to create a new version before you upgrade. >> >> This is only the tip of the iceberg, but a lot of the rest of it depends >> greatly on your configurations. >> >> Thanks, >> Shawn >> >> >