[jira] [Reopened] (SOLR-7914) Improve bulk doc update
[ https://issues.apache.org/jira/browse/SOLR-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwan-I Lee reopened SOLR-7914: -- Improve bulk doc update --- Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor Fix For: 4.10.5 Attachments: SOLR-7914.patch One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Resolved] (SOLR-7914) Improve bulk doc update
[ https://issues.apache.org/jira/browse/SOLR-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwan-I Lee resolved SOLR-7914. -- Resolution: Fixed Fix Version/s: 4.10.5 Improve bulk doc update --- Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor Fix For: 4.10.5 Attachments: SOLR-7914.patch One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Updated] (SOLR-7914) Improve bulk doc update
[ https://issues.apache.org/jira/browse/SOLR-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwan-I Lee updated SOLR-7914: - Attachment: SOLR-7914.patch Improve bulk doc update --- Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor Attachments: SOLR-7914.patch One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-7914) Improve bulk doc update
[ https://issues.apache.org/jira/browse/SOLR-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693343#comment-14693343 ] Kwan-I Lee commented on SOLR-7914: -- Will do. Thanks, Jan. Improve bulk doc update --- Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor Fix For: 4.10.5 Attachments: SOLR-7914.patch One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Closed] (SOLR-7914) Improve bulk doc update
[ https://issues.apache.org/jira/browse/SOLR-7914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kwan-I Lee closed SOLR-7914. Resolution: Duplicate Improve bulk doc update --- Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor Fix For: 4.10.5 Attachments: SOLR-7914.patch One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Created] (SOLR-7914) Improve bulk doc update
Kwan-I Lee created SOLR-7914: Summary: Improve bulk doc update Key: SOLR-7914 URL: https://issues.apache.org/jira/browse/SOLR-7914 Project: Solr Issue Type: Improvement Reporter: Kwan-I Lee Priority: Minor One limitation of Solr index update is: given a doc update batch, if one doc fails, Solr aborts the full batch operation, without specifying the problematic doc. This task aims to improve solr handling logic. E.g. The batch update should proceed, only skipping the problematic doc(s), and report those problematic doc ids in response. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6266) Couchbase plug-in for Solr
[ https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14175485#comment-14175485 ] Kwan-I Lee commented on SOLR-6266: -- Karol, Thanks for the reply. I also tried automatic XDCR configuration in Couchbase server by using the APIs they provide. The problem I encountered is they don't have API to switch XDCR protocol (at least I didn't find it on their website.) By default the protocol is set to version 2 upon creation, while we need version 1 to make the plugin work. I'll try to talk with Couchbase people to see if there's any way to make it. Kwan Couchbase plug-in for Solr -- Key: SOLR-6266 URL: https://issues.apache.org/jira/browse/SOLR-6266 Project: Solr Issue Type: New Feature Reporter: Varun Assignee: Joel Bernstein Attachments: solr-couchbase-plugin-0.0.3-SNAPSHOT.tar.gz, solr-couchbase-plugin-0.0.5-SNAPSHOT.tar.gz, solr-couchbase-plugin-0.0.5.1-SNAPSHOT.tar.gz, solr-couchbase-plugin.tar.gz, solr-couchbase-plugin.tar.gz It would be great if users could connect Couchbase and Solr so that updates to Couchbase can automatically flow to Solr. Couchbase provides some very nice API's which allow applications to mimic the behavior of a Couchbase server so that it can receive updates via Couchbase's normal cross data center replication (XDCR). One possible design for this is to create a CouchbaseLoader that extends ContentStreamLoader. This new loader would embed the couchbase api's that listen for incoming updates from couchbase, then marshal the couchbase updates into the normal Solr update process. Instead of marshaling couchbase updates into the normal Solr update process, we could also embed a SolrJ client to relay the request through the http interfaces. This may be necessary if we have to handle mapping couchbase buckets to Solr collections on the Solr side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-6266) Couchbase plug-in for Solr
[ https://issues.apache.org/jira/browse/SOLR-6266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14173588#comment-14173588 ] Kwan-I Lee commented on SOLR-6266: -- Karol, Andrzej, I'm interested in how this plugin handles different replication failure scenarios. Here is one of my tests: 1. Add some documents in Couchbase. 2. Activate this plugin, creating remote cluster and replication in Couchbase. - Data successfully pushed to Solr through XDCR. The Couchbase documents are now visible in Solr. 3. Stop Solr instance. Add a document, doc1, in Couchbase. 4. Restart Solr instance and activate plugin. With Elasticsearch-Couchbase plugin, doc1 will be pushed to Elasticsearch node once the machine is back. However with this plugin, the replication of doc1 will fail and never go to Solr instance. I spent some time debugging and tracing both Elasticsearch and Solr plugin code. For Elasticsearch one, couchbase.capi.servlet.ClusterMapServlet.doGet() will eventually get correct pool from req.getPathInfo(). However for Solr one, req.getPathInfo() keeps getting null value for pool no matter how many times Couchbase sends doc1 update request to Solr plugin. I'm testing it on Mac, so not sure if it happens in other systems. Couchbase plug-in for Solr -- Key: SOLR-6266 URL: https://issues.apache.org/jira/browse/SOLR-6266 Project: Solr Issue Type: New Feature Reporter: Varun Assignee: Joel Bernstein Attachments: solr-couchbase-plugin-0.0.3-SNAPSHOT.tar.gz, solr-couchbase-plugin-0.0.5-SNAPSHOT.tar.gz, solr-couchbase-plugin.tar.gz, solr-couchbase-plugin.tar.gz It would be great if users could connect Couchbase and Solr so that updates to Couchbase can automatically flow to Solr. Couchbase provides some very nice API's which allow applications to mimic the behavior of a Couchbase server so that it can receive updates via Couchbase's normal cross data center replication (XDCR). One possible design for this is to create a CouchbaseLoader that extends ContentStreamLoader. This new loader would embed the couchbase api's that listen for incoming updates from couchbase, then marshal the couchbase updates into the normal Solr update process. Instead of marshaling couchbase updates into the normal Solr update process, we could also embed a SolrJ client to relay the request through the http interfaces. This may be necessary if we have to handle mapping couchbase buckets to Solr collections on the Solr side. -- This message was sent by Atlassian JIRA (v6.3.4#6332) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
