[jira] Updated: (SOLR-1120) Simplify EntityProcessor API

[ https://issues.apache.org/jira/browse/SOLR-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-1120: - Attachment: SOLR-1120.patch futher simplifying DocBuilder Simplify EntityProcessor API

[jira] Commented: (SOLR-236) Field collapsing

[ https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12701862#action_12701862 ] Domingo Gómez García commented on SOLR-236: --- I made checkout on svn release-1.3.0

Partial results if a shard crash

Hi and greetings, this is my first post on that mailing list :) I'd like to add that functionnality. Right now, if i'm correct, when a shard crash (let's say I'm running 2 SOLR on a different port, and i'm shutting down one, but not the one I send the request to), everything stop. So, i'd

Re: lucene 2.9 migration issues -- MultiReader vs IndexReader document ids

Ok, not totally resolved Things work fine when I have my custom Filter alone or with other Filters, however if I add a query string to the mix it breaks with an IllegalStateException: java.lang.IllegalStateException: Auto should be resolved before now at

[jira] Updated: (SOLR-940) TrieRange support

[ https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uwe Schindler updated SOLR-940: --- Attachment: SOLR-940-LUCENE-1602.patch I modified the patch a little bit to also include an updated

Re: lucene 2.9 migration issues -- MultiReader vs IndexReader document ids

Looks like its my fault. Auto resolution was moved upto IndexSearcher in Lucene, and it looks like SolrIndexSearcher is not tickling it first. I'll take a look. - Mark Ryan McKinley wrote: Ok, not totally resolved Things work fine when I have my custom Filter alone or with other

Re: lucene 2.9 migration issues -- MultiReader vs IndexReader document ids

thanks! On Apr 23, 2009, at 6:32 PM, Mark Miller wrote: Looks like its my fault. Auto resolution was moved upto IndexSearcher in Lucene, and it looks like SolrIndexSearcher is not tickling it first. I'll take a look. - Mark Ryan McKinley wrote: Ok, not totally resolved Things work

[jira] Commented: (SOLR-1088) newSearcher(String name, boolean readOnly) is broken

[ https://issues.apache.org/jira/browse/SOLR-1088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702171#action_12702171 ] Mark Miller commented on SOLR-1088: --- I think I added that method with the readonly patch -

[jira] Commented: (SOLR-465) Add configurable DirectoryProvider so that alternate Directory implementations can be specified via solrconfig.xml

[ https://issues.apache.org/jira/browse/SOLR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12702173#action_12702173 ] Mark Miller commented on SOLR-465: -- Bah, those constructors came in after this patch - they

[jira] Updated: (SOLR-1126) replicated index files have incorrect timestamp

[ https://issues.apache.org/jira/browse/SOLR-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Noble Paul updated SOLR-1126: - Attachment: SOLR-1126.patch the fix replicated index files have incorrect timestamp

[jira] Created: (SOLR-1126) replicated index files have incorrect timestamp

replicated index files have incorrect timestamp --- Key: SOLR-1126 URL: https://issues.apache.org/jira/browse/SOLR-1126 Project: Solr Issue Type: Bug Components: replication (java)