[ 
https://issues.apache.org/jira/browse/SOLR-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13251909#comment-13251909
 ] 

Jan Høydahl commented on SOLR-3347:
-----------------------------------

Cool, Steven, it worked well with -p1. I updated 
http://wiki.apache.org/solr/HowToContribute with this info.
                
> deleteByQuery failing with SolrCloud without _version_ in schema.xml
> --------------------------------------------------------------------
>
>                 Key: SOLR-3347
>                 URL: https://issues.apache.org/jira/browse/SOLR-3347
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>            Reporter: Benson Margulies
>             Fix For: 4.0
>
>         Attachments: 
> 0001-Attempt-to-repro-problem-with-del-and-SolrCloud.patch, 
> provision-and-start.sh, schema.xml, solrconfig.xml
>
>
> Distributed execution of deleteByQuery("\*:\*") depends on the existence of a 
> field \_version\_ in the schema. The default schema has no comment on this 
> field to indicate its important or relevance to SolrCloud, and no message is 
> logged nor error status returned when there is no such field. The code in 
> DistributedUpdateProcessor just has an if statement that never ever does any 
> local deleting without it.
> I don't know whether the intention was that this should work or not. If 
> someone would clue me in, I'd make a patch for schema.xml to add comments, or 
> a patch to D-U-P to add logging. If it was supposed to work, I'm probably not 
> qualified to make the fix to make it work.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to