[
https://issues.apache.org/jira/browse/SOLR-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600989#action_12600989
]
Jason Rutherglen commented on SOLR-561:
---
Is there a reason why IndexDeletionPolic
[
https://issues.apache.org/jira/browse/SOLR-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12600774#action_12600774
]
Jason Rutherglen commented on SOLR-583:
---
Node - instance of Solr webapp on a se
[
https://issues.apache.org/jira/browse/SOLR-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599698#action_12599698
]
Jason Rutherglen commented on SOLR-569:
---
Can use the Apache JDK6 ver
Please explain the maintenence considerations.
On Thu, May 22, 2008 at 5:35 PM, Chris Hostetter <[EMAIL PROTECTED]>
wrote:
>
> : SOLR-567 is simple enough to add to the list.
>
> I can't speak for anyone else, but SOLR-567 certianly doesn't meet my
> definition of "simple" ... this one line, by i
[
https://issues.apache.org/jira/browse/SOLR-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12599009#action_12599009
]
Jason Rutherglen commented on SOLR-583:
---
Discussions needs to refer to an issue t
Name Service
Key: SOLR-583
URL: https://issues.apache.org/jira/browse/SOLR-583
Project: Solr
Issue Type: New Feature
Affects Versions: 1.3
Reporter: Jason Rutherglen
Fix For: 1.3
Coordinates
SOLR-567 is simple enough to add to the list.
On Wed, May 21, 2008 at 7:45 PM, Mike Klaas <[EMAIL PROTECTED]> wrote:
> There seems to be some sort of consensus building that there should be a
> 1.3 release in the near future. The first step is to figure out what we
> want to finish before it get
[
https://issues.apache.org/jira/browse/SOLR-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen closed SOLR-578.
-
Resolution: Won't Fix
Fix Version/s: 1.3
Ok
> Binary stream response for
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: solr-567.patch
solr-567.patch
Moved SimpleFacets.getFieldCacheCounts to
[
https://issues.apache.org/jira/browse/SOLR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12598308#action_12598308
]
Jason Rutherglen commented on SOLR-564:
---
After review, function queries ValueSo
[
https://issues.apache.org/jira/browse/SOLR-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597956#action_12597956
]
Jason Rutherglen commented on SOLR-578:
---
It is incongruous to
[
https://issues.apache.org/jira/browse/SOLR-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597863#action_12597863
]
Jason Rutherglen commented on SOLR-578:
---
Or place it in SolrQueryResponse.
>
[
https://issues.apache.org/jira/browse/SOLR-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597862#action_12597862
]
Jason Rutherglen commented on SOLR-578:
---
Maybe this will work. The request han
Binary stream response for request
--
Key: SOLR-578
URL: https://issues.apache.org/jira/browse/SOLR-578
Project: Solr
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Jason Rutherglen
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: solr-567.patch
solr-567.patch
Moved defining the solrcoreclass to config
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: (was: solr.567.5.17.2008.patch)
> SolrCore Plugga
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: (was: solr.567.5.11.2008.patch)
> SolrCore Plugga
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: (was: solr.567.5.10.2008.patch)
> SolrCore Plugga
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: solr.567.5.17.2008.patch
solr.567.5.17.2008.patch
In the interest of minimizing
Reporter: Jason Rutherglen
Priority: Minor
Make org.apache.solr.search.DocSetHitCollector public for use by other code
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[
https://issues.apache.org/jira/browse/SOLR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595960#action_12595960
]
Jason Rutherglen commented on SOLR-564:
---
The patches are a way to see if integra
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595933#action_12595933
]
Jason Rutherglen commented on SOLR-567:
---
Forgot to mention about a couple of
Otis Gospodnetic wrote:
> Jason, are your patches in various other Solr JIRA issues essentially the
answer to your question above: Is there a way to plug into these low level
Solr functions without a massive redesign? In other words, are you providing
patches incrementally with the goal of getting
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: solr.567.5.11.2008.patch
solr.567.5.11.2008.patch
Needed to abstract SolrCore, old
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-567:
--
Attachment: solr.567.5.10.2008.patch
solr.567.5.10.2008.patch
Here's a rough patch o
Reporter: Jason Rutherglen
Priority: Minor
Looks like the SimpleFacets.getFieldCacheCounts could have small optimization:
{noformat}
startTermIndex = Arrays.binarySearch(terms,prefix,nullStrComparator);
if (startTermIndex<0) startTermIndex=-startTermIndex-1;
// find the
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595580#action_12595580
]
Jason Rutherglen commented on SOLR-567:
---
IndexSchema needs references to SolrCo
[
https://issues.apache.org/jira/browse/SOLR-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-568:
--
Attachment: solr.568.5.8.2008.patch
solr.568.5.8.2008.patch - MultiDocSet and TestMultiDocSet
[
https://issues.apache.org/jira/browse/SOLR-567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595408#action_12595408
]
Jason Rutherglen commented on SOLR-567:
---
I figured someone on the core team sh
MultiDocSet
---
Key: SOLR-568
URL: https://issues.apache.org/jira/browse/SOLR-568
Project: Solr
Issue Type: New Feature
Components: search
Affects Versions: 1.3
Reporter: Jason Rutherglen
Analogous to
SolrCore Pluggable
--
Key: SOLR-567
URL: https://issues.apache.org/jira/browse/SOLR-567
Project: Solr
Issue Type: Improvement
Affects Versions: 1.3
Reporter: Jason Rutherglen
SolrCore needs to be an
[
https://issues.apache.org/jira/browse/SOLR-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-564:
--
Description:
Before when I looked at this, the changes required to make Solr realtime would
: Jason Rutherglen
Before when I looked at this, the changes required to make Solr realtime would
seem to break the rest of Solr. Is this still the case? In project Ocean
http://code.google.com/p/oceansearch/ there is a realtime core however
integrating into Solr has looked like a redesign of
.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Sunday, September 3, 2006 4:41:58 PM
Subject: Re: Lazy field loading error
: I implemented lazy field loading in Solr, but then get messed up results
: or EOFExceptions. The index is fine, I turned off lazy loading and it
: looks fin
I implemented lazy field loading in Solr, but then get messed up results or
EOFExceptions. The index is fine, I turned off lazy loading and it looks fine.
Is this known behavior?
.
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Monday, August 28, 2006 8:13:11 PM
Subject: Re: Possible bug in copyField
: It's coming from a custom XML query handler which is just a
: s
o: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Monday, August 28, 2006 6:29:29 PM
Subject: Re: Possible bug in copyField
: Thanks. Yes I came up with a hacked solution to the problem. Takes a
: Query and rewrites the Terms using the Analyzer. If the Analyzer
typcially the
06, at 3:37 PM, jason rutherglen wrote:
> Could someone point me to where in the Solr code the Analyzer is
> applied to a query parser field?
IndexSchema.java is where the analyzers are created for indexing and
for query parsing. It's fairly sophisticated in order to take into
Aug 28, 2006, at 1:41 PM, jason rutherglen wrote:
> Ok... Looks like its related to using SpanQueries (I hacked on the
> XML query code). I remember a discussion about this issue. Not
> something Solr specifically supports so my apologies. However if
> anyone knows about this
> Do you mean lazy loading of fields?
Yes.
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Tuesday, August 22, 2006 5:23:48 PM
Subject: Re: Tackling Solr Fieldable
On 8/22/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
Is this being worked on? Otherwise I'll do it.
Why does the deleteByQuery method and the DirectUpdateHandler2 not use the
existing IndexSearcher for deleting. Why does it open it's own Searcher?
What about ReentrantLock? I like it because it cleans up sync blocks. Adds a
few nice methods. Makes threading more OO.
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Thursday, June
e. Is it needed for anything right now?
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Thursday, June 8, 2006 1:50:45 PM
Subject: Re: ReentrantReadWriteLock
On 6/8/06, jason rutherglen <[
Have the Solr team looked at using ReentrantReadWriteLock for things like
LRUCache and in other places where read write locks are used?
Yes that makes sense. I will develop along those lines. Thanks!
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Cc: jason rutherglen <[EMAIL PROTECTED]>
Sent: Thursday, May 18, 2006 7:28:12 PM
Subject: Re: Making RemoteSearchable lik
client for Solr
On 5/18/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> > If you query for "x OR y", the doc score you get will be a combination
> of the doc score for x and the doc score for y. After you have the
> document score for the complete query, you can'
res for
x and y anymore.
Can the /select call return the IDFs for each individual term in the XML result?
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Thursday, May 18, 2006 6:33:29 PM
Subject: Re: Making RemoteSearchable like clien
On 5/18/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> I used the XML, I think using HTTP is important.
Is this written in Java? Using HTTPClient? Anything you will be able to share?
No caching on the client yet, that is a good idea, however my personal
goal is to have an index that
: Re: Making RemoteSearchable like client for Solr
On 5/18/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> I used the XML, I think using HTTP is important.
Is this written in Java? Using HTTPClient? Anything you will be able to share?
No caching on the client yet, that is a good idea, h
current /select call? I'm still trying to figure this
part out.
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Thursday, May 18, 2006 5:21:58 PM
Subject: Re: Making RemoteSearchable like client for Solr
On 5/18/06, jason
A solution to an index that requires 100s of millions of documents is to
distributed the documents over multiple servers. I thought I had the
RemoteSearchable like client for Solr pretty well done, however this normalized
scoring with weights throws a bit of a kink.
http://issues.apache.org/b
Sorry to paste a bunch of code in here but I want to pass in order to make the
updateable IndexReader work, I need to pass in the existing IndexSearcher into
the new SolrIndexSearcher, however currently the existing SolrIndexSearcher is
obtained after in the code. The locking and referencing is
Can this be done today with a simple HTTP parameter to the /select? Mainly for
testing to see how long a query takes without using the cache.
Thanks that works well.
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: Solr Dev ; jason rutherglen <[EMAIL PROTECTED]>
Sent: Friday, April 28, 2006 1:58:57 PM
Subject: Re: Adding range filter to Solr
: This is a little bit confusing for me, the documentati
at org.apache.solr.core.SolrCore.execute(SolrCore.java:600)
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Thursday, April 27, 2006 7:50:04 PM
Subject: Re: Adding range filter to Solr
On 4/2
Are you saying that ConstantScoreRangeQuery is interpreted by the IndexSearcher
to be the same as a filter?
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Thursday, April 27, 200
Where would this go in the code? I want to add a new XML based request handler
so that spans and range filters can be handled. Thanks.
ginal Message
From: Doug Cutting <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Wednesday, April 26, 2006 11:27:44 AM
Subject: Re: GData, updateable IndexSearcher
jason rutherglen wrote:
> Interesting, does this mean there is a plan for incrementally updateable
> IndexSearchers
there any negatives to updateable
IndexSearchers?
Thanks,
Jason
- Original Message
From: Doug Cutting <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Tuesday, April 25, 2006 9:04:47 PM
Subject: Re: GData
jason rutherglen wrote:
> Ah ok
4:10:36 PM
Subject: Re: GData
jason rutherglen wrote:
> Is a faster method of loading or updating the IndexSearcher something that
> makes sense for Lucene?
Yes. Folks have developed incrementally updateable IndexSearchers
before, but none is yet part of Lucene.
> Or just assume the Go
essage
From: Doug Cutting <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Tuesday, April 25, 2006 4:10:36 PM
Subject: Re: GData
jason rutherglen wrote:
> Is a faster method of loading or updating the IndexSearcher something that
> makes sense for Lucene?
Yes. Folks
makes sense for
Lucene? Or just assume the Google architecture is a lot more complex.
- Original Message
From: Yonik Seeley <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Tuesday, April 25, 2006 3:21:07 PM
Subject: Re: GData
<[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Tuesday, April 25, 2006 12:42:58 PM
Subject: Re: GData
On 4/25/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> Here is a good blog entry with a talk on GData from someone who worked on i
http://code.google.com/apis/gdata/protocol.html#Optimistic-concurrency
The versioning is for updates only.
TED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECTED]>
Sent: Tuesday, April 25, 2006 12:42:58 PM
Subject: Re: GData
On 4/25/06, jason rutherglen <[EMAIL PROTECTED]> wrote:
> Here is a good blog entry with a talk on GData from someone who worked on it.
> The
http://jeremy.zawodny.com/blog/archives/006687.html
Here is a good blog entry with a talk on GData from someone who worked on it.
The only thing I think Solr needs is faster replication, which perhaps can be
done faster using a direct replication model, preferably over HTTP of the
segments fil
can be run manaully. So one can disable the postCommit
listener
and run it manually to take snapshots at specific times rather than after
every commit.
Bill
On 4/23/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
>
> Hi Jason,
>
> On 4/21/06, jason rutherglen <[EMAIL PROTECTED]> wr
on the master,
sometimes I want to create a snapshot for the slave servers. This was very
confusing when I first started using Solr.
Thanks,
Jason
- Original Message
From: Chris Hostetter <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org; jason rutherglen <[EMAIL PROTECT
In using Solr I've found the need to have a reload command in addition to a
commit. The reason for this is sometimes updates are made but are not
available via the server. The commit makes a snapshot which on a large index
is a potentially expensive operation. Is there a way to do reload toda
Does this mean that the Google system does some sort of realtime replication?
- Original Message
From: Doug Cutting <[EMAIL PROTECTED]>
To: solr-dev@lucene.apache.org
Sent: Thursday, April 20, 2006 8:59:01 AM
Subject: GData
How hard would it be to build a GData server using Solr? An
op
301 - 371 of 371 matches
Mail list logo
