apache / apache/lucene

Make all of Analysis completely independent from Lucene Core [LUCENE-3151]

Open
#4,224 30 comments 0 reactions 0 assignees View on GitHub
affects-version:4.0-ALPHA legacy-jira-fix-version:4.9 legacy-jira-fix-version:6.0 legacy-jira-priority:Major type:enhancement
Dominant language
Java
Stars
3.6k
Forks
1.4k
Avg merge
2d 11h
Merged PRs (30d)
88

Description

Lucene's analysis package, including the definitions of Attribute, TokenStream, etc. are quite useful outside of Lucene (for instance, Mahout uses them) for text processing. I'd like to move the definitions, or at least their packaging, to a separate JAR file so that one can consume them w/o needing Lucene core. My draft idea is to have a definition area that Lucene core is dependent on and the rest of the analysis package can then be dependent on the definition area. (I'm open to other ideas as well)

---
Migrated from [LUCENE-3151](https://issues.apache.org/jira/browse/LUCENE-3151) by Grant Ingersoll (@gsingers), updated May 09 2016
Attachments: [LUCENE-3151.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-3151/LUCENE-3151.patch) (versions: 3)

Contributor guide

Open the contributing guide

Research direction

Start by reading the issue description and the attached LUCENE-3151.patch. Trace the analysis package's dependency boundaries with Lucene Core and compare them with the proposed definition area. Done means the analysis definitions can be consumed from a separate JAR without requiring Lucene Core.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, search
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.