Page Comparison

...

If fact the range expansion is more complex than that and can handle a wide range of different formats, including some of the following examples:

Number range expansion is automatic and does not require any changes to the index definition to be enabled, which also means that at the moment it can't be disabled, but that may change in the future.

Stop words

Lucene, the document search technology behind the Weave index search, uses a pre-defined list of “stop words”. Stop words typically include common words like "the," "and," "in," "is," and so on, which appear frequently in a language but don't carry significant meaning on their own. As of Weave 2.6.9 stop words are no longer used when building a index, this was done because stop words are generally useful when indexing large pieces of text, whereas Weave indexes are created on small pieces of text and the stop words should be included.

To restore the previous list of stop words, or set your own, you can create an new configuration item that lists the available stop words that should be used, e.g.

<?xml version="1.0" encoding="UTF-8"?>

<config xmlns="urn:com.cohga.server.config#1.0" xmlns:index="urn:com.cohga.server.index#1.0">
        <index:stopwords>
                <stopword>a</stopword>
                <stopword>an</stopword>
                <stopword>and</stopword>
                <stopword>are</stopword>
                <stopword>as</stopword>
                <stopword>at</stopword>
                <stopword>be</stopword>
                <stopword>but</stopword>
                <stopword>by</stopword>
                <stopword>for</stopword>
                <stopword>if</stopword>
                <stopword>in</stopword>
                <stopword>into</stopword>
                <stopword>is</stopword>
                <stopword>it</stopword>
                <stopword>no</stopword>
                <stopword>not</stopword>
                <stopword>of</stopword>
                <stopword>on</stopword>
                <stopword>or</stopword>
                <stopword>such</stopword>
                <stopword>that</stopword>
                <stopword>the</stopword>
                <stopword>their</stopword>
                <stopword>then</stopword>
                <stopword>there</stopword>
                <stopword>these</stopword>
                <stopword>they</stopword>
                <stopword>this</stopword>
                <stopword>to</stopword>
                <stopword>was</stopword>
                <stopword>will</stopword>
                <stopword>with</stopword>
        </index:stopwords>
</config>

Scheduling Updates

Because the index is built from the data that's available at the time it's built it may become stale over time and require rebuilding. This can be done manually at the OSGi console, (more on that later) or set up in the index definition using a schedule defined using a format similar to the Cron format.

By adding a schedule tag you can indicate to Weave when the index can be rebuilt down to the millisecond, and have it rebuilt at certain times each day or on certain days of the week (or a combination of these).

^*It appears that using * for the day of the week or the day of the month may cause issues (like the index continually being built).

...

The indexing in Weave provides a number of commands that can be used at the OSGi prompt to work with the indexes.

<> substitute, [] = optional, | alternate

...