Hi Heikki and developers,
I changed some codes and it caused the index rebuilding. I checked out a
latest version and re-run the harvest without my modification. Now it works
Thanks and best regards,
On Fri, Jun 7, 2013 at 9:51 AM, heikki <tropicano@...> wrote:
> yes, the category is missing, but you can just add it, then it should work.
> Lucene does not have some limit to the index (and neither does GeoNetwork
> constrain this somehow).
> When you re-start GeoNetwork, are you sure that nothing happened to the
> database, so all records are still there, and without updates ? And are you
> sure that the Lucene index is preserved correctly between stopping and
> restarting ?
> About the second problem, of retrieving more metadata in harvesting than
> ends up being searcheable, this might be caused e.g. when returned metadata
> is so malformed that GeoNetwork can't make sense of it; or if there is a
> character encoding problem, I believe; this kind of thing.
> Maybe try setting DEBUG log level for everything, and then see if you can
> find out what's happening ?
> On Fri, Jun 7, 2013 at 3:18 PM, Kai Liu <kliu.gis@...> wrote:
>> Hi Heikki,
>> I am sure that the index was rebuilt. When I sent Getrecords to the
>> geonetwork, it shows
>> <ows:ExceptionReport version="1.0.0" xsi:schemaLocation="
>> Catalog is indexing records, retry
>> If I search records in the interface, the number is increasing: 25, 60,
>> 213......... , and the files in webapps/geonetw
>> ork/WEB-INF/data/index/index/eng are new files, their size are increasing
>> I have another problem, when I havested a catalogue which has more than
>> 10000 records. It showes 10000 recordes has been added, but only about 5600
>> records was indexed and can be searched. I wonder if lucene has a limit to
>> build index in current version.
>> By the way, there is not category geonetwork.datamanager, in
>> Thanks and best regards,
>> Kai Liu
>> On Jun 6, 2013, at 19:18, heikki <tropicano@...> wrote:
>> hi Kai,
>> are you sure that the whole index is rebuilt ? What should happen is that
>> GeoNetwork compares the changeDate column for each metadata in the DB, to
>> the last change date recorded in the Lucene index. Only md that are
>> modified after they were last indexed are actually re-indexed.
>> You can check what happens if you set DEBUG log level for category
>> geonetwork.datamanager, in WEB-INF/log4j.cfg.
>> Kind regards
>> Heikki Doeleman
>> On Thu, Jun 6, 2013 at 8:33 PM, Kai Liu <kliu.gis@...> wrote:
>>> Hi all,
>>> I am using the latest geonetwork and hosting more than 100, 000 records.
>>> But now I have a problem: the geonetwork rebuilds index when I restart
>>> application. It lasts hours to rebuild the index and the number of
>>> users can get change when the geonetwork rebuilds index. It means users
>>> can't get exact search results during geontwork rebuilds index. I wonder
>>> there a way to disable lucene index rebuild on geonetwork startup.
>>> Thanks and best regards,
>>> Kai Liu
>>> How ServiceNow helps IT people transform IT departments:
>>> 1. A cloud service to automate IT design, transition and operations
>>> 2. Dashboards that offer high-level views of enterprise services
>>> 3. A single system of record for all IT processes
>>> GeoNetwork-users mailing list
>>> GeoNetwork OpenSource is maintained at