RE: Lucene Turbine Service
Seth,
Not really. I've included here my SearchService interface though, which you
might want to check out.
I'm not sure what your intended or current usage is, so don't know how relevant
my implementation is for you...
public interface SearchService
{
public static final String CONFIGURATION_FILE = search.xml;
public static final String
INCREMENTAL_INDEX_ENABLED_KEY = index.incremental;
public static final String
SEARCH_RESULT_DEFAULT_NAMESPACE_KEY =
[EMAIL PROTECTED];
public SearchResults search(Query query) throws ServiceException;
public SearchResults search(Query query, Filter filter) throws
ServiceException;
public SearchResults search(Query query, Filter filter,
int from, int to) throws ServiceException;
public SearchResults search(Query query, Filter filter,
int from, int to, String namespace) throws
ServiceException;
public void batchIndex() throws ServiceException;
public boolean incrementalIndexEnabled();
public void addObjectIndex(ObjectIndexer indexer) throws Exception;
public void updateObjectIndex(ObjectIndexer indexer)
throws Exception;
public Document deleteObjectIndex(String objectId) throws IOException,
InterruptedException;
public Analyzer getAnalyzer();
public IndexWriter getIndexWriter(boolean create) throws IOException;
}
On Sun, 2 Mar 2003 15:04:17 -0500, Seth Weiner said:
Kelvin,
Have you had a chance to check in any of your search subsystem
components? I know it's been a while since I mentioned the issue,
but I'd love to make some headway on a solid Turbine search
subsystem for general consumption.
Thanks, Seth
-Original Message-
From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Sunday,
January 26, 2003 8:17 PM To: Lucene Users List Subject: RE: Lucene
Turbine Service
Seth,
I had been meaning to do it for awhile, but inertia was
overwhelming. Then I recently needed to be able to modify the
configuration of the service at runtime, and Fulcrum didn't support
that, so I just refactored my way out of it. :-)
Why had I been wanting to do it? well, on hindsight, I think it
never was a good candidate for a turbine service in the first place.
the way i see it, a good candidate requires
a) Lifecycle support b) Configuration c) Pluggable implementations
For LuceneSearchService, a) was minimal, b) yes but not a big factor
and c) turned out to be impractical. I had hopes of creating a
SearchService where one could plug-in various implementations (check
out http://www.mail-archive.com/lucene-
[EMAIL PROTECTED]/msg01461.htm l) but gave up in the end.
Let me see if I can cleanup the subsystem I've refactored out and
check it in to Sandbox, then maybe we can discuss from there?
KT
On Tue, 21 Jan 2003 19:35:40 -0500, Seth Weiner said:
Thanks for the pointer! Might I ask what the motivation for the
refactoring was?
On a separate note I just took a look at the service in the
sandbox. It
doesn't appear to support addition of documents to the index.
Shouldn't
be hard to add, just seems like a strange ommision. Also, wouldn't
it be more efficient for the service to maintain a pool of
IndexSearchers rather than creating a new one for each search? Or
is there a problem with holding one or more index searchers open on
an index? To add/remove a document to the index, would all of the
IndexSearchers need to be closed, or is this safe to do?
The simple app I'm trying to write allows for the searching of an
index
through a turbine webapp interface as well as the ability to upload
a document through the webapp to be added to the index. If the
document exists in the index it's deleted and then the new version
is added.
If anyone's already done this feel free to share;) And while
you're in a charitable mood, my next step is to take the Lucene
service and make it an XMLRPC webservice. Thoughts and suggestions
on that idea are greatly appreciated.
Thanks, Seth
-Original Message-
From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Tuesday,
January 21, 2003 7:16 PM To: Lucene Users List Subject: Re: Lucene
Turbine Service
Yep. Look in Lucene Sandbox. Interesting you should ask, though,
because after about a year of using the LuceneSearchService, I've
recently refactored it out into a subsystem of its own...:-)
Regards, Kelvin
The book giving manifesto - http://how.to/sharethisbook
On Tue, 21 Jan 2003 18:44:33 -0500, Seth Weiner said:
Hi,
I'm fairly new to Lucene and am trying to create a 'simple'
Turbine webapp that will use Lucene for some indexing. Has
anyone written a simple Turbine/Fulcrum Lucene service for
searching and indexing documents?
Thanks, Seth Weiner
--
To unsubscribe, e-mail: mailto:lucene-user-
[EMAIL PROTECTED] For additional commands, e-mail:
mailto:lucene-user-
[EMAIL PROTECTED]
--
To unsubscribe, e-mail: mailto:lucene-user-
[EMAIL PROTECTED
RE: Lucene Turbine Service
Hi, Any one tried Incremental Indexing with Lucene. If so then kindly guide me how to do that?? Thanks a ton in advance Nellai... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Lucene Turbine Service
-Original Message-
From: Nellaiyappan Gomathinayagam
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 04, 2003 5:10 PM
To: Lucene Users List
Subject: RE: Lucene Turbine Service
Hi,
Any one tried Incremental Indexing with Lucene. If so then
kindly guide me how to do that??
What do you mean by 'incremental'? Adding a single entry/document to an index?
public void indexSingleEntry (File indexFile, String id, String cat, String prob,
String sol){
IndexWriter writer = null;
try {
Analyzer analyzer = new GermanAnalyzer();
writer = new IndexWriter(indexFile, analyzer, false);
Document doc = new Document();
doc.add(Field.Text(id, id));
doc.add(Field.Text(category, cat));
doc.add(Field.Text(problem, prob));
doc.add(Field.UnStored(solution, sol));
writer.addDocument(doc);
}
catch (Exception ex) {
ex.printStackTrace();
} finally {
if (null != writer) {
try {
writer.close();
} catch (Exception ex) {
ex.printStackTrace();
}
}
}
}
Marcel
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Lucene Turbine Service
Samuel, Not exactly sure of your question. But, if the path is known at the time of indexing, you just insert it in the Document that is created as part of the indexing. If you don't know the path till later, you might insert a partial path at index time and add the exact location when you use it. For example, in my own system, I use a structure called master_db, which has a standard structure underneath it. However, this whole database might be located anywhere for any given deployment. So, when I index, I define my document's location within this master_db structure as the path field. Then when I retrieve it, I simply doc.get(path) and tack it on to the actual location. As I said, I'm not sure this is exactly what you're looking for, but HTH anyway. Regards, Terry - Original Message - From: Samuel Alfonso Velázquez Díaz [EMAIL PROTECTED] To: Lucene Users List [EMAIL PROTECTED] Sent: Tuesday, March 04, 2003 11:34 AM Subject: RE: Lucene Turbine Service Hi I'm a newbe to lucene, I have troubles creating the index to be usable by my web application. The problem is that with the guide lines of the documentation, I created a index with URLs relative to my local file system doc.get(url); // Returns paths like C:/CopiaSite20030228/Legislacion/reglamentos/index.htm How can I create an index and specify that the ROOT of my documents points to mydomain.com?? Please help, I've been searching the docs and mailing list, but I've been without luck!! Regards! Samuel Alfonso Velázquez Díaz http://www.geocities.com/samuelvd [EMAIL PROTECTED] - Do you Yahoo!? Yahoo! Tax Center - forms, calculators, tips, and more - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Lucene Turbine Service
Kelvin, Have you had a chance to check in any of your search subsystem components? I know it's been a while since I mentioned the issue, but I'd love to make some headway on a solid Turbine search subsystem for general consumption. Thanks, Seth -Original Message- From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Sunday, January 26, 2003 8:17 PM To: Lucene Users List Subject: RE: Lucene Turbine Service Seth, I had been meaning to do it for awhile, but inertia was overwhelming. Then I recently needed to be able to modify the configuration of the service at runtime, and Fulcrum didn't support that, so I just refactored my way out of it. :-) Why had I been wanting to do it? well, on hindsight, I think it never was a good candidate for a turbine service in the first place. the way i see it, a good candidate requires a) Lifecycle support b) Configuration c) Pluggable implementations For LuceneSearchService, a) was minimal, b) yes but not a big factor and c) turned out to be impractical. I had hopes of creating a SearchService where one could plug-in various implementations (check out http://www.mail-archive.com/[EMAIL PROTECTED]/msg01461.htm l) but gave up in the end. Let me see if I can cleanup the subsystem I've refactored out and check it in to Sandbox, then maybe we can discuss from there? KT On Tue, 21 Jan 2003 19:35:40 -0500, Seth Weiner said: Thanks for the pointer! Might I ask what the motivation for the refactoring was? On a separate note I just took a look at the service in the sandbox. It doesn't appear to support addition of documents to the index. Shouldn't be hard to add, just seems like a strange ommision. Also, wouldn't it be more efficient for the service to maintain a pool of IndexSearchers rather than creating a new one for each search? Or is there a problem with holding one or more index searchers open on an index? To add/remove a document to the index, would all of the IndexSearchers need to be closed, or is this safe to do? The simple app I'm trying to write allows for the searching of an index through a turbine webapp interface as well as the ability to upload a document through the webapp to be added to the index. If the document exists in the index it's deleted and then the new version is added. If anyone's already done this feel free to share;) And while you're in a charitable mood, my next step is to take the Lucene service and make it an XMLRPC webservice. Thoughts and suggestions on that idea are greatly appreciated. Thanks, Seth -Original Message- From: Kelvin Tan [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 7:16 PM To: Lucene Users List Subject: Re: Lucene Turbine Service Yep. Look in Lucene Sandbox. Interesting you should ask, though, because after about a year of using the LuceneSearchService, I've recently refactored it out into a subsystem of its own...:-) Regards, Kelvin The book giving manifesto - http://how.to/sharethisbook On Tue, 21 Jan 2003 18:44:33 -0500, Seth Weiner said: Hi, I'm fairly new to Lucene and am trying to create a 'simple' Turbine webapp that will use Lucene for some indexing. Has anyone written a simple Turbine/Fulcrum Lucene service for searching and indexing documents? Thanks, Seth Weiner -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Lucene Turbine Service
Otis, hahaha...I'm not sure its all THAT much better than the one in Sandbox, but I'll clean it up when its ready and check it in for people to take a look anyways. What's with our Lucene App Framework? seems to have lost a little steam... KT On Sat, 25 Jan 2003 21:13:46 -0800 (PST), Otis Gospodnetic said: Kelvin, --- Kelvin Tan [EMAIL PROTECTED] wrote: Yep. Look in Lucene Sandbox. Interesting you should ask, though, because after about a year of using the LuceneSearchService, I've recently refactored it out into a subsystem of its own...:-) Something better than your existing fulcrum contribution in the Sandbox? Something you'd want to donate? Otis __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Lucene Turbine Service
Seth, I had been meaning to do it for awhile, but inertia was overwhelming. Then I recently needed to be able to modify the configuration of the service at runtime, and Fulcrum didn't support that, so I just refactored my way out of it. :-) Why had I been wanting to do it? well, on hindsight, I think it never was a good candidate for a turbine service in the first place. the way i see it, a good candidate requires a) Lifecycle support b) Configuration c) Pluggable implementations For LuceneSearchService, a) was minimal, b) yes but not a big factor and c) turned out to be impractical. I had hopes of creating a SearchService where one could plug-in various implementations (check out http://www.mail-archive.com/lucene-dev@jakarta.apache.org/msg01461.htm l) but gave up in the end. Let me see if I can cleanup the subsystem I've refactored out and check it in to Sandbox, then maybe we can discuss from there? KT On Tue, 21 Jan 2003 19:35:40 -0500, Seth Weiner said: Thanks for the pointer! Might I ask what the motivation for the refactoring was? On a separate note I just took a look at the service in the sandbox. It doesn't appear to support addition of documents to the index. Shouldn't be hard to add, just seems like a strange ommision. Also, wouldn't it be more efficient for the service to maintain a pool of IndexSearchers rather than creating a new one for each search? Or is there a problem with holding one or more index searchers open on an index? To add/remove a document to the index, would all of the IndexSearchers need to be closed, or is this safe to do? The simple app I'm trying to write allows for the searching of an index through a turbine webapp interface as well as the ability to upload a document through the webapp to be added to the index. If the document exists in the index it's deleted and then the new version is added. If anyone's already done this feel free to share;) And while you're in a charitable mood, my next step is to take the Lucene service and make it an XMLRPC webservice. Thoughts and suggestions on that idea are greatly appreciated. Thanks, Seth -Original Message- From: Kelvin Tan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 7:16 PM To: Lucene Users List Subject: Re: Lucene Turbine Service Yep. Look in Lucene Sandbox. Interesting you should ask, though, because after about a year of using the LuceneSearchService, I've recently refactored it out into a subsystem of its own...:-) Regards, Kelvin The book giving manifesto - http://how.to/sharethisbook On Tue, 21 Jan 2003 18:44:33 -0500, Seth Weiner said: Hi, I'm fairly new to Lucene and am trying to create a 'simple' Turbine webapp that will use Lucene for some indexing. Has anyone written a simple Turbine/Fulcrum Lucene service for searching and indexing documents? Thanks, Seth Weiner -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Lucene Turbine Service
Thanks for the pointer! Might I ask what the motivation for the refactoring was? On a separate note I just took a look at the service in the sandbox. It doesn't appear to support addition of documents to the index. Shouldn't be hard to add, just seems like a strange ommision. Also, wouldn't it be more efficient for the service to maintain a pool of IndexSearchers rather than creating a new one for each search? Or is there a problem with holding one or more index searchers open on an index? To add/remove a document to the index, would all of the IndexSearchers need to be closed, or is this safe to do? The simple app I'm trying to write allows for the searching of an index through a turbine webapp interface as well as the ability to upload a document through the webapp to be added to the index. If the document exists in the index it's deleted and then the new version is added. If anyone's already done this feel free to share;) And while you're in a charitable mood, my next step is to take the Lucene service and make it an XMLRPC webservice. Thoughts and suggestions on that idea are greatly appreciated. Thanks, Seth -Original Message- From: Kelvin Tan [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 21, 2003 7:16 PM To: Lucene Users List Subject: Re: Lucene Turbine Service Yep. Look in Lucene Sandbox. Interesting you should ask, though, because after about a year of using the LuceneSearchService, I've recently refactored it out into a subsystem of its own...:-) Regards, Kelvin The book giving manifesto - http://how.to/sharethisbook On Tue, 21 Jan 2003 18:44:33 -0500, Seth Weiner said: Hi, I'm fairly new to Lucene and am trying to create a 'simple' Turbine webapp that will use Lucene for some indexing. Has anyone written a simple Turbine/Fulcrum Lucene service for searching and indexing documents? Thanks, Seth Weiner -- To unsubscribe, e-mail: mailto:lucene-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:lucene-user- [EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
