Re: Incorrect wiki page, DaslConfiguration. And casesensitivity
Eirikur Hrafnsson <[email protected]>
| Newsgroups | gmane.comp.jakarta.slide.devel |
|---|---|
| Message-ID | <[email protected]> |
To answer myself a little with the case insensitive property search question: I changed my Domain.xml to redefine how some of the standard properties are indexed like so: <propertiesindexer classname="org.apache.slide.index.lucene.LucenePropertiesIndexer"> <parameter name="indexpath"> store/index/metadata </parameter> <parameter name="asynchron"> true </parameter> <configuration name="indexed-properties"> <!-- Idegaweb custom properties and forcing some standard properties to be case insensitive --> <property name="ContentType" namespace="IW:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> <property name="displayname" namespace="DAV:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> <property name="creator-displayname" namespace="DAV:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> <property name="getcontenttype" namespace="DAV:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> <property name="comment" namespace="DAV:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> <property name="getcontentlanguage" namespace="DAV:"> <text analyzer="org.apache.lucene.analysis.SimpleAnalyzer"/> <is-defined /> </property> </configuration> </propertiesindexer> After doing that AND uploading my test file again to re-index it (or you could throw away the whole index to regenerate it on startup) I managed to find the file by a part of its displayname with a DASL search and it isn't case-sensitive anymore : ) best regards Eiki, idega. On 21.6.2006, at 17:35, Eirikur Hrafnsson wrote: > uh yes there is. > > From http://wiki.apache.org/jakarta-slide/DaslConfiguration > Operators (extensions) > Operator property-contains > > Is an extension to RFC. It works like the contains operator but for > properties. This is intended for use with properties that contains > abstracts, keyword lists etc. > > > > On 21.6.2006, at 17:14, Michael Oliver wrote: > >> Uh, no there is no reference to "<S:property-contains>" on the >> DaslConfiguration page of the wiki. >> >> Michael Oliver >> CTO >> Alarius Systems LLC >> 6800 E. Lake Mead Blvd, #1096 >> Las Vegas, NV 89156 >> Phone:(702)866-9034 >> Cell:(518)378-6154 >> Fax:(702)974-0341 >> >> >> -----Original Message----- >> From: Eirikur Hrafnsson [mailto:[email protected]] >> Sent: Wednesday, June 21, 2006 10:58 AM >> To: Slide Developers Mailing List >> Cc: Slide Users Mailing List >> Subject: Incorrect wiki page, DaslConfiguration. And casesensitivity >> >> Hi all, >> >> I just wanted to point out an error in the Wiki page that has wasted >> my time twice now since I had forgotten it from the first time : / >> http://wiki.apache.org/jakarta-slide/DaslConfiguration >> >> The page states and illustrates that you can use a Slide only >> <S:property-contains> in your DASL searching. This will not fly! >> The correct name for the parameter is <S:propcontains> as I learned >> from an earlier post to this mailing list. >> >> Someone with Wiki edit privileges might want to change that... >> >> p.s. >> Is there any way to do a case-insensitive search with propcontains ? >> >> best regards >> Eiki, idega. >> >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> ¯¯¯ >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> Eirikur S. Hrafnsson >> Chief Software Engineer >> >> [email protected] >> >> >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> ¯¯¯ >> ¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯ >> Idega hf. ı Engjavegi 6 ı 104 Reykjavík ı Iceland >> Tel. +354 554 7557 ı Fax +354 885 7557 >> >> http://www.idega.com ı [email protected] >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> >