On 23.03.2012, at 13:06, Michel Benevento wrote:
> Hi,
>
> I have been working on importing a SKOS file as a custom vocabulary, with
> reasonable success so far. This involves quite a few steps and some hail mary
> restarts, so I have a couple of questions about it. I have read and
> successfully performed the initial steps described here:
> http://incubator.apache.org/stanbol/docs/trunk/customvocabulary.html.
>
> Questions:
> - what exactly are the required steps for reloading a custom index? Do I just
> replace the solrindex.zip in /sling/datafiles ?
> - is it necessary to update the bundle jar each time I generate a new index?
> - if so, how do I increase the version of the generated jar?
>
This depends on the settings for the "Synchronized" property within the
"{indexing-root}/indexing/config/indexing.property" file.
Here are the comments for that property
# The "Synchronized" property is supported by some Entityhub Yard
implementations
# to automatically update/delete local data as soon as the created archive
with
# the indexed data is updated/deleted in the /datafiles folder of Apache
Stanbol
# By default this feature is activated. For very big indexes users might
want to
# disable this feature to allow the deletion of the archive after the index
was
# initialised successfully.
# By default this feature is enabled. Uncommend the next line to deactivate
it.
#Synchronized=false
So if you have not set this to "true" than the only thing required is to
{name} … refers to the name of your index
1. delete the old "{name}.solrindex.zip" in "{stanbol-home}/sling/datafiles"
2. wait for at least 5sec
3. copy the new version
4. wait until the new index is loaded and initialized (depends on the size)
The second point is important, because the background thread only checks every
5sec if a file was removed/added.
If synchronized=false you will need to
1. stop the bundle (this should cause the current index to be deleted)
* you can validate this by checking the
"{stanbol-home}/sling/indexing/default" for a sub-folder starting with {name}.
2. copy the new version of the index to "{stanbol-home}/sling/datafiles"
3. start the bundle
4. wait until the new index is loaded and initialized
regarding
> - is it necessary to update the bundle jar each time I generate a new index?
> - if so, how do I increase the version of the generated jar?
The versioning system of bundles is not used in this case.
best
Rupert
> Thanks,
> Michel
>
