I think you may have better luck setting up Eclipse, Subclipse etc and hook
off of trunk rather than having to re-create the eclipse project every time
a nightly build comes out.
I simply have an eclipse project tied to trunk and every so often i'll do an
SVN update when I want/need the latest
See http://hudson.zones.apache.org/hudson/job/Solr-trunk/959/changes
Hi Amit,
This is what I am looking for. Do you know the URL for trunk?
Thanks,
Pradeep.
--- On Sun, 10/18/09, Amit Nithian anith...@gmail.com wrote:
From: Amit Nithian anith...@gmail.com
Subject: Re: deploy solr in Eclipse IDE
To: solr-dev@lucene.apache.org
Date: Sunday, October 18, 2009,
-1 for weak references in caching.
This makes memory management less deterministic (predictable) and at
peak can cause cache-thrashing. In other words, the worst case gets
even more worse. When designing a system I want predictability and I
want to control the worst case, because system meltdowns
DocumentList and Document QueryResponseWriter
-
Key: SOLR-1516
URL: https://issues.apache.org/jira/browse/SOLR-1516
Project: Solr
Issue Type: New Feature
Components: search
Affects
[
https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris A. Mattmann updated SOLR-1516:
Attachment: SOLR-1516.Mattmann.101809.patch.txt
DocumentList and Document
[
https://issues.apache.org/jira/browse/SOLR-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-1506:
---
Attachment: SOLR-1506.patch
Fixes a bug, added Apache headers
Search multiple cores using
[
https://issues.apache.org/jira/browse/SOLR-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Rutherglen updated SOLR-1477:
---
Priority: Minor (was: Trivial)
Summary: Search on multi-tier cores (was: Search on
Lance,
Do you mean soft references?
On Sun, Oct 18, 2009 at 3:59 PM, Lance Norskog goks...@gmail.com wrote:
-1 for weak references in caching.
This makes memory management less deterministic (predictable) and at
peak can cause cache-thrashing. In other words, the worst case gets
even more
On Mon, Oct 19, 2009 at 4:29 AM, Lance Norskog goks...@gmail.com wrote:
-1 for weak references in caching.
This makes memory management less deterministic (predictable) and at
peak can cause cache-thrashing. In other words, the worst case gets
even more worse. When designing a system I want
[
https://issues.apache.org/jira/browse/SOLR-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shalin Shekhar Mangar updated SOLR-1516:
Fix Version/s: (was: 1.4)
1.5
Moving to 1.5. We are not
11 matches
Mail list logo