Re: Forwardslash delimiter.Solr4.0 query for path like /Customer/Content/*

2012-11-01 Thread Jack Krupansky
: Forwardslash delimiter.Solr4.0 query for path like /Customer/Content/* Ok.If there is no other way I will have some string parsing to do, but in this case I am wondering a little bit about the chosen delimiter...as it is central to nearly any path in directories, web resources etc.,right? Best

Re: Forwardslash delimiter.Solr4.0 query for path like /Customer/Content/*

2012-11-01 Thread Dirk Högemann
aybe a custom search component that runs before the QueryComponent and > does the escaping? > > -- Jack Krupansky > > -Original Message- From: Dirk Högemann > Sent: Tuesday, October 30, 2012 1:07 PM > To: solr-user@lucene.apache.org > Subject: Forwardslash delimiter.So

Re: Forwardslash delimiter.Solr4.0 query for path like /Customer/Content/*

2012-10-30 Thread Jack Krupansky
Maybe a custom search component that runs before the QueryComponent and does the escaping? -- Jack Krupansky -Original Message- From: Dirk Högemann Sent: Tuesday, October 30, 2012 1:07 PM To: solr-user@lucene.apache.org Subject: Forwardslash delimiter.Solr4.0 query for path like

Forwardslash delimiter.Solr4.0 query for path like /Customer/Content/*

2012-10-30 Thread Dirk Högemann
Hi, I am currently upgrading from Solr 3.5 to Solr 4.0 I used to have filter-bases restrictions for my search based on the paths of documents in a content repository. E.g. fq={!q.op=OR df=}folderPath_}/customer/content/* Unfortunately this does not work anymore, as lucene now supports Regexpsea