Mike,
I've applied the patch as of a June-dated trunk. There were some
trivial conflicts, but mostly-easy to apply. It has been in production
for a couple months with no major hiccups so far :).
Justin
"Smiley, David W." writes:
> Hi Mike.
>
> I have hopes that LSP will be ready in time for
Unfortunately, what that means is that your client application has to
do any accent-folding before you get to Solr, or you have to write your
own component that handles this. There's been some talk of making
the wildcards go through some sort of analysis chain, but it hasn't
been coded yet as far a
thank you for your advices guys... i have tried analysis, without wildcards
by the way and it ws working smoothly ( cant check it now coz its sunday :)
)
so in this case it is not possible to support wildcards with accented
letters? I have tried many other words too and when i use accented letter
Usually what's going on in this case is that wildcards aren't analyzed, so
they're never going through the asciifoldingfilter. So you're looking in your
index for françois* and, since the filter isn't applied, the 'ç' isn't
changed to 'c'.
You can infer this from tacking &debugQuery=on to your URL
Well, especially if you optimize after your indexing operation, you could
easily have your index size double temporarily. The reason is that
replication moves the changed segments. When you optimize, your
entire index is re-written into a new segment and presto! your
index on the slave doubles. Thi
Does hl.fragsize do what you want?
Best
Erick
On Sat, Sep 3, 2011 at 11:56 AM, alex wrote:
> hi all,
> I would like to truncate some titles(or limit length) while still using
> highlighthing if possible , like :
> very long title...end of very long title or
> very long title sfgdsdfsg end of ver
Ah, you're right. You'll have to go into that bit of code and look at the
various group parameters and create your own links for paging,
particularly the "matches" response value. Basically, you're paging on
different criteria than Solritas is set up for and have to roll your own...
Best
Erick
On
This an unsolved problem in general. The TREC folks try this, see:
http://trec.nist.gov/
but in general I've found that each domain has such specific needs
that "correctness" isn't an easy thing to pin down. Of course you
can, with a known set of data, define the "best" response and try to
tune So
First question is whether you want to. There are ways to stop the
search, but how do you know that the last document of your 200K
isn't the most relevant? There's no way I know to determine that
without examining all the docs.
Best
Erick
On Fri, Sep 2, 2011 at 11:20 AM, John wrote:
> Hi,
>
> In
You're on a multicore setup, are you sure you're indexing and searching
to the same core?
the fact that it works for you in Jetty but not Tomcat sure looks like
you've set your Tomcat instance up differently, there shouldn't be any
difference between the two from a Solr perspective.
Best
Erick
O
I'm looking to implement something similar. Has anybody worked something out
to work around this issue?
Any guidance is greatly appreciated!
Regards,
Federico
--
View this message in context:
http://lucene.472066.n3.nabble.com/Pattern-Is-there-a-method-of-resolving-multivalued-date-ranges-into
Hi,
Is this simply for returning a date string, or do you really need a full-blown
Date object for your years?
I'd probably go with a "tint" field for the faceting on year, if year is the
lowest date resolution you need.
If you need to convert 2008 to 2008-01-01T00:00:00Z to put into a real "dat
If I understand correctly, you SORT on login_time desc.
Perhaps your biggest problem is that for each user logging in, they jump to
page 1, so this issue is very visible.
A simple way to fix this is to add a filter when you page, e.g.
fq=login_time:[* TO ], effectively freezing the time
window y
Many customers have asked me how to do this, so it's not easy enough.
Therefore I opened SOLR-2742 to add even more convenience :)
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
Solr Training - www.solrtraining.com
On 25. aug. 2011, at 01:38, Chris Hostetter wrote:
>
Are you able to share the source code for this CombiningFilter?
This sounds like it should be a relatively simple filter.
-Yonik
http://www.lucene-eurocon.com - The Lucene/Solr User Conference
On Sat, Sep 3, 2011 at 2:28 PM, shinkanze wrote:
> hi
> every one
> i am new to solr i have a problem while indexing and replicating
> my index size is 80GB
> indexing problem ::
> when i detlta indexed previous index or main index was deleted all i was
> left with was delta index
> what may be
hi all,
I would like to truncate some titles(or limit length) while still using
highlighthing if possible , like :
very long title...end of very long title or
very long title sfgdsdfsg end of very...
Can it be done currently with any highlighter ?
thanks.
When I specify only 3 no of rows(&rows=3) I just get only 3 results. This
problem is not with the no of docs, but with grouping of docs.
Well in velocity script browse.vm there is a code that is related to
pagination.
#if($response.response.get('grouped'))
#else
#link_to_previous_page("previo
Plus, for the function query termfreq(), it does not support wild card or
phrase query. it just support simple word. Is there anybody having
experience about those term vector issues?
thanks,
Zong
On Fri, Sep 2, 2011 at 5:40 PM, Zong Peng wrote:
> Hi,
>
> I am using the nightly built version so
hi
every one
i am new to solr i have a problem while indexing and replicating
my index size is 80GB
indexing problem ::
when i detlta indexed previous index or main index was deleted all i was
left with was delta index
what may be the possible cause for it??
replication problem :
when i did r
20 matches
Mail list logo
