[Exist-open] Lucene elements in collection.xconf causing odd logging errors

[Joe W. <jo...@gm...>]

Hi all,

In working through some questions I had about indexing, I noticed
something strange in the logs.  It appears that collection.xconf files
that contain lucene elements are generating errors.  Using a vanilla
build of 1.5dev (rev. 11020; I did a 'build clean', SVN Update, then
'build'), I loaded the example files (localhost:8080/exist/admin >
Examples Setup > the 'eXist-db shipped files' option).  The next time
I restart the database, I get the following errors (note: I've turned
trace logging on):

17 Jan 2010 17:22:54,166 [main] TRACE
(CollectionConfigurationManager.java [loadConfiguration]:231) -
Reading collection configuration from
'/db/system/config/db/shakespeare/collection.xconf'
17 Jan 2010 17:22:54,168 [main] INFO  (IndexSpec.java [read]:115) -
Unable to process index configuration element :lucene
17 Jan 2010 17:22:54,169 [main] INFO  (IndexSpec.java [read]:115) -
Unable to process index configuration element :ngram
17 Jan 2010 17:22:54,169 [main] DEBUG (LuceneIndexWorker.java
[configure]:97) - Configuring lucene index
17 Jan 2010 17:22:54,174 [main] DEBUG (DOMFile.java [findValue]:1359)
- Node 1.3.2.1.3 could not be found. Giving up.
17 Jan 2010 17:22:54,174 [main] DEBUG (NativeBroker.java [start]:3069)
- Node 1.3.2.1.3 not found
17 Jan 2010 17:22:54,175 [main] TRACE (NGramIndexWorker.java
[configure]:151) - NGram index defined on SPEAKER
17 Jan 2010 17:22:54,177 [main] TRACE
(CollectionConfigurationManager.java [loadConfiguration]:231) -
Reading collection configuration from
'/db/system/config/db/mondial/mondial.xconf'
17 Jan 2010 17:22:54,178 [main] DEBUG (CollectionConfiguration.java
[read]:229) - /db/system/config/db/mondial : Validation mode=auto
17 Jan 2010 17:22:54,195 [main] DEBUG (LuceneIndexWorker.java
[configure]:97) - Configuring lucene index
17 Jan 2010 17:22:54,196 [main] TRACE
(CollectionConfigurationManager.java [loadConfiguration]:231) -
Reading collection configuration from
'/db/system/config/db/mods/collection.xconf'
17 Jan 2010 17:22:54,292 [main] DEBUG (LuceneIndexWorker.java
[configure]:97) - Configuring lucene index
17 Jan 2010 17:22:54,293 [main] TRACE
(CollectionConfigurationManager.java [loadConfiguration]:231) -
Reading collection configuration from
'/db/system/config/db/xmlad/acronyms.xconf'
17 Jan 2010 17:22:54,293 [main] INFO  (IndexSpec.java [read]:115) -
Unable to process index configuration element :lucene
17 Jan 2010 17:22:54,294 [main] INFO  (IndexSpec.java [read]:115) -
Unable to process index configuration element :ngram
17 Jan 2010 17:22:54,294 [main] DEBUG (LuceneIndexWorker.java
[configure]:97) - Configuring lucene index
17 Jan 2010 17:22:54,295 [main] TRACE (NGramIndexWorker.java
[configure]:151) - NGram index defined on @id
17 Jan 2010 17:22:54,297 [main] DEBUG (NGramIndex.java [sync]:86) - SYNC NGRAM

Notice that the "Unable to process index configuration element"
messages only appear in cases when the collection.xconf files contain
a lucene element (Shakespeare and Acronyms).

1. Is this "Unable to process index configuration element" message
anything to be concerned about?

2. What does it mean that "Node 1.3.2.1.3 could not be found"?  Is
this anything to be concerned about?

Thanks,
Joe