cancel
Showing results for 
Search instead for 
Did you mean: 

Lucene Queries from Node Browser failing

jjmierwa
Champ in-the-making
Champ in-the-making
Hello,

I'm still very new to both Alfresco and Lucene so please bear with me. I am running 4.0.b. When going to the node browser and trying to execute Lucene queries, I continually get the following error message "Search failed due to: org.alfresco.repo.search.impl.lucene.LuceneQueryParserException: 021315839" The numbers at the end vary with each identical query or query variant thereof that I run. I am doing very basic queries based on those detailed on a search tutorial and also on the web services SDK examples where the content has already been created. The logs appear to be running but I am seeing no exceptions being generated.

Does any one out there have any ideas? Is it something in the way that the system was configured or does Lucene have to be somehow enabled? Any ideas are welcome.
4 REPLIES 4

mitpatoliya
Star Collaborator
Star Collaborator
when ever you are using any lucene query you need to follow its syntax.
This error generally occurs when you are violating the syntactical rules of lucene.
Please refer this link for correct formats.
http://wiki.alfresco.com/wiki/Search

jjmierwa
Champ in-the-making
Champ in-the-making
I have reviewed and re-reviewed the web page that you provided and am at a loss to see what is wrong with the syntax. I have executed samples which have placed simple text content into alfresco. One example of the content is "The quick brown fox jumped over the lazy dog". Some of the content is company home and other test content is located in other test spaces.

Selecting workspace://SpacesStore and "lucene" from the search dropdown, I am entering TEXT:"quick brown fox" and I get the error. Syntactically, it conforms to the web page. Any other thoughts on what is going on?

jjmierwa
Champ in-the-making
Champ in-the-making
The problem has been resolved by removing and re-installing Alfresco, after which the syntax i was using worked just fine. It's unfortunate that the parser errors are so ambiguous.

mitpatoliya
Star Collaborator
Star Collaborator
Please mark it as solved.