mirror of https://github.com/apache/lucene.git
Updated my bio, since I'm no longer at Grand Central.
Added a missing tag in lucenesandbox.xml that broke Anakia. Rebuilt out-of-date docs. git-svn-id: https://svn.apache.org/repos/asf/lucene/java/trunk@149772 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Cutting
parent
2ef3150b70
commit
ce605b9a08
|
|
@ -194,10 +194,7 @@ Tomcat. </p>
|
|||
From your Tomcat directory look in the webapps/luceneweb subdirectory. If its not
|
||||
present, try browsing to "http://localhost:8080/luceneweb" then look again.
|
||||
Edit a file called configuration.jsp. Ensure that the indexLocation is equal to the
|
||||
location you used for your index. Note that if you are using a
|
||||
Windows OS, you will need to escape backslashes. For example, the indexLocation may look
|
||||
something like "c:\\dev\\lucene-index".
|
||||
You may also customize the appTitle and appFooter
|
||||
location you used for your index. You may also customize the appTitle and appFooter
|
||||
strings as you see fit. Once you have finsihed altering the configuration you should
|
||||
restart Tomcat. You may also wish to update the war file by typing
|
||||
<b>jar -uf luceneweb.war configuration.jsp</b> from the luceneweb subdirectory.
|
||||
|
|
|
|||
|
|
@ -59,24 +59,22 @@
|
|||
<p><strong>Resources</strong></p>
|
||||
<ul>
|
||||
<li> <a href="http://lucene.sourceforge.net/cgi-bin/faq/faqmanager.cgi">FAQ (Official)</a>
|
||||
</li>
|
||||
<li> <a href="http://www.jguru.com/faq/Lucene">JGuru FAQ</a>
|
||||
</li>
|
||||
<li> <a href="./gettingstarted.html">Getting Started</a>
|
||||
</li>
|
||||
<li> <a href="http://www.jguru.com/faq/Lucene">JGuru FAQ</a>
|
||||
</li>
|
||||
<li> <a href="http://jakarta.apache.org/site/bugs.html">Bugs</a>
|
||||
</li>
|
||||
<li> <a href="http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=Lucene&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=%27Importance%27">Lucene Bugs</a>
|
||||
</li>
|
||||
<li> <a href="./resources.html">Articles</a>
|
||||
</li>
|
||||
<li> <a href="./queryparsersyntax.html">Query Syntax</a>
|
||||
</li>
|
||||
<li> <a href="./api/index.html">Javadoc API</a>
|
||||
<li> <a href="./api/index.html">Javadoc</a>
|
||||
</li>
|
||||
<li> <a href="./contributions.html">Contributions</a>
|
||||
</li>
|
||||
<li> <a href="./lucenesandbox.html">Lucene Sandbox</a>
|
||||
</li>
|
||||
<li> <a href="./resources.html">Articles</a>
|
||||
</li>
|
||||
</ul>
|
||||
<p><strong>Plans</strong></p>
|
||||
|
|
@ -191,3 +189,23 @@ developed in an open and cooperative fashion.
|
|||
</body>
|
||||
</html>
|
||||
<!-- end the processing -->
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -115,8 +115,8 @@
|
|||
The best reference is <a href="http://www.htdig.org">
|
||||
htDig</a>, though it is not quite as sophisticated as
|
||||
Lucene, it has a number of features that make it
|
||||
desireable. It however is a traditional c-compiled app
|
||||
which makes it somewhat unpleasent to install on some
|
||||
desirable. It however is a traditional c-compiled app
|
||||
which makes it somewhat unpleasant to install on some
|
||||
platforms (like Solaris!).
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -129,7 +129,7 @@
|
|||
with others.
|
||||
</p>
|
||||
<p>
|
||||
While I'm outlaying a fairly large featureset, these can
|
||||
While I'm outlaying a fairly large feature set, these can
|
||||
be implemented incrementally of course (and are probably
|
||||
best if done that way).
|
||||
</p>
|
||||
|
|
@ -148,9 +148,9 @@
|
|||
<blockquote>
|
||||
<p>
|
||||
The goal is to provide features to Lucene that allow it
|
||||
to be used as a dropin search engine. It should provide
|
||||
to be used as a drop-in search engine. It should provide
|
||||
many of the features of projects like <a href="http://www.htdig.org">htDig</a> while surpassing
|
||||
them with unique Lucene features and capabillities such as
|
||||
them with unique Lucene features and capabilities such as
|
||||
easy installation on and java-supporting platform,
|
||||
and support for document fields and field searches. And
|
||||
of course, <a href="http://apache.org/LICENSE">
|
||||
|
|
@ -159,11 +159,11 @@
|
|||
<p>
|
||||
To reach this goal we'll implement code to support the
|
||||
following objectives that augment but do not replace
|
||||
the current Lucene featureset.
|
||||
the current Lucene feature set.
|
||||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
Document Location Independance - meaning mapping
|
||||
Document Location Independence - meaning mapping
|
||||
real contexts to runtime contexts.
|
||||
Essentially, if the document is at
|
||||
/var/www/htdocs/mydoc.html, I probably want it
|
||||
|
|
@ -176,21 +176,21 @@
|
|||
many environments than is *remote* indexing (for
|
||||
instance http). I would suggest that most folks
|
||||
would prefer that general functionality be
|
||||
suppored by Lucene instead of having to write
|
||||
supported by Lucene instead of having to write
|
||||
code for every indexing project. Obviously, if
|
||||
what they are doing is *special* they'll have to
|
||||
code, but general document indexing accross
|
||||
webservers would not qualify.
|
||||
code, but general document indexing across
|
||||
web servers would not qualify.
|
||||
</li>
|
||||
<li>
|
||||
Document interperatation abstraction - currently
|
||||
Document interpretation abstraction - currently
|
||||
one must handle document object construction via
|
||||
custom code. A standard interface for plugging
|
||||
in format handlers should be supported.
|
||||
</li>
|
||||
<li>
|
||||
Mime and file-extension to document
|
||||
interperatation mapping.
|
||||
interpretation mapping.
|
||||
</li>
|
||||
</ul>
|
||||
</blockquote>
|
||||
|
|
@ -241,7 +241,7 @@
|
|||
</li>
|
||||
<li>
|
||||
replacement type - the type of
|
||||
replacewith path: relative, url or
|
||||
replace with path: relative, URL or
|
||||
path.
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -277,7 +277,7 @@
|
|||
</li>
|
||||
<li>
|
||||
IncludeFilter - include only items
|
||||
matching filter. (can occur mulitple
|
||||
matching filter. (can occur multiple
|
||||
times)
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -311,7 +311,7 @@
|
|||
it. Command line options override
|
||||
the properties file in the case of
|
||||
duplicates. There should also be an
|
||||
enivironment variable or VM parameter to
|
||||
environment variable or VM parameter to
|
||||
set this.
|
||||
</li>
|
||||
</ul>
|
||||
|
|
@ -320,8 +320,8 @@
|
|||
</p>
|
||||
<p>
|
||||
This should extend the AbstractCrawler and
|
||||
support any addtional options required for a
|
||||
filesystem index.
|
||||
support any additional options required for a
|
||||
file system index.
|
||||
</p>
|
||||
<p>
|
||||
<b>HTTP Crawler </b>
|
||||
|
|
@ -331,7 +331,7 @@
|
|||
</p>
|
||||
<ul>
|
||||
<li>
|
||||
span hosts - Wheter to span hosts or not,
|
||||
span hosts - Whether to span hosts or not,
|
||||
by default this should be no.
|
||||
</li>
|
||||
<li>
|
||||
|
|
@ -346,11 +346,11 @@
|
|||
recurse and go to
|
||||
/nextcontext/index.html this option says
|
||||
to also try /nextcontext to get the dir
|
||||
lsiting)
|
||||
listing)
|
||||
</li>
|
||||
<li>
|
||||
map extensions -
|
||||
(always/default/never/fallback). Wether
|
||||
(always/default/never/fallback). Whether
|
||||
to always use extension mapping, by
|
||||
default (fallback to mime type), NEVER
|
||||
or fallback if mime is not available
|
||||
|
|
@ -376,7 +376,7 @@
|
|||
<blockquote>
|
||||
<p>
|
||||
A configurable registry of document types, their
|
||||
description, an identifyer, mime-type and file
|
||||
description, an identifier, mime-type and file
|
||||
extension. This should map both MIME -> factory
|
||||
and extension -> factory.
|
||||
</p>
|
||||
|
|
@ -500,13 +500,13 @@
|
|||
<tr><td>
|
||||
<blockquote>
|
||||
<p>
|
||||
A class taht maps standard fields from the
|
||||
A class that maps standard fields from the
|
||||
DocumentFactories into *fields* in the Document objects
|
||||
they create. I suggest that a regular expression system
|
||||
or xpath might be the most universal way to do this.
|
||||
For instance if perhaps I had an XML factory that
|
||||
represented XML elements as fields, I could map content
|
||||
from particular fields to ther fields or supress them
|
||||
from particular fields to their fields or suppress them
|
||||
entirely. We could even make this configurable.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -568,7 +568,7 @@
|
|||
While this goes slightly beyond what HTDig provides by
|
||||
providing field mapping (where HTDIG is just interested
|
||||
in Strings/numbers wherever they are found), it provides
|
||||
at least what I would need to use this as a dropin for
|
||||
at least what I would need to use this as a drop-in for
|
||||
most places I contract at (with the obvious exception of
|
||||
a default set of content handlers which would of course
|
||||
develop naturally over time).
|
||||
|
|
|
|||
|
|
@ -106,7 +106,11 @@
|
|||
</td></tr>
|
||||
<tr><td>
|
||||
<blockquote>
|
||||
</blockquote>
|
||||
<P>
|
||||
You can access Lucene Sandbox CVS repository at
|
||||
<A HREF="http://cvs.apache.org/viewcvs/jakarta-lucene-sandbox/">http://cvs.apache.org/viewcvs/jakarta-lucene-sandbox/</A>.
|
||||
</P>
|
||||
</blockquote>
|
||||
</p>
|
||||
</td></tr>
|
||||
<tr><td><br/></td></tr>
|
||||
|
|
|
|||
|
|
@ -131,11 +131,10 @@ Palo Alto Research Center (PARC), Apple, and Excite@Home, and authored
|
|||
several information retrieval <a href="http://lucene.sourceforge.net/publications.html">papers and
|
||||
patents</a>.</p>
|
||||
|
||||
<p>Doug currently works for <a href="http://www.grandcentral.com/">Grand
|
||||
Central</a>.</p>
|
||||
|
||||
<p>Please do not email Doug directly about Lucene. Instead use
|
||||
the <a href="http://jakarta.apache.org/site/mail.html">Jakarta-Lucene mailing lists</a>.</p>
|
||||
<p>Recently Doug has worked on peer-to-peer search at Infrasearch
|
||||
(aquired by Sun's JXTA project) and on web services at Grand Central.
|
||||
Currently he continues to help develop Lucene and is available for
|
||||
contract work.</p>
|
||||
|
||||
</li>
|
||||
<li><b>Otis Gospodnetic</b> (otis at apache.org)</li>
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ not necessarily be maintained, particularly in their current state.
|
|||
<P>
|
||||
You can access Lucene Sandbox CVS repository at
|
||||
<A HREF="http://cvs.apache.org/viewcvs/jakarta-lucene-sandbox/">http://cvs.apache.org/viewcvs/jakarta-lucene-sandbox/</A>.
|
||||
|
||||
</P>
|
||||
</section>
|
||||
|
||||
</body>
|
||||
|
|
|
|||
|
|
@ -22,11 +22,10 @@ several information retrieval <a
|
|||
href="http://lucene.sourceforge.net/publications.html">papers and
|
||||
patents</a>.</p>
|
||||
|
||||
<p>Doug currently works for <a href="http://www.grandcentral.com/">Grand
|
||||
Central</a>.</p>
|
||||
|
||||
<p>Please do not email Doug directly about Lucene. Instead use
|
||||
the <a href="http://jakarta.apache.org/site/mail.html">Jakarta-Lucene mailing lists</a>.</p>
|
||||
<p>Recently Doug has worked on peer-to-peer search at Infrasearch
|
||||
(aquired by Sun's JXTA project) and on web services at Grand Central.
|
||||
Currently he continues to help develop Lucene and is available for
|
||||
contract work.</p>
|
||||
|
||||
</li>
|
||||
<li><b>Otis Gospodnetic</b> (otis at apache.org)</li>
|
||||
|
|
|
|||
Loading…
Reference in New Issue