On 9/19/06, Brian Lucas <[EMAIL PROTECTED]> wrote:
Converting to 'integer' and deleting/reindexing fixed it. Can 'sint' be
used for the id with highlighting, or does one need to use integer or string
for that?
It should be usable (but I personally haven't tested that).
If it's not, it's a bug a
ould have changed sint to integer without deleting the
data.
-B
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Yonik Seeley
Sent: Tuesday, September 19, 2006 11:55 AM
To: solr-user@lucene.apache.org
Subject: Re: strange highlighting behavior
On 9/19
On 9/19/06, Yonik Seeley <[EMAIL PROTECTED]> wrote:
The fix would be to use
FieldType.indexedToReadable() to convert the indexed form back to a
readable form.
Oops, that should be storedToReadable since the id is obtained from
the stored fields, not from the index.
Hmmm, a quick look at the co
On 9/19/06, Brian Lucas <[EMAIL PROTECTED]> wrote:
The unusual characters on lst name="…" are what I can't figure out, as it
DEFINITELY
is not the id. I've tried indexed id with "integer", "sint", and "string" all
with the
same result.
Yes, looks like you hit a bug where you are seeing the "
I’m experiencing some unusual behavior when I perform a search with
highlighting enabled.
I’ve set up “id” as “sint” and indexed properly, but performing a search gives
the following result:
3.0647626
2
369845
1
Microsoft Reorganizes
Microsoft Reorganizes
3.0647626
