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 Australia.
Phone: 03 5227 8230 International: +61 3 5227 8230
Fax: 03 5227 8000
/2009/09/08/auto-suggest-from-popular-queries-using-edgengrams/
Cheers
Avlesh
On Mon, Oct 26, 2009 at 7:43 AM, Bernadette Houghton
bernadette.hough...@deakin.edu.au wrote:
We need to offer begins with type searches, e.g. a search for surname,
f will retrieve surname, firstname, surname, f
, 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...@deakin.edu.au wrote:
Thanks for this suggestion (thanks Gerald also: no, we're not using
BlackLight
source. copyfield
source=*author_mt dest=all/ should work for you as long as you have a
field called all defined in your schema. 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
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
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 checking.
Bern
-Original Message-
From: Joel Nylund [mailto:jnyl...@yahoo.com]
Sent
, 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
Joel
On Oct 28, 2009, at 6:20 PM, Bernadette Houghton wrote:
Hi Joel, I had a similar issue
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 29, 2009 at 2:52 AM, Bernadette Houghton
bernadette.hough...@deakin.edu.au wrote:
Here's the all code snippets -
!-- catchall field, containing all
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
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
I've just set up something similar (much thanks to Avesh!)-
fieldType name=edgytext class=solr.TextField positionIncrementGap=100
analyzer type=index
tokenizer class=solr.KeywordTokenizerFactory/
filter class=solr.LowerCaseFilterFactory/
filter class=solr.EdgeNGramFilterFactory
, 2009 at 5:25 PM, Bernadette Houghton
bernadette.hough...@deakin.edu.au wrote:
I've just set up something similar (much thanks to Avesh!)-
fieldType name=edgytext class=solr.TextField
positionIncrementGap=100
analyzer type=index
tokenizer class=solr.KeywordTokenizerFactory/
filter class
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
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:
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
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: +61 3 5227 8000
MSN: bern_hough...@hotmail.com
Email:
bernadette.hough
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 8230
Fax: 03
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.xml file already contains URIencoding
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
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, Shalin.
Tomcat
Shalin, the XML from solr admin for the relevant field is displaying as -
str name=citation_ta title=Browse by Author Name for Moncrieff, Joan
href=/fez/list/author/Moncrieff%2C+Joan/Moncrieff, Joan/a, a
title=Browse by Author Name for Macauley, Peter
omega)
display correctly. But with solr turned on, garbage displays instead. If we
enter the characters as decimal (e.g. #969;), all displays OK with or without
solr. Does this suggest anything to anyone??
TIA
bern
-Original Message-
From: Bernadette Houghton [mailto:bernadette.hough
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 2009 9:18 AM
protected=protwords.txt/
filter class=solr.RemoveDuplicatesTokenFilterFactory/
/analyzer
/fieldType
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
, 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 in the same place)
does not get retrieved
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
bernadette.hough...@deakin.edu.au
wrote:
Hi Christian, try this one - http://www.deakin.edu.au/dro/view/DU
...
-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 and the error -
Oct 09 08:20:17 [debug] [196] Solr
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
.
Regards, Patrick
Bernadette Houghton schrieb:
Sorry, the last line was truncated -
HTTP Status 400 - org.apache.lucene.queryParser.ParseException: Cannot parse
'(Asia -- Civilization AND status_i:(2)) ': Encountered - at line 1, column
7. Was expecting one of: ( ... * ... QUOTED
29 matches
Mail list logo