topic Re: Lucene Query PATH Question in Alfresco Archive

Lucene Query PATH Question

mtw999 — Fri, 15 Feb 2013 21:08:25 GMT

I'm trying to query type from NodeBrowser query utilityATH:"/app:company_home/st:sites/cm:alftrain/cm:documentLibrary/cm:TestFolder01" TYPE:"{http://www.ziaconsulting.com/model/knowledgebase/1.0}article"returns resultsPATH:"/app:company_home/st:sites/cm:alftrain/cm:documentLibrary/cm:TestFolder01"

Re: Lucene Query PATH Question

mitpatoliya — Mon, 18 Feb 2013 06:26:13 GMT

May be internally it is tockenising the path with "/" to drill down to destination.
But if you put URI it will be ambiguous for search engine that might be the issue.

Also you are using combination of prefix and URI what is the behavior when you use URI for all?
and by the way is it just for the knowledge or any req?

Re: Lucene Query PATH Question

mtw999 — Mon, 18 Feb 2013 17:09:54 GMT

If I use only/all URI it fails. I was trying to determine where it was failing in PATH which is why there may appear to combination of prefix and URI (i.e. was URI for my custom type failing). I put the URI in type jsut as an experiment and TYPE is being resolved from URI. I was trying to figure out if there is some issue or something else I needed to do when using URI in PATH

Mike

Re: Lucene Query PATH Question

andy — Mon, 11 Mar 2013 10:35:39 GMT

Hi

When you use PATH you must use the form prefix:localName for each element. You can not us the URI.
Exactly as you cannot use the URI in an XPATH expresssion.

Andy