: q=reference:"4-1.2"
:
: the value is a text, but the following is indexed as a number (e.g.:
: 004001002, where "4" becomes "004", and 1 becomes "001", and 2 "002"),
depnding on how you look at it, you could implment this as
one of two plugins:
1) if you consider this a special form of query
thank you guys for the answers... now I have to check / read some docs ;)
Rich
-Original Message-
From: Simon Willnauer [mailto:simon.willna...@googlemail.com]
Sent: Tuesday, September 21, 2010 23:00
To: solr-user@lucene.apache.org
Subject: Re: trie
2010/9/21 Péter Király :
> You
2010/9/21 Péter Király :
> You can read about it in Lucene in Action second edition.
have a look at
http://www.lucidimagination.com/developer/whitepaper/Whats-New-in-Apache-Lucene-3-0
page 4 to 8 should give you a good intro to the topic
simon
>
> Péter
>
> 2010/9/21 Papp Richard :
>> is there
http://en.wikipedia.org/wiki/Trie explains pretty well what a trie is
and what it's used for. In search, suffix trees (which are a special
case of tries) are especially important.
On 21 September 2010 21:34, Papp Richard wrote:
> is there any good tutorial how to use and what is trie? what I fou
You can read about it in Lucene in Action second edition.
Péter
2010/9/21 Papp Richard :
> is there any good tutorial how to use and what is trie? what I found on the
> net is really blurry.
>
> rgeards,
> Rich
>
>
> __ Information from ESET NOD32 Antivirus, version of virus signature
>
On Mon, Dec 21, 2009 at 5:37 PM, Marc Sturlese wrote:
>
> Should sortMissingLast param be working on trie-fields?
>
>
Nope, trie fields do not support sortMissingFirst or sortMissingLast.
--
Regards,
Shalin Shekhar Mangar.
On Thu, Oct 1, 2009 at 2:54 PM, Lance Norskog wrote:
> Trie fields also do not support faceting.
Only those that index multiple tokens per value to speed up range queries.
> They also take more ram in
> some operations.
Should be less memory on average.
-Yonik
http://www.lucidimagination.com
On Thu, Oct 1, 2009 at 11:09 PM, Steve Conover wrote:
>> Not in time for 1.4, but yes they will eventually get it.
>> It has to do with the representation... currently we can't tell
>> between a 0 and "missing".
>
> Hmm. So does that mean that a query for latitudes, stored as trie
> floats, from
> Not in time for 1.4, but yes they will eventually get it.
> It has to do with the representation... currently we can't tell
> between a 0 and "missing".
Hmm. So does that mean that a query for latitudes, stored as trie
floats, from -10 to +10 matches documents with no (i.e. null) latitude
value
On Thu, Oct 1, 2009 at 10:39 AM, Steve Conover wrote:
> I just noticed this comment in the default schema:
>
>
>
> Does that mean TrieFields are never going to get sortMissingLast?
Not in time for 1.4, but yes they will eventually get it.
It has to do with the representation... currently we can'
Trie fields also do not support faceting. They also take more ram in
some operations.
Given these defects, I'm not sure that promoting tries as the default
is appropriate at this time. (I'm sure this is an old argument.:)
On Thu, Oct 1, 2009 at 7:39 AM, Steve Conover wrote:
> I just noticed this
I just noticed this comment in the default schema:
Does that mean TrieFields are never going to get sortMissingLast?
Do you all think that a reasonable strategy is to use a copyField and
use "s" fields for sorting (only), and trie for everything else?
On Wed, Sep 30, 2009 at 10:59 PM, Steve Co
Hmm, seems I was one day too early with my nightly then:p
Quote from Chris (2009-08-20 17:04):
"i changed it to be manufacturedate_dt since that fits with the existing
scheme ... the data is all made up, but so is all hte rest of our data."
seems like lucene.apache.org is down at the moment but wi
Thanks for the reply Yonik!
I'm using the nightly from 2009-08-20, so its a rather fresh build. And by
comparing the schema with the one im using now I had made a mistake when
defining the field.
By examining the most recent build, i noticed that the normal date field is
defined as follows:
(its a
I can't reproduce any problem.
Are you using a recent nightly build?
See the example schema of a recent nightly build for the correct way
to define a Trie based field - the article / blog may be out of date.
Here's what I used to test the example data:
http://localhost:8983/solr/select?q=manufact
Trie has a custom parser that can load the FieldCache for sorting. Its
basically a built in type now, that supports fieldcache, sorting, stored
fields, etc.
On Sat, Jul 4, 2009 at 3:27 PM, Chris Hostetter wrote:
>
> : My data are library call numbers, normalized to be comparable, resulting
> in
>
: My data are library call numbers, normalized to be comparable, resulting in
: (maximum) 21-character strings of the form "RK 052180H359~999~999"
:
: Now, these are fine -- they work for sorting and ranges and the whole thing,
: but right now I can't use them because I've got two or three for ea
On Tue, Jun 9, 2009 at 10:19 PM, Amit Nithian wrote:
> I take it by the deafening silence that this is not possible? :-)
>
Anything is possible :)
However, it might be easier to upgrade to 1.4 instead.
>
> On Mon, Jun 8, 2009 at 11:34 AM, Amit Nithian wrote:
>
> > Hi,
> > I am still using So
I take it by the deafening silence that this is not possible? :-)
On Mon, Jun 8, 2009 at 11:34 AM, Amit Nithian wrote:
> Hi,
> I am still using Solr 1.2 with the Lucene 2.2 that came with that version
> of Solr. I am interested in taking advantage of the trie filtering to
> alleviate some perfor
19 matches
Mail list logo
