vgritsenko2004/02/18 18:44:43
Modified:java/src/org/apache/xindice/server/rpc/messages Query.java
Log:
Make method static
Revision ChangesPath
1.10 +7 -7
xml-xindice/java/src/org/apache/xindice/server/rpc/messages/Query.java
Index: Query.java
===
vgritsenko2004/02/18 18:45:37
Modified:java/src/org/apache/xindice/client/xmldb
ResourceSetImpl.java
Log:
Use defined constant for the "key" attribute
Revision ChangesPath
1.14 +3 -4
xml-xindice/java/src/org/apache/xindice/client/xmldb/R
vgritsenko2004/02/18 18:46:28
Modified:java/src/org/apache/xindice/client/xmldb
XindiceCollection.java
Log:
Remove duplicate NS declaration, reference constant in NodeSource
Revision ChangesPath
1.18 +4 -3
xml-xindice/java/src/org/apache
vgritsenko2004/02/18 18:50:44
Modified:java/src/org/apache/xindice/client/xmldb/embed
CollectionImpl.java
Log:
Add check on null/empty collection name
Revision ChangesPath
1.32 +11 -4
xml-xindice/java/src/org/apache/xindice/client/xmldb/e
vgritsenko2004/02/18 18:51:35
Modified:java/src/org/apache/xindice/client/xmldb/services
XUpdateQueryServiceImpl.java
Log:
formatting
Revision ChangesPath
1.12 +4 -5
xml-xindice/java/src/org/apache/xindice/client/xmldb/services/XUpdateQu
vgritsenko2004/02/18 19:05:15
Modified:java/src/org/apache/xindice/client/xmldb/xmlrpc
CollectionImpl.java
java/src/org/apache/xindice/core FaultCodes.java
java/src/org/apache/xindice/server/rpc
RPCDefaultMessa
vgritsenko2004/02/18 19:06:44
Modified:java/src/org/apache/xindice/server/rpc/messages
RemoveCollection.java
Log:
Exception handling: throw XMLDB exception when necessary.
Revision ChangesPath
1.10 +25 -21
xml-xindice/java/src/org/apache/x
vgritsenko2004/02/18 19:29:01
Modified:java/tests/src/org/apache/xindice/integration/client/basic
CollectionTest.java
java/tests/src/org/apache/xindice/integration/client/services
IndexedSearchTest.java
Log:
tests improve
vgritsenko2004/02/19 05:14:26
Modified:java/src/org/apache/xindice/client/xmldb DatabaseImpl.java
java/src/org/apache/xindice/client/xmldb/xmlrpc
CollectionImpl.java
Log:
Improving exception handling
Revision ChangesPath
1.27 +3
I'm currently attempting to add a Lucene based full text indexer to
Xindice 1.1b3. A Lucene index needs to be explicitly closed but it seems
that, certainly in embedded mode, an indexer's close() method never gets
called so I don't get to close my Lucene index. It'll be fairly simple
to add I t
I've written a full text indexer that builds a Lucene index. That all
seems to work fine. Now the hard part: what should the API be for
querying the index? I can't find a spec for XPath full text queries
although there is this document:
http://www.w3.org/TR/2003/WD-xquery-full-text-requirements
I assume your indexer only indexes "whole words" (perhps with stemming)
and therefore would not be useful in assisting evaluation of the
"contains" or "ends-with" functions (as a substring
index would be useful for)?
e.g.
if the text was: "some words"
contains("some words", "wor") would return true
Terry Rosenbaum wrote:
I assume your indexer only indexes "whole words" (perhps with stemming)
and therefore would not be useful in assisting evaluation of the
"contains" or "ends-with" functions (as a substring
index would be useful for)?
e.g.
if the text was: "some words"
contains("some words", "
Andy Armstrong wrote:
You can provide Lucene with different Analyzers[1] which determine how
the text stream is handled so you could do what you want. I haven't
decided the best way to allow the creator of the index to specify the
Analyzer chain yet but I will make it possible to control which
Isn't there a contains() function in XPath 2.0?
In Tamino's xpath-1.0-like query language they use ~= for a
fulltext "contains", as in
/document/section[objective~="develop"] (find all document
sections whose objective contains the word "develop").
I'm not suggesting you copy Tamino extensions to
[EMAIL PROTECTED] wrote:
Isn't there a contains() function in XPath 2.0?
There may be - to my shame I haven't read the spec in detail.
In Tamino's xpath-1.0-like query language they use ~= for a
fulltext "contains", as in
/document/section[objective~="develop"] (find all document
sections whose obj
There is a contains function in xpath 1.0 as well
--snip from spec
Function: boolean contains(string, string)
The contains function returns true if the first argument string contains
the second argument string, and otherwise returns false.
> > I'm not suggesting you copy Tamino extensions
Been looking forward to a lucene integration into xindice.
Not quite on our need now list, but probably only a few months away.
Kind of a dumb question...
Does lucene support incremental additions without a full index rebuild?
Cheers, Gary
--
G
18 matches
Mail list logo