[OAK-6355] Usage of NodeAggregator creates cyclic dependency between oak.spi.query and oak.plugins.index.*

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.7.3, 1.8.0
• Component/s: core, indexing, query
• Epic Link: Modularisation of Oak
• Assignee: Unassigned
• Reporter: Angela Schreiber
• Created: 15/Jun/17 14:04
• Updated: 08/Oct/19 15:22
• Resolved: 28/Jun/17 15:37

Description

As mentioned in OAK-6304 I had an another look at the dependencies of the oak.spi.query packages space and found a single dependency on oak.plugins.index.*:

QueryIndex.FulltextQueryIndex.getNodeAggregator returns a org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator.

As far as I could see this is the only dependency left within the oak.spi.query package pointing to interfaces/classes inside oak-core.

tmueller, would it be possible to move the org.apache.jackrabbit.oak.plugins.index.aggregate.NodeAggregator interface to some package below oak.spi.query or a potential (new) oak.spi.index? wdyt?

Issue Links

• relates to: OAK-6304 Cyclic dependency between oak.spi.query an oak.query.*