That's bad that there should be such limitations. Is this something which we can work around? Or is it related to how we use the API?

We can always continue exploring the custom collector approach we use ATM. The limitations we have is based on the fact that the field cache only used to return the first value for a given field. I think this limitation does not exist anymore!?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira