I can run the example, but when I try to use a live instance of accumulo (1.8) it throws a ClassNotFoundException DocumentIndexIntersectingIterator.java. It seems like the GraphxGraphGenerator is built against Accumulo 1.6.4, and even the test doesn't seem to work if I bump it up to 1.8. I wonder if this is an issue with the latest version of Accumulo not being supported by Rya? I find it strange that Accumulo complains about not being able to find the DocumentIndexIntersectingIterator.java class since it is a Rya class and not an accumulo class.. do i need to install (some kind of) a Rya addon to Accumulo for this to work?
On Mon, Jan 9, 2017 at 7:39 PM, Puja Valiyil <[email protected]> wrote: > Hi John, > It's not possible to use the core Rya indices to support the graphx api-- > there is a requirement for uniqueness in vertices that is not possible to > support using the core indices. To support graphx efficiently, all of the > assertions on a node of the graph must be stored on a single accumulo row > (so you can guarantee all of the assertions will be stored on a single > accumulo tablet). The core Rya indices do not support this requirement, > but the entity centric index does. > There is a configuration parameter to enable the entity centric index. You > can see how to enable it by looking at the entity centric example in the > examples project-- let me know if you have trouble finding it. > > On Monday, January 9, 2017, John Smith <[email protected]> wrote: > > > I'm trying to use the GraphXGraphGenerator class but it is hard coded to > > use the EntityCentricIndex table by default. But this doesn't exist in > Rya > > by default. Shouldn't this default to the SPO table? Or perhaps even > > better, be a configurable parameter? What is the purpose of the > > EntityCentricIndex ? How do I enable it? > > >
