[jsword-devel] Exception when generating new index

[Gabriel Valencia]

Didn't find a bug anywhere on this and haven't heard it reported  
here, but I'm getting an exception when I try to re-index the KJV. It  
seems to be based on the new search features with strongs, etc.:

INFO: Failed to initialise Lucene search engine.
org.crosswire.jsword.book.BookException: Failed to initialise Lucene  
search engine.
	at org.crosswire.jsword.index.lucene.LuceneIndex.<init> 
(LuceneIndex.java:182)
	at org.crosswire.jsword.index.lucene.LuceneIndexManager$1.run 
(LuceneIndexManager.java:108)
	at java.lang.Thread.run(Thread.java:613)
Caused by: java.io.IOException: Not a valid Strong's Number "H0000"
	at org.crosswire.jsword.index.lucene.StrongsNumberFilter.next 
(StrongsNumberFilter.java:71)
	at org.apache.lucene.index.DocumentWriter.invertDocument 
(DocumentWriter.java:167)
	at org.apache.lucene.index.DocumentWriter.addDocument 
(DocumentWriter.java:95)
	at org.apache.lucene.index.IndexWriter.buildSingleDocSegment 
(IndexWriter.java:706)
	at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java: 
694)
	at org.apache.lucene.index.IndexWriter.addDocument(IndexWriter.java: 
680)
	at  
org.crosswire.jsword.index.lucene.LuceneIndex.generateSearchIndexImpl 
(LuceneIndex.java:411)
	at org.crosswire.jsword.index.lucene.LuceneIndex.<init> 
(LuceneIndex.java:137)
	... 2 more

If we find bugs from nightly builds, should we go ahead and report  
them? Not sure if this qualifies as a BD bug or if it has to do with  
the module.
--
Gabriel Valencia
<gee4vee at mac.com>
Are you a GOOD person? Take this test to find out! http:// 
www.wayofthemaster.com/goodperson.shtml


On May 6, 2007, at 12:00 PM, jsword-devel-request at crosswire.org wrote:

> Send jsword-devel mailing list submissions to
> 	jsword-devel at crosswire.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://www.crosswire.org/mailman/listinfo/jsword-devel
> or, via email, send a message with subject or body 'help' to
> 	jsword-devel-request at crosswire.org
>
> You can reach the person managing the list at
> 	jsword-devel-owner at crosswire.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of jsword-devel digest..."
>
>
> Today's Topics:
>
>    1. Changes to JSword (DM Smith)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 6 May 2007 12:28:25 -0400
> From: DM Smith <dmsmith555 at yahoo.com>
> Subject: [jsword-devel] Changes to JSword
> To: J-Sword Developers Mailing List <jsword-devel at crosswire.org>
> Message-ID: <91815585-BDE8-44FD-A310-5B226BAFCB97 at yahoo.com>
> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
>
> Everyone,
>
> I have just made two changes to JSword:
>
> First, I have replaced URL with URI wherever possible. Unfortunately
> this is an API change. The problem is that URL depends on the state
> of the Internet to compare two URLs. That is, URL.equals(Object)
> would do name resolution. This had an unfortunate side-effect of
> blocking or inappropriately returning false when the internet was  
> flaky.
>
> Second, I have changed the index to include the ability to search
> keys, Strong's numbers and cross-references. To use these features,
> you will need to re-index your modules. The current index will work
> without these features.
>
> In Lucene, you can search for tagged terms by prefixing a term with
> its field as in:
> key:Matt.1.1
> 	Finds the verse. Note, there is only one value stored in this field
> and the argument is an OSIS ID.
>
> strong:H3068
> 	Finds all verses with the Hebrew Strong's number of 3068, or YHWH.
> Use G for Greek. The Strong's number is never prefixed by 0. Modules
> are inconsistent in how they represent Strong's numbers, but this is
> normalized.
>
> xref:Matt.1.1
> 	Finds all verses with a cross reference to Matthew 1:1. Note, the
> argument is an OSIS ID. No ranges. No normalization from a free-form
> reference to an OSIS ID.
>
>
> Some thoughts:
> Because of the inflexibility of these, I am reluctant to make the
> features generally known.
>
> key: is really dumb, but it came for free.
>
> I see a couple of uses for strong:
> First, one can find similar verses to a current verse. This would be
> done by creating a search request consisting of all the Strong's
> numbers in the verse and then doing a prioritized search for the top
> 20 verses retrieved. If the search also included the text each as
> fuzzy, it could find verses in the alternate testament.
>
> One could also tie a lookup in a Strong's dictionary to verses using
> that number. Note, one could use this technique to find verses
> against one Bible having Strong's numbers, but display the verses
> from the current Bible.
>
> For xref:
> Find related. Again, one can use this technique to find verses
> against one Bible having cross references, but display the verses
> from the current Bible.
>
> I'd love to hear feedback and your ideas!
>
> In His Service,
> 	DM Smith
>
>
>
>
> ------------------------------
>
> _______________________________________________
> jsword-devel mailing list
> jsword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/jsword-devel
>
>
> End of jsword-devel Digest, Vol 36, Issue 1
> *******************************************