...
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 setup 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, have it rebuilt at certain times each day or on certain days of the week (or a combination of these).
| Unit | Range |
|---|---|
| milliseconds | 0-999 |
| seconds | 0-59 |
| minutes | 0-59 |
| hours | 0-23 |
| day of week | 1-7 (sunday-saturday) |
| day of month | 1-31 |
| month | 1-12 |
Schedule | Description |
0 0 30 2 | will run at 2:30am each day |
0 0 30 2,14 | will run at 2:30am and 2:30pm each day |
0 0 30 2,8,14,20 | will run at 2:30am, 8:30am, 2:30pm and 8:30pm each day |
0 0 30 2 13 | will run at 2:30am each MondayTuesday |
0 0 30 2 * 1 | will run at 2:30am on the first of each month |
0 0 30 2 * 1 2 | will run at 2:30am on the first of February each year |
0 0 30 2 5 * 2 | will run at 2:30am on each Thursday of February each year |
0 0 30 2 5 4 1 2 | will run at 2:30am on each Thursday Wednesday and on the first of February each year |
0 0 15,45 | will run every half hour at quarter past and quarter to |
...