Lucene's storing functionality is just a simple storage mechanism. You
can certainly and easily use your own storage mechanism. When you get
your user created id back from Lucene due to a hit, just pass that id to
your storage system to get the original text and then feed that to the
Highlighter. Your storage system/code might be slower than Lucene, but I
don't believe there is anything about Lucene's system that would give it
an inside advantage.
- Mark
Michael J. Prichard wrote:
Hello Folks,
I wanted to stay away from storing text in the indexes in order to
keep them smaller. I have a requirement now though to provide
highlighting and, more so, fragments of the content so they will be
displayed on the UI.
Do you all prefer to store the text in the index to make this easier
or would you suggest retrieving the text from the source after doing
your search. From I can tell you need to run through the Hits anyway....
I am trying to keep the indexes as small as possible (they are still
HUGE...but...) so storing fields is not really what I want to do. I
will if it is the best and most efficient way to do so.
Thanks,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
