You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Yonik Seeley (JIRA)" <ji...@apache.org> on 2010/01/12 20:42:54 UTC
[jira] Created: (SOLR-1720) replication configuration bug with
multiple replicateAfter values
replication configuration bug with multiple replicateAfter values
-----------------------------------------------------------------
Key: SOLR-1720
URL: https://issues.apache.org/jira/browse/SOLR-1720
Project: Solr
Issue Type: Bug
Affects Versions: 1.4
Reporter: Yonik Seeley
Fix For: 1.5
Jason reported problems with Multiple replicateAfter values - it worked after changing to just "commit"
http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1720) replication configuration bug with
multiple replicateAfter values
Posted by "Shalin Shekhar Mangar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799600#action_12799600 ]
Shalin Shekhar Mangar commented on SOLR-1720:
---------------------------------------------
Yonik, replicateAfter is supposed to be specified multiple times with different values. A single replicateAfter with comma separated value is invalid. So it is by design, not a bug. We could change that if you want.
> replication configuration bug with multiple replicateAfter values
> -----------------------------------------------------------------
>
> Key: SOLR-1720
> URL: https://issues.apache.org/jira/browse/SOLR-1720
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Yonik Seeley
> Fix For: 1.5
>
>
> Jason reported problems with Multiple replicateAfter values - it worked after changing to just "commit"
> http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SOLR-1720) replication configuration bug with
multiple replicateAfter values
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yonik Seeley closed SOLR-1720.
------------------------------
Resolution: Invalid
> replication configuration bug with multiple replicateAfter values
> -----------------------------------------------------------------
>
> Key: SOLR-1720
> URL: https://issues.apache.org/jira/browse/SOLR-1720
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Yonik Seeley
> Fix For: 1.5
>
>
> Jason reported problems with Multiple replicateAfter values - it worked after changing to just "commit"
> http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1720) replication configuration bug with
multiple replicateAfter values
Posted by "Jason Rutherglen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799843#action_12799843 ]
Jason Rutherglen commented on SOLR-1720:
----------------------------------------
For consistency maybe we should support comma delimited lists? I edit the shards a lot (comma delimited), which could use different elements as well, so by rote, I just used commas for this, because it seemed like a Solr standard...
Thanks for clarifying!
> replication configuration bug with multiple replicateAfter values
> -----------------------------------------------------------------
>
> Key: SOLR-1720
> URL: https://issues.apache.org/jira/browse/SOLR-1720
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Yonik Seeley
> Fix For: 1.5
>
>
> Jason reported problems with Multiple replicateAfter values - it worked after changing to just "commit"
> http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SOLR-1720) replication configuration bug with
multiple replicateAfter values
Posted by "Yonik Seeley (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799800#action_12799800 ]
Yonik Seeley commented on SOLR-1720:
------------------------------------
Gah - totally missed that! I saw the syntax Jason used and just assumed it was supposed to work.
Let's just change the example on the wiki to include startup?
<str name="replicateAfter">commit</str>
<str name="replicateAfter">startup</str>
That will match the example schema and prevent any confusion over "multiple values".
> replication configuration bug with multiple replicateAfter values
> -----------------------------------------------------------------
>
> Key: SOLR-1720
> URL: https://issues.apache.org/jira/browse/SOLR-1720
> Project: Solr
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Yonik Seeley
> Fix For: 1.5
>
>
> Jason reported problems with Multiple replicateAfter values - it worked after changing to just "commit"
> http://www.lucidimagination.com/search/document/e4c9ba46dc03b031/replication_problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.