lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Stephan <fast.j...@gmx.net>
Subject Indexing of virtual "made up" documents
Date Tue, 26 Apr 2005 07:21:05 GMT
Hi there,

lets see if somebody listens on this list :-D

I wonder if the following is possible with Lucene.

I would like to add documents to the index, which aren't real documents.
:-) Meaning: there is no text to parse and tokenize. What I have is a
number of features, some are simple words, some are combinations of
words. Those features classify an entity in my database.

I have also an own parser/analyzer/tokenizer which is able to take a
text and extract those features from it. (Possibly a query.)

So, I wanna do sth like (pseudo code):

   Lucene.index(myEntity.getId, myEntity.getDescriptors)

and then when a query was issued:

   List entityIds = Lucene.query(myQuery.convertToLuceneQueryLanguage)

I was looking at the source and couldn't find a possibility to get rid
of the analyzing stage to hand the features to Lucene myself.

One possibility would be to use an analyzer which only considers
whitespace as delimiter and set all descriptors as one string. This
feels suboptimal, because I have them as single tokens already and
concatenating them first, to let lucene tokenize them again,  should not
be necessary.

Also, the neighbour information isn't applicable in my scenario. It
seems you use placement of terms somehow. I don't have placement
information. Would that hurt Lucene?
I am not sure how Lucenes uses the placement information, but in the
described case where I concatenate all my features to a
whitespace-delimited text, I fear that Lucene uses the placement of
features in this made-up text and comes to some wrong conclusions (after
all, the placement is arbitrary in the "made-up" text).

Also 2, I am not sure yet, how the converter would have to look like.
After all the terms in the query have to be of the same form as those in
the index, otherwise they wouldn't match. Can I inject my own analyzer
only for the query part, so that lucene hands it phrases and lets it
build features from those phrases?

Any info is appreciated. I could maybe build my own simple index, the
analyzer is already there, but I would prefer to use a professional
solution with a good query language and some additional
nice-to-have-features.

May I use Lucene? :-)

Best wishes,
Daniel

Mime
View raw message