[jira] Commented: (SOLR-440) Should use longs for internal DateField storage

[ https://issues.apache.org/jira/browse/SOLR-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555493#action_12555493 ] Stu Hood commented on SOLR-440: --- Thanks a lot for the explanation, I think I get it now. That

Re: purpose of MultiCore "default" ?

: That leaves one purpose of MultiCore "default" -- there may be a better : solution for it: the "default" core is used to set the web-app wide variables : configured in solrconfig.xml: : requestDispatcher/requestParsers/@multipartUploadLimitInKB : requestDispatcher/requestParsers/@enableRemote

[jira] Created: (SOLR-449) python (and presumably ruby) writer can generate NaN

python (and presumably ruby) writer can generate NaN Key: SOLR-449 URL: https://issues.apache.org/jira/browse/SOLR-449 Project: Solr Issue Type: Bug Affects Versions: 1.3 R

[jira] Commented: (SOLR-440) Should use longs for internal DateField storage

[ https://issues.apache.org/jira/browse/SOLR-440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12555450#action_12555450 ] Hoss Man commented on SOLR-440: --- >From an email reply i'm just now looking at... {noformat} Da

Re: remove raw-schema.jsp?

thats my feeling... the more code we can remove from .jsp files, the better. SOLR-142 did add a deprecation warning to get-file.jsp -- but I think that is reasonable to keep around since (i think) some people depend on it to read the remote schema/config. ryan Mike Klaas wrote: I don't th

Re: remove raw-schema.jsp?

I don't think a deprecation warning is necessary (it's not really part of the "interface" of Solr). -Mike On 2-Jan-08, at 9:14 AM, Ryan McKinley wrote: Hello- Is raw-schema.jsp in use? It isn't (nor has it been) linked to anything. The schema/config links used to point to get-file.jsp

[jira] Resolved: (SOLR-142) RawResponseWriter - replace /admin/get-file.jsp

[ https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley resolved SOLR-142. Resolution: Fixed Fix Version/s: 1.3 > RawResponseWriter - replace /admin/get-file.jsp > -

remove raw-schema.jsp?

Hello- Is raw-schema.jsp in use? It isn't (nor has it been) linked to anything. The schema/config links used to point to get-file.jsp Should we remove it? Add a deprecation warning? ryan

[jira] Assigned: (SOLR-142) RawResponseWriter - replace /admin/get-file.jsp

[ https://issues.apache.org/jira/browse/SOLR-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ryan McKinley reassigned SOLR-142: -- Assignee: Ryan McKinley > RawResponseWriter - replace /admin/get-file.jsp > -

Hudson build is back to normal: Solr-Nightly #307

See http://lucene.zones.apache.org:8080/hudson/job/Solr-Nightly/307/changes

Build failed in Hudson: Solr-Nightly #306

See http://lucene.zones.apache.org:8080/hudson/job/Solr-Nightly/306/changes -- [...truncated 461 lines...] AUsrc/java/org/apache/solr/request/LocalSolrQueryRequest.java AUsrc/java/org/apache/solr/request/MultiMapSolrParams.java AUsrc/

Solr nightly build failure

init-forrest-entities: [mkdir] Created dir: /tmp/apache-solr-nightly/build compile-common: [mkdir] Created dir: /tmp/apache-solr-nightly/build/common [javac] Compiling 31 source files to /tmp/apache-solr-nightly/build/common [javac] Note: Some input files use unchecked or unsafe o