Ask Questions and Find Answers

Hi Olga,

I don't have access to the 6.2 EE source, but I can tell you that the property is not part of the CE edition. As an EE customer though, you should be able to access the source to reference. The behaviour between the annotation and the IndexerRegitryUtil is odd -- certainly sounds like a bug. For the property though, here is what I would suggest (after you have downloaded and unpacked the source)

1. First open the portal.properties file (from portal-impl) and look the property up in there. Liferay does a really good job (imho) of adding comments to properties that help explain what they're used for -- so you might find your answer right inline. 

... if that doesn't work ...

2. Open the file PropsKeys and look up the property. That should take you to the line where you can see the constant which is most likely INDEX_REQUEST_BUFFER_ENABLED as this is the pattern that Liferay uses for naming conventions and such. Once you have that you can search the entire code base for that constants and I am willing to bet only one or two locations will come up. I would imagine at that point it would only take you a few minutes of reviewing the code to reveal the mystery

I'm sorry that I can't give you a definitive answer, but I am happy to help in your hunt -- but you have to be the hands at the keyboard since I don't have the source. If you do take this advice, let us kow what you find -- I am curious!

Hi Olga,

About the problem related to indexer proxy is not updated:

Inspection of liferay sources showed that in second case registry returns not indexer, but indexer proxy which is not updated on portlet redeployment. ​​

I have reviewed 7.0, 7.1 and master source code and it seems that issue is already solved in newer versions:

• https://github.com/liferay/liferay-portal/blob/master/modules/apps/portal-search/portal-search/src/main/java/com/liferay/portal/search/internal/IndexerRegistryImpl.java#L151

As Liferay 6.2 is in Limited support phase, that issue won't be solved in that version.

We've found that if we set property index.request.buffer.enabled to false, than registry util returns indexer instance insite of proxy object and everything works fine. But I didn't manage to find any documentation for this property.
Could anyone tell me, why annotation and direct call of registry works different and consult on index.request.buffer.enabled property and possible effects of setting it to false?
​​​​​

index.request.buffer.enabled is related to 7.0 Index Buffer functionality that was backported to 6.2 version in https://issues.liferay.com/browse/LPS-69361

Index Buffer avoids to index same object more than once, see full explanation in that LPS-69361. In case that buffer is deactivated, unnecessary index operations will be done.
Without Index Buffer, some customers has also detected out-of-sync indexations: last index request is not indexed in last place, so wrong data is indexed. But that issue is not very common and is only produced in case having CPU shortage or a CPU with a small number of cores.

About why annotation works in a different way than getting the indexer from registry, that is very stange as annotation internally also gets indexer from registry, see code from IndexableAdvice:

• https://github.com/liferay/liferay-portal/blob/6.2.x/portal-impl/src/com/liferay/portal/search/IndexableAdvice.java#L77

In my opinion, the only explanation is that behavior is caused by classloaders, but I am not sure.

As you are using an Enterprise version of Liferay, if you need more information my advice is to open a ticket to Liferay Enterprise Support service.

Regards,
Jorge