[jira] Commented: (SOLR-404) Client for Coldfusion

2007-10-31 Thread sami hoda (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539152 ] sami hoda commented on SOLR-404: This is a big opportunity for the Solr project to mesh with the legendary Adobe ColdF

[jira] Updated: (SOLR-404) Client for Coldfusion

2007-10-31 Thread Wayne Graham (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wayne Graham updated SOLR-404: -- Attachment: SolColdfusion.tar.gz The client library > Client for Coldfusion > - > >

[jira] Created: (SOLR-404) Client for Coldfusion

2007-10-31 Thread Wayne Graham (JIRA)
Client for Coldfusion - Key: SOLR-404 URL: https://issues.apache.org/jira/browse/SOLR-404 Project: Solr Issue Type: New Feature Affects Versions: 1.2 Environment: Coldfusion >= 7 Solr >= 1.2 Repor

Re: SolrQueryParser Default Operator from schema.xml broken in trunk?

2007-10-31 Thread raikoe
Yonik Seeley wrote: > > I think I've fixed it... can you try the latest trunk? > > -Yonik > Yes, now it works :) Thanks for the quick fixing. Raiko -- View this message in context: http://www.nabble.com/SolrQueryParser-Default-Operator-from-schema.xml-broken-in-trunk--tf4724215.html#a13

Re: SolrQueryParser Default Operator from schema.xml broken in trunk?

2007-10-31 Thread Yonik Seeley
On 10/31/07, raikoe <[EMAIL PROTECTED]> wrote: > today i updated the solr libs in my application to the current trunk > version. It seems that the default operator (which i defined AND in my > schema.xml) is not considered anymore when creating the new SolrQueryParser > in LuceneQParserPlugin.java:

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

2007-10-31 Thread Grant Ingersoll (JIRA)
Utilize Lucene 2.3's new Document/Field/Token reuse capabilities Key: SOLR-403 URL: https://issues.apache.org/jira/browse/SOLR-403 Project: Solr Issue Type: Improvement

[jira] Updated: (SOLR-324) solr can't perform sort by long field

2007-10-31 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated SOLR-324: - Attachment: SOLR-324.patch Patch based on latest trunk of Lucene, where I committed the changes to

[jira] Work started: (SOLR-324) solr can't perform sort by long field

2007-10-31 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on SOLR-324 started by Grant Ingersoll. > solr can't perform sort by long field > - > > Key: SOLR-324 >

[jira] Updated: (SOLR-324) solr can't perform sort by long field

2007-10-31 Thread Grant Ingersoll (JIRA)
[ https://issues.apache.org/jira/browse/SOLR-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Grant Ingersoll updated SOLR-324: - Priority: Minor (was: Major) > solr can't perform sort by long field > ---

SolrQueryParser Default Operator from schema.xml broken in trunk?

2007-10-31 Thread raikoe
Hello, today i updated the solr libs in my application to the current trunk version. It seems that the default operator (which i defined AND in my schema.xml) is not considered anymore when creating the new SolrQueryParser in LuceneQParserPlugin.java:66. In my query I do not define the default op