I have a field where there are items that are plurals, and used as very
specific locators, so i do a solr search type:articles, and it translates it
into : type:article, then into type:articl... is tehre a way to stop it from
doing this on either the field "type" or on a list of words "articles,
n
hello,
my documents have a field called member_of,
this field holds a list, so it will look like this:
member_of: fred bob mike journals wsjournals jen steve
if 'member_of' is a 'string' and i search:
goats AND member_of(fred bob journals)
i get the right results,
however, the faceting doesnt wo
DHast wrote:
>
> hello,
> my documents have a field called member_of,
> this field holds a list, so it will look like this:
> member_of: fred bob mike journals wsjournals jen steve
> if 'member_of' is a 'string' and i search:
> goats AND member_of(fre
DHast wrote:
>
>
>
> DHast wrote:
>>
>> hello,
>> my documents have a field called member_of,
>> this field holds a list, so it will look like this:
>> member_of: fred bob mike journals wsjournals jen steve
>> if 'member_of' i
is it possible to do somehting like this:
Now im wondering how to do something like this:
if so, i dont seem to be making progress
thanks
--
View this message in context:
http://www.nabble.com/copyfield-at-search-time--tp25491979p25491979.html
Sent from the Solr - User mailing l
hi,
if i do a search: text:"law order"~40
i get this:
text:"law order"~40
text:"law order"~40
PhraseQuery(text:"law order"~40)
text:"law order"~40
OldLuceneQParser
However if i do: "law order"~40
i get this:
"law order"~40
"law order"~40
text:law order
text:law order
OldLuceneQParser
my Sche
well it seems what is happening is solr is not being consistent,
DHast wrote:
>
> hi,
> if i do a search: text:"law order"~40
> i get this:
>
> text:"law order"~40
> text:"law order"~40
> PhraseQuery(text:"law order"~40)
>
parses to a PhraseQuery. I have trouble believing even Solr 1.3
> behaved like you reported, something seems fishy.
>
> Erik
>
> On Sep 18, 2009, at 9:02 AM, DHast wrote:
>
>>
>> well it seems what is happening is solr is not being consistent,
>>
&g
when i have my fieldname: text set as a text field, advanced search queries
work very well, but when i have it set as a string it seems to ignore them,
like proximity searching and so on.
example: text as string:
text:"law order"~33
text:"law order"~33
text:law order
text:law order
text as text:
009, at 6:37 AM, DHast wrote:
>
>>
>> when i have my fieldname: text set as a text field, advanced search
>> queries
>> work very well, but when i have it set as a string it seems to
>> ignore them,
>> like proximity searching and so on.
>> exampl
ok, used the built in fieldtype text_ws that seems to go well
DHast wrote:
>
> i have looked, and seem to be running into a dead end every time i try it,
> but again it may be because of the caching and me not realizing it was
> doing it till my hair was half pulled.
>
> i do
is there a way i can actually tell solr which index i want it to search
against with the query? I know it will cost a bit on performance, but it
would be helpful
i have many indexes and it would be nice to determine which one should be
used by the user.
thanks
--
View this message in context:
ht
Singh wrote:
>
> Are you talking about multiple cores?
>
> Cheers
> Avlesh
>
> On Mon, Sep 21, 2009 at 9:15 PM, DHast
> wrote:
>
>>
>> is there a way i can actually tell solr which index i want it to search
>> against with the query? I know it will
well after looking at http://wiki.apache.org/solr/CoreAdmin
perhaps multiple cores is what i want,
DHast wrote:
>
> No, I am talking about having multiple indexes, i want to send the index
> name to the searcher so it will search that index, rather than use the one
> defined i
Hello,
I have recently installed Solr as an alternative to our home made lucene
search servers, and while in most respects the performance is better, i
notice that phrase searches are incredibly slow compared to normal lucene,
primarily when using facets
example:
"City of New York, Matter of" tak
ah, it turns out it was one of my 6 facets, the author. in the data pool
tehre are over 1.9 million documents, and about 800,000 authors, removing
that facet worked since the field was untokenizd and slow considering how
many values tehre were. Solr is definitely faster, and as fast and or
faste
little
over 22 GB's
Lance Norskog-2 wrote:
>
> Are you saying that faceting is faster on a tokenized field? Is this true?
>
> On Tue, Oct 20, 2009 at 2:02 PM, DHast
> wrote:
> ...
> , removing
>> that facet worked since the field was untokenizd and
17 matches
Mail list logo