RE: solr plug-in - external document store

ok, I now have a ExternalStoreRequestHandler that extends RequestHandlerBase. how do include extra fields in documents that get rendered by the SolrQueryResponse? do I need to recreate the DocList? > -Original Message- > From: Ben Incani [mailto:[EMAIL PROTECTED] > Sent: Thursday, 24

[jira] Updated: (SOLR-303) Distributed Search over HTTP

[ https://issues.apache.org/jira/browse/SOLR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yonik Seeley updated SOLR-303: -- Attachment: distributed.patch Updated patch: - face refinement requests piggyback on the requests to retr

[jira] Commented: (SOLR-470) DateField throws error on iso8601 date

[ https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565637#action_12565637 ] patrick o'leary commented on SOLR-470: -- parseMath returns a Date object that's formated

Re: For an "XML" fieldtype

Hi all, Sorry to repost on this issue. Is there a regular way to use a field to store XML source of a document? If not, is a fieldType the solution ? Or, is it a "solr-user" question ? Sorry if I have post in the bad place. -- Frédéric Glorieux École nationale des chartes Direction des nouve

[jira] Commented: (SOLR-470) DateField throws error on iso8601 date

[ https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565584#action_12565584 ] Hoss Man commented on SOLR-470: --- I'm notsure i understand your comment ... i don't see any reas

[jira] Commented: (SOLR-470) DateField throws error on iso8601 date

[ https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565571#action_12565571 ] patrick o'leary commented on SOLR-470: -- It's a little iffy but what if you just default

[jira] Updated: (SOLR-470) DateField throws error on iso8601 date

[ https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man updated SOLR-470: -- Fix Version/s: 1.3 > DateField throws error on iso8601 date > -- > >

[jira] Assigned: (SOLR-470) DateField throws error on iso8601 date

[ https://issues.apache.org/jira/browse/SOLR-470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reassigned SOLR-470: - Assignee: Hoss Man a quick glance at the code verifies this (to me anyway ... i haven't written a test cas

[jira] Issue Comment Edited: (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&focusedCommentId=12565561#action_12565561 ] yourabi edited comment on SOLR-424 at 2/4/08 2:03 PM: Since all r

[jira] Updated: (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:all-tabpanel ] Yousef Ourabi updated SOLR-424: --- Attachment: TextResponseWriter-SOLR-424.patch Tweak line 115 of TextResponseWriter.writeVal() to test n

[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&focusedCommentId=12565561#action_12565561 ] Yousef Ourabi commented on SOLR-424: Since all response writers implement the TextRespons

Re: Build failed in Hudson: Solr-trunk #341

On 4-Feb-08, at 12:25 AM, Apache Hudson Server wrote: [junit] Running org.apache.solr.update.AutoCommitTest [junit] [junit] 0int>0numFound="0" start="0"/> [junit] [junit] ) [junit] Tests run: 3, Failures: 1, Errors: 0, Time elapsed: 6.349 sec [junit] Test org.a

Re: parse exception results in 500 error

agree -- 400 with a meaningful message is a better error. Yonik Seeley wrote: Right now, a parse exception results in a 500 http error code, when it should be 400. There are a number of places this could be handled, but I'm thinking in this case it should be done right at the source (that QPars

parse exception results in 500 error

Right now, a parse exception results in a 500 http error code, when it should be 400. There are a number of places this could be handled, but I'm thinking in this case it should be done right at the source (that QParser.parse() and getQuery() should throw SolrExceptions with 400 error codes instead

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

[ https://issues.apache.org/jira/browse/SOLR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12565468#action_12565468 ] Charles Hornberger commented on SOLR-236: - bq. However, instead of requiring each and

Build failed in Hudson: Solr-trunk #341

See http://hudson.zones.apache.org/hudson/job/Solr-trunk/341/changes -- [...truncated 1114 lines...] AUclient/ruby/solr-ruby/lib/solr/importer/xpath_mapper.rb A client/ruby/solr-ruby/lib/solr/importer/hpricot_mapper.rb A client/ruby/s