Again it seems to me like you are trying to read from the index directly. You should never do that. Just pretend like the index doesn't even exist, and write normal content nodes onto the normal non-index part of the tree and then index will STILL be getting used automatically. It works just like an RDBMS index. You create the index, and then forget about it. All your searches will use the appropriate indexes if they can but you should never try to look at the index itself. Just write code as if the index did not exist. When you add nodes to the content tree, they will be "indexed" automatically. If you ARE trying to store DATA in an index, then do not do that. That is wrong. You should be storing data as nodes on the tree. The index will take care of itself automatically.
Best regards, Clay Ferguson [email protected] On Tue, Oct 11, 2016 at 8:49 AM, rachna <[email protected]> wrote: > Hi, > > Just like property index type, I have got my own index type called custom, > which is loaded with data according to requirement. So query is not > picking > up this index as it's custom type, I want to write my own API function to > read this index and return data, I am not getting any exception but neither > data. > When I use node.getNodes(), it doesn't return me any nodes from :index node > onwards, > When I use oak-run tool to open this index, I can see it's populated with > the required data from :index onwards. > > > > -- > View this message in context: http://jackrabbit.510166.n4. > nabble.com/Custom-index-type-tp4665031p4665105.html > Sent from the Jackrabbit - Users mailing list archive at Nabble.com. >
