| Re: [orion-dev] /filesearch not immediately successful |
|
Hello Mark, I executed the following command: http://localhost:8082/search/search.html#/file/hsn-OrionContent/nw.epm.refapps.shop/,regEx=true,fileType=xml which led to a lot of
“/file/hsn-OrionContent/nw.epm.refapps.shop
/.../?depth=1” calls. One call returned the pom.xml that I am exactly searching for:
As you can see, the response is in JSON. However, when I run the command http://localhost:8082/file/hsn-OrionContent/nw.epm.refapps.shop/?depth=1 with jQuery.ajax() or in a REST client, I always get a response in HTML (and less information compared to the JSON response above):
I am not very familiar with HTTP headers, but I set “Accept” to “application/json” in the REST client
and dataType : "json" in the jQuery.ajax(), but with no effect. Do have any idea how to get the response in JSON? Best regards Hergen From: orion-dev-bounces@xxxxxxxxxxx [mailto:orion-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mark Macdonald Hi Hergen,
https://your-orion-server/search/search.html#/file/hergen-OrionContent/your/working/directory/,regEx=true,fileType=xml When you visit this URL in your browser, and click Search, it should find all xml files in the working directory, including pom.xml. Since the crawler currently
does not provide a way to filter against a filename, this is the best you can achieve right now.
As Ken said, there's many improvements in the search functionality that we'd like to see…
On Fri, Apr 25, 2014 at 10:14 AM, Siefken, Hergen <hergen.siefken@xxxxxxx> wrote: Dear Ken, your screenshot shows a functionality with which I can search for a specific term in
a files content, right? I search for a specific file name („pom.xml“). I use the following call to do this:
/filesearch?q=NameLower:pom.xml+Location:/file/user-OrionContent/folder/* Can I use the “Regular _expression_” in this call “to force a crawling search”?
If so, how can I do this? Best regards Hergen From:
orion-dev-bounces@xxxxxxxxxxx [mailto:orion-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ken Walker One workaround to this (yes the indexer can be slow to update changes) is to toggle the "Regular _expression_" option to force a crawling search vs. using the index.
|
