Yonk, can you please advise whether this event will be recorded and available
for later download? (It starts 5am our time ;-) )
Regards
Bern
-Original Message-
From: ysee...@gmail.com [mailto:ysee...@gmail.com] On Behalf Of Yonik Seeley
Sent: Thursday, 25 February 2010 10:23 AM
To: solr
Not sure what version it was supported from, but we're on 1.3.
bern
-Original Message-
From: A. Steven Anderson [mailto:a.steven.ander...@gmail.com]
Sent: Friday, 6 November 2009 10:25 AM
To: solr-user@lucene.apache.org
Subject: Re: leading and trailing wildcard query
> Hi Steve, a query
, 2009 at 5:25 PM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au> wrote:
> I've just set up something similar (much thanks to Avesh!)-
>
> positionIncrementGap="100">
>
>
>
>maxGramSize="25" /&g
I've just set up something similar (much thanks to Avesh!)-
.
.
.
.
bern
-Original Message-
From: Otis Gospodnetic [mailto:otis_gospodne...@yahoo.com]
Sent: Friday, 6 November 2009
Sorry, answering my own question - I see it has been marked for 1.5 :-)
-Original Message-
From: Bernadette Houghton [mailto:bernadette.hough...@deakin.edu.au]
Sent: Friday, 30 October 2009 2:54 PM
To: 'solr-user@lucene.apache.org'
Subject: uppercase and wildcards/truncation
Looks like solr 1.3 at least is still not lowercasing wildcarded/truncated
queries.
I see from http://issues.apache.org/jira/browse/SOLR-219 that this has been an
issue for a while.
Anyone know if this has yet been solved?
TIA
Bernadette Houghton, Library Business Applications Developer
r any other
field type is being copied into the field.
Having said that converting the "all" field to type "edgytext" should still
work fine. All your regular searches on a text field should also work with
the edgytext field. Ain't it like that?
Cheers
Avlesh
On Thu, Oct
gt; 2009/10/28 Joel Nylund :
>> Thanks Bern, now that you mention it they are in there, I assume if
>> I remove
>> them it will work, but I probably dont want to do that right?
>>
>> Is there a way for this particular query to ignore stopwords
>>
>> thanks
&g
articular query to ignore stopwords
thanks
Joel
On Oct 28, 2009, at 6:20 PM, Bernadette Houghton wrote:
> Hi Joel, I had a similar issue the other day; in my case the
> solution turned out to be that the letters were stopwords. Don't
> know if this is your answer, but worth c
Hi Joel, I had a similar issue the other day; in my case the solution turned
out to be that the letters were stopwords. Don't know if this is your answer,
but worth checking.
Bern
-Original Message-
From: Joel Nylund [mailto:jnyl...@yahoo.com]
Sent: Thursday, 29 October 2009 9:17 AM
To:
. Moreover, for your specific use
case, the "all" field needs to be of type "edgytext".
Cheers
Avlesh
On Wed, Oct 28, 2009 at 9:35 AM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au> wrote:
> Thanks Avlesh. The issue with not doing a phrase query on my &quo
.org/java/2_3_2/queryparsersyntax.html#Escaping%20Special%20Characters.
If you use SolrJ, there is a ClientUtils class somewhere in the package
which has helper functions to achieve query escaping.
Cheers
Avlesh
On Tue, Oct 27, 2009 at 9:22 AM, Bernadette Houghton <
bernadette.hough...@d
ilto:avl...@gmail.com]
Sent: Monday, 26 October 2009 6:32 PM
To: solr-user@lucene.apache.org
Subject: Re: "begins with" searches
Read up of setting-up these kind searches here -
http://www.lucidimagination.com/blog/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
C
s don't work on phrase searches, nor do range searches.
Any suggestions as to how best to search for "begins with" phrases; or, how to
best configure solr to support such searches?
TIA
Bernadette Houghton, Library Business Applications Developer
Deakin University Geelong Victoria 3217
eanup before
the submit to the Solr server that replaces each sequence of minus
characters by a single one.
Regards, Patrick
Bernadette Houghton schrieb:
> Sorry, the last line was truncated -
>
> HTTP Status 400 - org.apache.lucene.queryParser.ParseException: Cannot parse
&
Thanks for this, marklo; it is a *very* useful page.
bern
-Original Message-
From: marklo [mailto:mar...@pcmall.com]
Sent: Thursday, 8 October 2009 1:10 PM
To: solr-user@lucene.apache.org
Subject: Re: Problems with WordDelimiterFilterFactory
Use http://solr-url/solr/admin/analysis.jsp t
... "[" ... "{" ... ...
-Original Message-
From: Bernadette Houghton [mailto:bernadette.hough...@deakin.edu.au]
Sent: Friday, 9 October 2009 8:22 AM
To: 'solr-user@lucene.apache.org'
Subject: RE: Problems with WordDelimiterFilterFactory
Here's the query a
ubject: Re: Problems with WordDelimiterFilterFactory
Bern,
I am interested on the solr query. In other words, the query that your
system sends to solr.
Thanks,
Christian
On Oct 7, 2009, at 5:56 PM, Bernadette Houghton
wrote:
> Hi Christian, try this one - http://www.deakin.edu.au/dro/view/DU:360
10/07/2009 05:32 PM, Bernadette Houghton wrote:
> We are having some issues with our solr parent application not retrieving
> records as expected.
>
> For example, if the input query includes a colon (e.g. hot and cold:
> temperatures), the relevant record (which contains a colon
ces either side of hyphen) doesn't work.
Our schema.xml contains the following -
Added to beginning of tomcat startup.bat (positioning is important!)
set JAVA_OPTS="-Dfile.encoding=UTF-8"
Thanks to everyone for their much appreciated help!
Bern
-Original Message-----
From: Bernadette Houghton [mailto:bernadette.hough...@deakin.edu.au]
Sent: Monday, 31 August 20
small omega)
display correctly. But with solr turned on, garbage displays instead. If we
enter the characters as decimal (e.g. ω), all displays OK with or without
solr. Does this suggest anything to anyone??
TIA
bern
-Original Message-
From: Bernadette Houghton [mailto:bernadette.
Shalin, the XML from solr admin for the relevant field is displaying as -
Moncrieff, Joan, Macauley, Peter and Epps, Janine 2006, “My Universe is Here�: Implications
For the Future of Academic Libraries From the Results of a Survey of
Researchers, vol. 38, no. 2, pp. 71-83.
The wei
om: Shalin Shekhar Mangar [mailto:shalinman...@gmail.com]
Sent: Wednesday, 26 August 2009 5:50 PM
To: solr-user@lucene.apache.org
Subject: Re: encoding problem
On Wed, Aug 26, 2009 at 12:52 PM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au> wrote:
> Thanks for your quick reply, Sh
Thanks for your quick reply, Shalin.
Tomcat is running on my Windows machine, but does not appear in Windows
Services (as I was expecting it should ... am I wrong?). I'm running it from a
startup.bat on my desktop - see below. Do I add the Dfile line to the
startup.bat?
SOLR is part of the rep
m
On Wed, Aug 26, 2009 at 10:24 AM, Bernadette Houghton <
bernadette.hough...@deakin.edu.au> wrote:
> We have an encoding problem with our solr application. That is, non-ASCII
> chars displaying fine in SOLR, but in googledegook in our application .
>
> Our tomcat server.xm
ng for the JVM, but have no
idea how to do this. I'm running Windows, and there is no tomcat process in my
Windows Services.
TIA
Bernadette Houghton, Library Business Applications Developer
Deakin University Geelong Victoria 3217 Australia.
Phone: 03 5227 8230 International: +61 3 5227 82
other field type and apply a suitable tokenizer?? Is this correct, and if so,
which tokenizer?
TIA
Bernadette Houghton, Library Business Applications Developer
Deakin University Geelong Victoria 3217 Australia.
Phone: 03 5227 8230 International: +61 3 5227 8230
Fax: 03 5227 8000 International:
Dear all, does anybody have any solr searching end-user documentation that they
can pass on?
Regards
Bernadette Houghton, Library Business Applications Developer
Deakin University Geelong Victoria 3217 Australia.
Phone: 03 5227 8230 International: +61 3 5227 8230
Fax: 03 5227 8000
29 matches
Mail list logo
