Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-3997

join module should not depend on grouping module

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 4.0-ALPHA
    • 4.9, 6.0
    • None
    • None
    • New

    Description

      I think TopGroups/GroupDocs should simply be in core?

      Both grouping and join modules use these trivial classes, but join depends on grouping just for them.

      I think its better that we try to minimize these inter-module dependencies.
      Of course, another option is to combine grouping and join into one module, but
      last time i brought that up nobody could agree on a name.

      Anyway I think the change is pretty clean: its similar to having basic stuff like Analyzer.java in core,
      so other things can work with Analyzer without depending on any specific implementing modules.

      Attachments

        1. LUCENE-3997.patch
          13 kB
          Robert Muir
        2. LUCENE-3997.patch
          13 kB
          Robert Muir

        Activity

          People

            Unassigned Unassigned
            rcmuir Robert Muir
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: