[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493006
]
Ryan McKinley commented on SOLR-20:
---
great! Any feedback/help would be wonderful.
I hope it is not *too* long before
[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-217:
--
Attachment: ignoreUnnamedFields_v3.patch
added a simple test to the existing patch.
one thing to note is that th
[
https://issues.apache.org/jira/browse/SOLR-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-217:
-
Assignee: Hoss Man
> schema option to ignore unused fields
> -
>
>
SolrQueryParser should do more error checking
-
Key: SOLR-223
URL: https://issues.apache.org/jira/browse/SOLR-223
Project: Solr
Issue Type: Improvement
Components: search
Repo
[
https://issues.apache.org/jira/browse/SOLR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man reassigned SOLR-115:
-
Assignee: Hoss Man
> replace BooleanQuery.getClauses() with clauses()
> ---
[
https://issues.apache.org/jira/browse/SOLR-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-115:
--
Attachment: SOLR-115.patch
audited all of our uses of getClausese() ... they were mainly for iteration,
and a fe
[
https://issues.apache.org/jira/browse/SOLR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Hiatt updated SOLR-199:
Attachment: SOLR-199-n-gram.patch
This is the new patch, not just cut out of SOLR-81...
I removed references
Good point. That looks flat out broken.
-- Adam
On May 1, 2007, at 2:16 PM, Chris Hostetter wrote:
: > NGramTokenizerFactory is refering to constants from, and
constructing
: an instance of, EdgeNGramTokenizer
: Are you saying that this worries you b/c it is referenced in the
example
: > NGramTokenizerFactory is refering to constants from, and constructing
: an instance of, EdgeNGramTokenizer
: Are you saying that this worries you b/c it is referenced in the example
: schema and will thus break without the lucene-analyzers package? I do
: agree that this example should probab
[
https://issues.apache.org/jira/browse/SOLR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492948
]
Adam Hiatt commented on SOLR-199:
-
I'll make those changes. I agree that we don't want bloated base classes.
> NGramTo
[
https://issues.apache.org/jira/browse/SOLR-199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492947
]
Hoss Man commented on SOLR-199:
---
NGramTokenizerFactory is refering to constants from, and constructing an
instance of, E
[
https://issues.apache.org/jira/browse/SOLR-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man resolved SOLR-137.
---
Resolution: Fixed
Assignee: Yonik Seeley
this was fixed by yonik on April 11 in r527594
http://svn.apach
: goes to:
: http://lucene.apache.org/solr/api/index.html (404)
:
: we should probably fix that!
The link is correct, that's where they are suppose to be -- the
problem seems to be that buildingthe javadocs is currently broken
When i run "ant javadoc" locally i'm getting a bunch of warnings a
In teh future, please direct questions like this about "using" solr to the
solr-user list ... it has more subscribers so there are more people to
offer advice.
: For the sake of performance, I want to suppress output of which inside . But need
: to be reserved.
just specify an "fl" list which
It works!
By the way, fl=field1+field2+ also works :-)
-Original Message-
From: Mike Klaas [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 1:40 AM
To: solr-dev@lucene.apache.org
Subject: Re: The ability to offering offset of keyword in search result
On 5/1/07, David Xiao <
found the problem in DirectSolrConnection.java, we were tickling this
bug...
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5082928
...my gut says not to try and manually fix the site right now, and just
wait for the next nightly to take care of it -- mainly because i'm
paranoid about messin
Ryan: this should probably be called out in the CHANGES.txt as a change in
behavior.
: Date: Tue, 01 May 2007 09:02:08 -
: From: [EMAIL PROTECTED]
: Reply-To: solr-dev@lucene.apache.org
: To: [EMAIL PROTECTED]
: Subject: svn commit: r533978 -
: /lucene/solr/trunk/src/webapp/src/org/apache
: advertise http over https for read-only access, as it causes less load
: on our servers, and possibly less firewall problems.
M ... gotcha, that makes sense.
-Hoss
On 5/1/07, David Xiao <[EMAIL PROTECTED]> wrote:
Would you please give me an example? For example, I want to pick only
fieldname="features"
from the query result
Try something like:
?q=a+query&hl=true&hl.fl=features&fl=features
-Mike
[
https://issues.apache.org/jira/browse/SOLR-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12492902
]
Will Johnson commented on SOLR-20:
--
the new api's work great, thanks! what's the plan for this going forward? id'
li
the javadoc link from:
http://lucene.apache.org/solr/
goes to:
http://lucene.apache.org/solr/api/index.html (404)
we should probably fix that!
Would you please give me an example? For example, I want to pick only
fieldname="features"
from the query result
Regards,
David
-Original Message-
From: Chris Hostetter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 24, 2007 1:50 AM
To: solr-dev@lucene.apache.org
Subject: RE: The abili
Hello,
I am using parameter: “hl=true&hl.fl=features” to query fragment. I receive
following xml result from solr server:
-
Full document contents comes here, Blah blah ………
-
23 matches
Mail list logo
