yes, no worries.
i just check in advance what fields are available and build the Sort
object accordingly. Eventually BCC would be there...but not
necessary so at first.
Anyway, got it to work! Thanks for your help.
All the best,
Michael
On Jan 8, 2008, at 4:37 PM, Doron Cohen wrote:
H
Hi Michael, I think you mean the exception thrown when you
search and sort with a field that was not yet indexed:
RuntimeException: field "BBC" does not appear to be indexed
I think the current behavior is correct, otherwise an application
might (by a bug) attempt to sort by a wrong field, th
my mistake, I thought I was looking at the solr mailing list ;)
If you change your analyzer, it does not change the tokens that are
already in the index -- you will need to re-index for any changes to
take effect.
ryan
Michael Prichard wrote:
Meaning that it says "field is not indexed". Wh
Meaning that it says "field is not indexed". Where is
sortMissingLastAttribute?
thanks.
On Jan 8, 2008, at 4:13 PM, Ryan McKinley wrote:
what do you mean by "fail"? -- there is the sortMissingLast attribute
Michael Prichard wrote:
ok... i should read the manual more often.
i went ahead a
what do you mean by "fail"? -- there is the sortMissingLast attribute
Michael Prichard wrote:
ok... i should read the manual more often.
i went ahead and just added untokenized, unstored sort fields
question, if I put a field in to sort of but say I have not indexed any
as of yet...will
ok... i should read the manual more often.
i went ahead and just added untokenized, unstored sort fields
question, if I put a field in to sort of but say I have not indexed
any as of yet...will the Sort fail? For example, say I have a BCC
field and nothing has been indexed with that yet
Is it possible to sort on a tokenized field? For example, I break
email address into pieces, i.e.
[EMAIL PROTECTED]
becomes
[EMAIL PROTECTED]
michael.prichard
michael
prichard
email.com
email
so when sorting on this field I get some strange results. Do I need
to create another field jus
: In our application we need to do this for all 20 fields. That means
: me have to create twenty redundant fields just for sorting.
: That's really an overhead in size and indexing-time.
I guess it just depends on the size of your index and how fast is "fast
enough" when indexing ... most people
Hi Chris,
sure, you can create an addional field for every field that should
support sorting.
In our application we need to do this for all 20 fields. That means
me have to create twenty redundant fields just for sorting.
That's really an overhead in size and indexing-time.
:: using the stored
: for years there is the discussion to make lucene able to sort on TOKENIZED
: fields.
really? .. i've only been on the list since 1.4.3 but i don't remember it
being much of a recurring topic.
: (e.g. if more then one term is available concatenate the tokens OR use the
: stored value for sortin
Hello,
for years there is the discussion to make lucene able to sort on TOKENIZED
fields.
(e.g. if more then one term is available concatenate the tokens OR use the
stored value for sorting).
Could some of the developer please make a statement if there are any
plans to implement this feature in
11 matches
Mail list logo