I believe that Java 1.4 and 1.5 can serialize and deserialize objects
directly to XML. Therefore you can store the XML directly into Lucene
as an unindexed field. You could also use one of the XML analyzers to
parse and index the fields.
On 8/25/05, Kevin L. Cobb <[EMAIL PROTECTED]> wrote:
> I jus
>> but I'm still lost on how to convert
> everything to SpanQuery
> variants.
See the QuerySpansExtractor I linked to here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=35518
This uses SpanTermQuery for individual TermQuerys. As
for all of the other query types eg fuzzy, prefix,
range etc th
Based on this discussion, I've gone back and re-read everything
in LIA on SpanQuery, etc.
Isn't this just another manifestation of the same problem? How
do I reliably, correctly convert an arbitrary lucene query into its
equivalent SpanQuery?
Here's one, for example:
+text:"jurassic barnea" +au
Hi,
I don't think by default it does so. But, you can certainly serialize
the java object and use base 64 to encode it into a text string, then,
you can store it as a field.
Cheers,
Jian
On 8/25/05, Kevin L. Cobb <[EMAIL PROTECTED]> wrote:
> I just had a thought this morning. Does Lucene have t
I just had a thought this morning. Does Lucene have the ability to store
Serialized Java Objects for return during a search. I was thinking that
this would be a nifty way to package up all of the return values for a
search. Of course, I wouldn't expect the serialized objects would not be
searchable
On 8/24/05, Monsur Hossain <[EMAIL PROTECTED]> wrote:
>
> Otis, we've been continually impressed with the performance of Lucene.
> We've been ever increasing the load we are putting on it (from our small
> help section, to our slightly larger metros, to our big groups, and then
> our gigantic webl
Unfortunately I've not had the time to address the
phrase highlighting issues in the current highlighter
but I think I've an idea as to how best to fix it:
I would suggest rewriting the highlighter to use Spans
not Terms to find the relevant sections in a text.
Most of the code required for such a
You can also use the
PerFieldAnalyzerWrapper to search in KeywordFields using QueryParser.
Best,
Martin
Vanlerberghe, Luc wrote:
Is your Analyzer aware that that particular field does not need to be
tokenized?
During indexation, if a field is passed that is passed as
tokenize=false, the ana
Is your Analyzer aware that that particular field does not need to be
tokenized?
During indexation, if a field is passed that is passed as
tokenize=false, the analyzer won't be called so the string will be
stored as-is.
During searching, the queryparser doesn't know which fields should be
tokeniz
Hi,
on our setup, we are using two completely separated processes, one to
search and another to highlight the found documents. Both this
processes are used by other applications through xml-rpc calls.
Our index is used to search the content of an Oracle DB; for this
reason, there are no stored fi
On Thursday 25 August 2005 04:47, Fred Toth wrote:
> All,
>
> First, my thanks to those who've contributed to the current
> best practices for highlighting. We use your code!
>
> However, after reviewing recent discussions about highlighting,
> and struggling with our own highlighting issues, I'm
11 matches
Mail list logo
