Content revisions support

Sadly, it seems that's not easily possible. You would probably need to implement a datasource controller that provides the revisions as a new item type.
There's currently not much documentation on how to do that (README.txt and inline comments), but I'm currently working on expanding developer documentation in the handbook – so, hopefully better documentation will be available shortly.

Any updates over here ?

I need to be able to retrieve old revisions also in my index.

Best,

No, no updates that I know of. As said, this is already possible to do, just write a datasource controller which provides the entities in such a way (or pay someone to do it). If it is generic enough, we might even include it into this module directly.
I myself don't have the time to implement this (and there also doesn't seem to be much demand), so it will probably not be added unless someone else implements it.

That would be great to have. I'm thinking about using this in combination with computed properties - so that you have the revision from-to time span available for filtering.

This would be great to have. Especially when constructing views that should display the original author of a node and the user that last modified the node.

This would be great to have. Especially when constructing views that should display the original author of a node and the user that last modified the node.

I think that's an entirely different issue, that just affects the Views field handlers and not at all the indexing.

@ dasjo: OK, let's make it a feature request, then. Unless someone provides a patch (or funding), though, it probably won't be implemented.

This issue has not seen activity in over 2,5 years. I am therefore closing this issue to clean up the issue queue. Feel free to re-open and update this issue if you feel this issue is still relevant and of importance.