7;s necessary to invalidate the cache.
Jon
> -Original Message-
> From: Yonik Seeley [mailto:[EMAIL PROTECTED]
>
> On 9/6/07, Jonathan Woods <[EMAIL PROTECTED]> wrote:
> > As a quick sideline to the discussion on FunctionQueries
> (which is way
> > beyon
As a quick sideline to the discussion on FunctionQueries (which is way
beyond me): would it not be useful for a FunctionQuery to be able to exclude
hits (using that term loosely) as well as to affect their score? Can/should
the current framework do that?
I ask because I want to exclude hits on t
[
https://issues.apache.org/jira/browse/SOLR-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12525287
]
Jonathan Woods commented on SOLR-344:
-
Hoss - I take on board a lot of what you say, and I appreciate the fact you
I'm interested in knowing how people think SolrDocument is going to feature
in the 1.3 release, and wanted to make a few comments.
imho, SolrDocument's role is best kept as a kind of value object used only
for communications with remote clients. I don't think it should appear much
in the underly
[
https://issues.apache.org/jira/browse/SOLR-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Woods updated SOLR-344:
Attachment: New Java API for Solr.pdf
> New Java API
>
>
>
New Java API
Key: SOLR-344
URL: https://issues.apache.org/jira/browse/SOLR-344
Project: Solr
Issue Type: Improvement
Components: clients - java, search, update
Affects Versions: 1.3
Reporter: Jonathan
, update
Affects Versions: 1.2, 1.3
Reporter: Jonathan Woods
Priority: Minor
At the moment, wherever InterruptedException is caught, it's merely logged. In
all cases, we should consider propagating the interruption instead - after all,
InterruptedExceptions h
[
https://issues.apache.org/jira/browse/SOLR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519198
]
Jonathan Woods commented on SOLR-332:
-
I understand.
Feel free to close this issue if you think that
[
https://issues.apache.org/jira/browse/SOLR-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Woods updated SOLR-328:
Attachment: ObjectField.patch
For what it's worth, I've attached a first att
[
https://issues.apache.org/jira/browse/SOLR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518806
]
Jonathan Woods commented on SOLR-332:
-
I'm implementing ObjectField extends FieldType as per
[
https://issues.apache.org/jira/browse/SOLR-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518788
]
Jonathan Woods commented on SOLR-332:
-
I should have said: I'm assuming that the right way to define '
://issues.apache.org/jira/browse/SOLR-332
Project: Solr
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Jonathan Woods
Priority: Minor
Constants in org.apache.solr.schema aren't visible to classes outside that
package, yet they're useful e.g.
I'm moving a content management system's Lucene library over to Solr to reap
the benefits, but along the way I'm meeting some problems which I imagine
affect everyone doing the same kind of thing.
I realise that Solr began life as something which was primarily designed to
be used over HTTP or wit
Issue Type: New Feature
Components: search
Affects Versions: 1.3
Reporter: Jonathan Woods
Priority: Minor
A while back I developed a means of storing and retrieving arbitrary Objects in
a Lucene Document [Field], and I thought that something similar might be
14 matches
Mail list logo