small bug in solrj? resultquery.addFacetField overwrites resultquery.setFacetMinCount to 1.

Hi, when constructing a resultquery using SOlrJ the method addFacetField overwrites the value set with setFacetMinCount to 1. Is this intentional or a small bug? Cheers, Geert-Jan -- View this message in context:

Re: small bug in solrj? resultquery.addFacetField overwrites resultquery.setFacetMinCount to 1.

Britske wrote: Hi, when constructing a resultquery using SOlrJ the method addFacetField overwrites the value set with setFacetMinCount to 1. Is this intentional or a small bug? Looks like it was intentional, but I agree it is a bad idea. I'll change it in sec ryan

[jira] Closed: (SOLR-403) Utilize Lucene 2.3's new Document/Field/Token reuse capabilities

[ https://issues.apache.org/jira/browse/SOLR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll closed SOLR-403. Resolution: Duplicate Dup of SOLR-330 Utilize Lucene 2.3's new Document/Field/Token reuse

[jira] Commented: (SOLR-414) Coherent plugin initialization strategy

[ https://issues.apache.org/jira/browse/SOLR-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546772 ] Ryan McKinley commented on SOLR-414: I am ok with relaxing the constraints. As implemented, we could change the

[jira] Updated: (SOLR-418) Editorial Query Boosting Component

[ https://issues.apache.org/jira/browse/SOLR-418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-418: --- Attachment: SOLR-418-QueryBoosting.patch Here is an updated patch that implements sorting. Rather

[jira] Updated: (SOLR-423) SolrRequestHandler close notification

[ https://issues.apache.org/jira/browse/SOLR-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley updated SOLR-423: --- Attachment: SOLR-423-CloseHook.patch This version adds a CloseHook to SolrCore. The test now looks

[jira] Commented: (SOLR-423) SolrRequestHandler close notification

[ https://issues.apache.org/jira/browse/SOLR-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546851 ] Ryan McKinley commented on SOLR-423: That then got me thinking that instead of a CloseHook we should probably

solr version upgrade

should i re-index all the data if i upgrade to the larest solr version? -- View this message in context: http://www.nabble.com/solr-version-upgrade-tf4899944.html#a14034971 Sent from the Solr - Dev mailing list archive at Nabble.com.

Re: solr version upgrade

On Nov 29, 2007 4:05 PM, anuvenk [EMAIL PROTECTED] wrote: should i re-index all the data if i upgrade to the larest solr version? No, it shouldn't be needed. -Yonik

[jira] Commented: (SOLR-424) The ruby output type produces incorrect output for numeric types without a value

[ https://issues.apache.org/jira/browse/SOLR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546905 ] Kurt Schrader commented on SOLR-424: The problem with making it zero is that it can cause problems if zero is a

[jira] Commented: (SOLR-424) The ruby output type produces incorrect output for numeric types without a value

[ https://issues.apache.org/jira/browse/SOLR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546910 ] Yonik Seeley commented on SOLR-424: --- If the field has no value, it should not be added to the index. Think about a

[jira] Commented: (SOLR-424) The ruby output type produces incorrect output for numeric types without a value

[ https://issues.apache.org/jira/browse/SOLR-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546923 ] Kurt Schrader commented on SOLR-424: I understand that, but the issue here is how to deal with indexes that have a

Re: solr version upgrade

On Nov 29, 2007 6:08 PM, anuvenk [EMAIL PROTECTED] wrote: I got this doubt because i added a few stopwords and synonyms but even after restarting solr tomacat, the stopwords and synonyms were still not being taken in to account by solr. Since we upgraded recently i wasn't sure if that was the

Re: solr version upgrade

On Nov 29, 2007 6:26 PM, anuvenk [EMAIL PROTECTED] wrote: The schema hasn't been updated in a long time though. I have the same version of solr the same index configs on my local PC and that seems to exlude the stop words i added while searching. Its quite puzzling why the new stopwords

Re: Removing duplicate results

: You can see all the results have 'credit report dispute' in the title. : Although they belong to different categories/states, it still looks : duplicate to the users. Can solr be made to not display the same result, if : a result with the same phrase in the 'title' has already been displayed?