[jira] [Commented] (SOLR-3920) CloudSolrServer doesn't allow to index multiple collections with one instance of server
[ https://issues.apache.org/jira/browse/SOLR-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471597#comment-13471597 ] Mark Miller commented on SOLR-3920: --- You can set the default collection (a method on the CloudSolrServer) or set the collection per update call (collection param). > CloudSolrServer doesn't allow to index multiple collections with one instance > of server > --- > > Key: SOLR-3920 > URL: https://issues.apache.org/jira/browse/SOLR-3920 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Affects Versions: 4.0-BETA >Reporter: Grzegorz Sobczyk > > With one instance of CloudSolrServer I can't add documents to multiple > collections, for example: > {code} > CloudSolrServer server = new CloudSolrServer(zkHost); > UpdateRequest updateColl1 = new UpdateRequest(); > updateColl1.setAction(ACTION.COMMIT, true, true); > updateColl1.process(server); > UpdateRequest updateColl2 = new UpdateRequest(); > updateColl2.setAction(ACTION.COMMIT, true, true); > updateColl2.process(server); > {code} > Second update goes to first collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3920) CloudSolrServer doesn't allow to index multiple collections with one instance of server
[ https://issues.apache.org/jira/browse/SOLR-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471847#comment-13471847 ] Grzegorz Sobczyk commented on SOLR-3920: I'm sorry - pasted wrong example :( I wrote test and replaced previous code with it. > CloudSolrServer doesn't allow to index multiple collections with one instance > of server > --- > > Key: SOLR-3920 > URL: https://issues.apache.org/jira/browse/SOLR-3920 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Affects Versions: 4.0-BETA >Reporter: Grzegorz Sobczyk > > With one instance of CloudSolrServer I can't add documents to multiple > collections, for example: > {code} > @Test > public void shouldCommitToTwoCores() throws Exception { > //given > try { > CloudSolrServer server = new CloudSolrServer("localhost:9983"); > UpdateRequest commit1 = new UpdateRequest(); > commit1.setAction(ACTION.COMMIT, true, true); > commit1.setParam("collection", "collection1"); > //this commit is bug's cause > commit1.process(server); > > SolrInputDocument doc = new SolrInputDocument(); > doc.addField("id", "id"); > doc.addField("name", "name"); > > UpdateRequest update2 = new UpdateRequest(); > update2.setParam("collection", "collection2"); > update2.add(doc); > update2.process(server); > > UpdateRequest commit2 = new UpdateRequest(); > commit2.setAction(ACTION.COMMIT, true, true); > commit2.setParam("collection", "collection2"); > commit2.process(server); > SolrQuery q1 = new SolrQuery("id:id"); > q1.set("collection", "collection1"); > SolrQuery q2 = new SolrQuery("id:id"); > q2.set("collection", "collection2"); > > //when > QueryResponse resp1 = server.query(q1); > QueryResponse resp2 = server.query(q2); > > //then > Assert.assertEquals(0L, resp1.getResults().getNumFound()); > Assert.assertEquals(1L, resp2.getResults().getNumFound()); > } finally { > CloudSolrServer server1 = new CloudSolrServer("localhost:9983"); > server1.setDefaultCollection("collection1"); > server1.deleteByQuery("id:id"); > server1.commit(true, true); > > CloudSolrServer server2 = new CloudSolrServer("localhost:9983"); > server2.setDefaultCollection("collection2"); > server2.deleteByQuery("id:id"); > server2.commit(true, true); > } > } > {code} > Second update goes to first collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3920) CloudSolrServer doesn't allow to index multiple collections with one instance of server
[ https://issues.apache.org/jira/browse/SOLR-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471864#comment-13471864 ] Mark Miller commented on SOLR-3920: --- Hmm...I wonder if it's the caching that was put in... I'll try working your test into our unit tests. > CloudSolrServer doesn't allow to index multiple collections with one instance > of server > --- > > Key: SOLR-3920 > URL: https://issues.apache.org/jira/browse/SOLR-3920 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Affects Versions: 4.0-BETA >Reporter: Grzegorz Sobczyk > Fix For: 4.1, 5.0 > > > With one instance of CloudSolrServer I can't add documents to multiple > collections, for example: > {code} > @Test > public void shouldSendToSecondCore() throws Exception { > //given > try { > CloudSolrServer server = new CloudSolrServer("localhost:9983"); > UpdateRequest commit1 = new UpdateRequest(); > commit1.setAction(ACTION.COMMIT, true, true); > commit1.setParam("collection", "collection1"); > //this commit is bug's cause > commit1.process(server); > > SolrInputDocument doc = new SolrInputDocument(); > doc.addField("id", "id"); > doc.addField("name", "name"); > > UpdateRequest update2 = new UpdateRequest(); > update2.setParam("collection", "collection2"); > update2.add(doc); > update2.process(server); > > UpdateRequest commit2 = new UpdateRequest(); > commit2.setAction(ACTION.COMMIT, true, true); > commit2.setParam("collection", "collection2"); > commit2.process(server); > SolrQuery q1 = new SolrQuery("id:id"); > q1.set("collection", "collection1"); > SolrQuery q2 = new SolrQuery("id:id"); > q2.set("collection", "collection2"); > > //when > QueryResponse resp1 = server.query(q1); > QueryResponse resp2 = server.query(q2); > > //then > Assert.assertEquals(0L, resp1.getResults().getNumFound()); > Assert.assertEquals(1L, resp2.getResults().getNumFound()); > } finally { > CloudSolrServer server1 = new CloudSolrServer("localhost:9983"); > server1.setDefaultCollection("collection1"); > server1.deleteByQuery("id:id"); > server1.commit(true, true); > > CloudSolrServer server2 = new CloudSolrServer("localhost:9983"); > server2.setDefaultCollection("collection2"); > server2.deleteByQuery("id:id"); > server2.commit(true, true); > } > } > {code} > Second update goes to first collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3920) CloudSolrServer doesn't allow to index multiple collections with one instance of server
[ https://issues.apache.org/jira/browse/SOLR-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483783#comment-13483783 ] Mark Miller commented on SOLR-3920: --- I started hitting this rarely in a test while working on another issue - I added to the test so that it would catch a problem here. Fix coming soon. > CloudSolrServer doesn't allow to index multiple collections with one instance > of server > --- > > Key: SOLR-3920 > URL: https://issues.apache.org/jira/browse/SOLR-3920 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Affects Versions: 4.0-BETA >Reporter: Grzegorz Sobczyk >Assignee: Mark Miller > Fix For: 4.1, 5.0 > > > With one instance of CloudSolrServer I can't add documents to multiple > collections, for example: > {code} > @Test > public void shouldSendToSecondCore() throws Exception { > //given > try { > CloudSolrServer server = new CloudSolrServer("localhost:9983"); > UpdateRequest commit1 = new UpdateRequest(); > commit1.setAction(ACTION.COMMIT, true, true); > commit1.setParam("collection", "collection1"); > //this commit is bug's cause > commit1.process(server); > > SolrInputDocument doc = new SolrInputDocument(); > doc.addField("id", "id"); > doc.addField("name", "name"); > > UpdateRequest update2 = new UpdateRequest(); > update2.setParam("collection", "collection2"); > update2.add(doc); > update2.process(server); > > UpdateRequest commit2 = new UpdateRequest(); > commit2.setAction(ACTION.COMMIT, true, true); > commit2.setParam("collection", "collection2"); > commit2.process(server); > SolrQuery q1 = new SolrQuery("id:id"); > q1.set("collection", "collection1"); > SolrQuery q2 = new SolrQuery("id:id"); > q2.set("collection", "collection2"); > > //when > QueryResponse resp1 = server.query(q1); > QueryResponse resp2 = server.query(q2); > > //then > Assert.assertEquals(0L, resp1.getResults().getNumFound()); > Assert.assertEquals(1L, resp2.getResults().getNumFound()); > } finally { > CloudSolrServer server1 = new CloudSolrServer("localhost:9983"); > server1.setDefaultCollection("collection1"); > server1.deleteByQuery("id:id"); > server1.commit(true, true); > > CloudSolrServer server2 = new CloudSolrServer("localhost:9983"); > server2.setDefaultCollection("collection2"); > server2.deleteByQuery("id:id"); > server2.commit(true, true); > } > } > {code} > Second update goes to first collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-3920) CloudSolrServer doesn't allow to index multiple collections with one instance of server
[ https://issues.apache.org/jira/browse/SOLR-3920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484556#comment-13484556 ] Mark Miller commented on SOLR-3920: --- Yeah, the caching is whack if you change up the collection list. I've got a test and fix. > CloudSolrServer doesn't allow to index multiple collections with one instance > of server > --- > > Key: SOLR-3920 > URL: https://issues.apache.org/jira/browse/SOLR-3920 > Project: Solr > Issue Type: Bug > Components: SolrCloud >Affects Versions: 4.0-BETA >Reporter: Grzegorz Sobczyk >Assignee: Mark Miller > Labels: 4.0.1_Candidate > Fix For: 4.1, 5.0 > > > With one instance of CloudSolrServer I can't add documents to multiple > collections, for example: > {code} > @Test > public void shouldSendToSecondCore() throws Exception { > //given > try { > CloudSolrServer server = new CloudSolrServer("localhost:9983"); > UpdateRequest commit1 = new UpdateRequest(); > commit1.setAction(ACTION.COMMIT, true, true); > commit1.setParam("collection", "collection1"); > //this commit is bug's cause > commit1.process(server); > > SolrInputDocument doc = new SolrInputDocument(); > doc.addField("id", "id"); > doc.addField("name", "name"); > > UpdateRequest update2 = new UpdateRequest(); > update2.setParam("collection", "collection2"); > update2.add(doc); > update2.process(server); > > UpdateRequest commit2 = new UpdateRequest(); > commit2.setAction(ACTION.COMMIT, true, true); > commit2.setParam("collection", "collection2"); > commit2.process(server); > SolrQuery q1 = new SolrQuery("id:id"); > q1.set("collection", "collection1"); > SolrQuery q2 = new SolrQuery("id:id"); > q2.set("collection", "collection2"); > > //when > QueryResponse resp1 = server.query(q1); > QueryResponse resp2 = server.query(q2); > > //then > Assert.assertEquals(0L, resp1.getResults().getNumFound()); > Assert.assertEquals(1L, resp2.getResults().getNumFound()); > } finally { > CloudSolrServer server1 = new CloudSolrServer("localhost:9983"); > server1.setDefaultCollection("collection1"); > server1.deleteByQuery("id:id"); > server1.commit(true, true); > > CloudSolrServer server2 = new CloudSolrServer("localhost:9983"); > server2.setDefaultCollection("collection2"); > server2.deleteByQuery("id:id"); > server2.commit(true, true); > } > } > {code} > Second update goes to first collection. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org