Build failed in Hudson: Solr-trunk #557

See http://hudson.zones.apache.org/hudson/job/Solr-trunk/557/changes Changes: [yonik] lucene update 2.4-dev r691741 [yonik] SOLR-747: update example solrconfig.xml [gsingers] SOLR-749: Allow QParser and ValueSourceParser to be overridden -- [...truncated

[jira] Resolved: (SOLR-743) Update the bitset usage in Schema to enums

[ https://issues.apache.org/jira/browse/SOLR-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mark Miller resolved SOLR-743. -- Resolution: Invalid I still have interest in going over this myself, but as far as solr is concerned, I

1.3.0 RC2

Is available at http://people.apache.org/~gsingers/solr/1.3-RC2/ I've included the signatures this time. If you want to download the whole directory, you can get solr.tar As always, let me know any issues, etc. Later today I will let solr- user know about RC2. -Grant

Re: Forrest PDF non-Latin-1 support [was: RE: prototype Solr 1.3 RC 1]

Thank you Steve! See, I knew you'd nail it. I don't want to complicate lives of others just because of one little diacritic. Otis -- Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch - Original Message > From: Steven A Rowe <[EMAIL PROTECTED]> > To: solr-dev@lucene.apache.or

[jira] Updated: (SOLR-651) A SearchComponent for fetching TF-IDF values

[ https://issues.apache.org/jira/browse/SOLR-651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated SOLR-651: - Attachment: SOLR-651.patch Here's a first crack at this. It still needs more unit tests to exercis

Re: Forrest PDF non-Latin-1 support [was: RE: prototype Solr 1.3 RC 1]

On Fri, 2008-08-29 at 17:57 -0400, Steven A Rowe wrote: > On 08/29/2008 at 3:24 PM, Chris Hostetter wrote: > > I suspect the PDF formatter just doesn't play nicely with the > > non-trivial UTF-8 characters. ... > > There's an open Forrest bug for this problem: >

RE: Forrest PDF non-Latin-1 support [was: RE: prototype Solr 1.3RC 1]

Hi Thorsten, On 09/04/2008 at 3:57 PM, Thorsten Scherler wrote: > On Fri, 2008-08-29 at 17:57 -0400, Steven A Rowe wrote: > > On 08/29/2008 at 3:24 PM, Chris Hostetter wrote: > > > I suspect the PDF formatter just doesn't play nicely with the > > > non-trivial UTF-8 characters. > ... > > > > Ther

[jira] Commented: (SOLR-42) Highlighting problems with HTMLStripWhitespaceTokenizerFactory

[ https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628473#action_12628473 ] Lance Norskog commented on SOLR-42: --- A slight nit: Unicode contains three characters, fffD,

[jira] Commented: (SOLR-42) Highlighting problems with HTMLStripWhitespaceTokenizerFactory

[ https://issues.apache.org/jira/browse/SOLR-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628475#action_12628475 ] Lance Norskog commented on SOLR-42: --- Another bigger nit: the last time I studied this, the H

Purpose of CSVRequestHandler / CSVLoader Split?

Whereas the XmlUpdateRequestHandler handles its whole request within a single class, the CSVRequestHandler delegates almost all of its implementation to a CSVLoader class. Is there a short answer to why there would be a split in one case and not the other? (I guess I'm bothered because I'm having t

Re: Purpose of CSVRequestHandler / CSVLoader Split?

: Whereas the XmlUpdateRequestHandler handles its whole request within a : single class, the CSVRequestHandler delegates almost all of its : implementation to a CSVLoader class. Is there a short answer to why : there would be a split in one case and not the other? (I guess I'm Off the cuff: I *t

[jira] Commented: (SOLR-567) SolrCore Pluggable

[ https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12628541#action_12628541 ] Noble Paul commented on SOLR-567: - The code has changed drastically since the last patch is c