Really strange behaviour while searching

[alarocca]

I created my custom model with a text field which value can be selected by a list (by means of constraints). All works as expected except the search. This is what happens:

- Add a PDF, selecting my custom model as document type, and from the options list I choose "Specialties"
- Immediately, execute a search for my-custom-field equals to "Specialties" and it works.
- After few seconds (usually between 0 and 15), the same search do not provide any result. The same test I did using API and search features.
- Further I still cand find that document appending the asterisk to the search string,

String query = "@oes\\:productRequestBusiness:Specialties*";
‍‍

If I update the document, without chancing any data, for few seconds it is again searchable without the asterisk.

This happens only with PDF and XLS, no problem with DOC and PPT. Seems to be an issue related to the indexing feature.

I had this problem with Alfresco 2.1 on Windows 2003 and MSSQL Server. I will try to reproduce it with MySQL or HSQLDB.

[alarocca]

I did further checks about.

This issue is not related to the database (reproduced with MS SQL and HSQLDB), neither to the custom fied type (reproduced with list/constraints and simple text).

This happens with any type of document not only PDF and XLS as previously reported.

Searching on standard fields works perfectly.

It seems to be a bug on the indexing engine.


http://issues.alfresco.com/browse/AR-1855

[andy]

Hi

What language/locale are you using?
What rules have you got set that could affect these documents?
Are you using meta data extraction?

Do you mean the search ending with a * works?
Does the search work if it is quoted?

When you go and look and edit this property is it set to what you expect it to be? Is it set correctly when you go and look in the node browser (as admin)?

What are your settings in the DD for indexing this property?
How is it set?

Andy

[alarocca]

Hi Andy,

as you can see

http://issues.alfresco.com/browse/AR-1855

the reported issue was due to the meta data extraction rule put on the root (Company Home). Once removed it, all works as expected. Even if my expectation is that even with that rule anything should work.

I tested without any difference with English and Italian.