From: Guillermo B. <gb...@5d...> - 2005-09-27 22:57:28
|
I am trying to range index a collection in an eXist Database, snapshot = 20050805, using the following xconf file: <?xml version=3D"1.0" encoding=3D"UTF-8"?> <collection xmlns=3D"http://exist-db.org/collection-config/1.0"> <index> <fulltext default=3D"none" attributes=3D"false" = alphanum=3D"false"/> <create path=3D"//MyElement/@id" type=3D"xs:string"/> <create path=3D"//MyElement/@firstName" type=3D"xs:string"/> <create path=3D"//MyElement/@lastName" type=3D"xs:string"/> </index> </collection> When I try reindexing the log shows that the xconf file was actually = parsed and that the reindexing was under way: 2005-09-27 16:44:26,343 [http-80-Processor3] DEBUG (RpcConnection.java = [parse]:1162) - parsing = /db/system/config/db/data/myCollection/myCollection.xconf took 15ms. 2005-09-27 16:44:37,562 [http-80-Processor13] DEBUG (NativeBroker.java = [reindex]:1854) - Reindexing collection /db/data/myCollection Unfortunately, the log does not show any signs that the collection was = actually reindexed. Furthermore, if I run an xQuery referencing one of = the "indexed" attributes I do not get any [quickNodeSetCompare] entries = in the log, and the performance time of the xQueries does not improve a = bit. At first I thought the index-path of my xconf file was incorrect, but, = when I changed the "type" attribute from "xs:string" to "xs:double", I = got the following warning message: 2005-09-27 16:24:32,281 [http-80-Processor3] WARN = (NativeValueIndex.java [convertToAtomic]:723) - The specified type: = 'xs:double' and value 'JACKELYN' cannot be used as index key. It is null = or does not implement interface Indexable. 2005-09-27 16:24:32,281 [http-80-Processor3] WARN = (NativeValueIndex.java [convertToAtomic]:718) - Node value: = 'JGODFREY555' cannot be converted to type xs:double This clearly indicated the indexing was trying to take place on the = right attribute and that the indexing went through all the resources of = the collection. I find this error extremely strange because I performed the same = indexing on the same collection placed on the previous snapshot of eXist = and everything went well. =20 Any help would be grately appreciatted. Guillermo Barreiro |