Good point, I'm honestly not sure how Lucene would exactly interpret the example query string
Rob On 10/7/13 3:32 PM, "Chris Dollin" <[email protected]> wrote: >On Monday, October 07, 2013 02:31:35 PM Rob Vesse wrote: > >> In the example given your FILTER clause is superfluous since the text >> query ensures that only subjects which satisfy the text query are >>matched >> so having the FILTER as well is doing unnecessary work over the possible >> solutions produced by the text query. >> >> Rob > >I thought the string ('Daily newspaper') fed to text:query was taken >as a statement in the Lucene query language, in which, if I am >recalling correctly, it will be taken as "containing 'Daily' or >'newspaper'. >OR rather than AND or in-sequence. The filter is needed to validate >candidates. > >If I'm wrong I have some Elda documentation to fix ... > >> >{ >> > >> >*?s text:query (dbpprop:type 'Daily newspaper')* . >> > >> >?s dbpprop:type ?v1 . >> > >> >*FILTER ( REGEX(STR(?v1), "Daily newspaper" , "i") )* >> >} > >Chris > >-- >"You're down as expendable. You don't get a weapon." /Dark Lord of >Derkholm/ > >Epimorphics Ltd, http://www.epimorphics.com >Registered address: Court Lodge, 105 High Street, Portishead, Bristol >BS20 6PT >Epimorphics Ltd. is a limited company registered in England (number >7016688) >
