[jira] Resolved: (SOLR-1346) undefined term in dismaxhandler doc

[ https://issues.apache.org/jira/browse/SOLR-1346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man resolved SOLR-1346. Resolution: Invalid as noted at the top of the page... bq. In addition to the CommonQueryParameters,

[jira] Commented: (SOLR-914) Presence of finalize() in the codebase

[ https://issues.apache.org/jira/browse/SOLR-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743562#action_12743562 ] Hoss Man commented on SOLR-914: --- I don't understand objections to the idea that finalize should

[jira] Assigned: (SOLR-914) Presence of finalize() in the codebase

[ https://issues.apache.org/jira/browse/SOLR-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hoss Man reassigned SOLR-914: - Assignee: Hoss Man Presence of finalize() in the codebase ---

Solr nightly build failure

init-forrest-entities: [mkdir] Created dir: /tmp/apache-solr-nightly/build [mkdir] Created dir: /tmp/apache-solr-nightly/build/web compile-solrj: [mkdir] Created dir: /tmp/apache-solr-nightly/build/solrj [javac] Compiling 84 source files to /tmp/apache-solr-nightly/build/solrj

Hudson build is back to normal: Solr-trunk #896

See http://hudson.zones.apache.org/hudson/job/Solr-trunk/896/changes

date functions and floats

Now that we have date fields that internally store milliseconds (and can currently be used in function queries) we have the basis for a good replacement for using things like ord(date)... which is now a bad idea since it causes the FieldCache to be instantiated at the highest level reader...

lucene upgrade

FYI, I plan on updating the lucene libs once LUCENE-1794 is checked in. -Yonik http://www.lucidimagination.com

Re: date functions and floats

: We could either: : - change function queries to use doubles internally - probably a good : idea for the future in general - seems like geo might need more : precision too. : - come up with a new date scale function that uses doubles internally? off the cuff idea i remember thinking of a long

Re: date functions and floats

On Sat, Aug 15, 2009 at 11:16 AM, Chris Hostetterhossman_luc...@fucit.org wrote: : We could either: : - change function queries to use doubles internally - probably a good : idea for the future in general - seems like geo might need more : precision too. : - come up with a new date scale

[jira] Commented: (SOLR-914) Presence of finalize() in the codebase

[ https://issues.apache.org/jira/browse/SOLR-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743773#action_12743773 ] Lance Norskog commented on SOLR-914: Yes, Solr should keep working. But somewhere in the

[jira] Commented: (SOLR-1143) Return partial results when a connection to a shard is refused

[ https://issues.apache.org/jira/browse/SOLR-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12743775#action_12743775 ] Lance Norskog commented on SOLR-1143: - If the search subsystem has a problem, the ops

Re: date functions and floats

: Yeah, I've had the same idea... typing of the functions. I think : we'll get to that sooner or later, but I'm not sure it's something we : can do for 1.4, and it would seem to cause a proliferation of classes : (or switch statements at every level?). i don't see why it would cause either ...