Hanlp Lucene Plugin is live · free · last verified 4 Nov 2026 · viability monitor
Hanlp Lucene Plugin
HanLP Chinese word segmentation for Solr and Lucene, installed as two JARs plus a schema.xml fieldType.
For a Solr 5.x core indexing Chinese, this is the shortest path to HanLP-grade segmentation: two JARs, one fieldType, restart. The catch is age — the tutorial is pinned to Solr 5.2.1, so if you're on a newer branch, smoke-test that com.hankcs.lucene.HanLPTokenizerFactory resolves before you build around it. On 5.x it earns its place; elsewhere, scope a proof-of-concept first.
Verdict generatedVerified 9d ago · liveness 55/100 · cite: rightaichoice.com/tools/hanlp-lucene-plugin
- Search engineers running Apache Solr 5.x with Chinese-language content who need word-level indexing
- Java developers who want HanLP tokenization configured entirely through schema.xml
- Teams needing domain-specific custom dictionaries to lift Chinese recall
- Catalogs where ambiguous Chinese word boundaries (和服 vs 商品和服务) cause false-positive hits
- Solr deployments on versions newer than 5.x that can't budget a compatibility spike first
- Non-Lucene search platforms such as Elasticsearch, which need a separate adapter
- Teams wanting a managed or hosted Chinese tokenization service
We scan live Reddit threads, YouTube comments, X posts, G2 reviews and other communities — and hand you an honest verdict in under a minute.
- Honest verdict, not marketing
- Real pros & cons from real users
- Attributed quotes with receipts
3 free scans · no card needed
Skip this plugin if you're on a modern Solr branch and can't spend a day smoke-testing whether a tokenizer documented against Solr 5.2.1 still loads, or if you want Chinese tokenization delivered as a hosted service.
Re-typing fields is not optional: any business field you leave on Solr's default analyzer becomes unsearchable, which surfaces as a recall complaint weeks after launch
Free and open-source, hosted on GitHub, so the cost comparison isn't licence spend — it's engineering time. A Solr 5.x shop pays nothing and spends a schema migration plus dictionary tuning. On a newer branch the cheaper-looking free plugin can cost more than a paid tokenizer that ships current-version support, because the compatibility spike is unbilled until it overruns.
In short
Hanlp Lucene Plugin — HanLP Chinese word segmentation for Solr and Lucene, installed as two JARs plus a schema.xml fieldType. Best for Search engineers running Apache Solr 5.x with Chinese-language content who need word-level indexing, Java developers who want HanLP tokenization configured entirely through schema.xml, Teams needing domain-specific custom dictionaries to lift Chinese recall. Free to use.
What is Hanlp Lucene Plugin?
Hanlp Lucene Plugin — HanLP Chinese word segmentation for Solr and Lucene, installed as two JARs plus a schema.xml fieldType. Best for Search engineers running Apache Solr 5.x with Chinese-language content who need word-level indexing, Java developers who want HanLP tokenization configured entirely through schema.xml, Teams needing domain-specific custom dictionaries to lift Chinese recall. Free to use.
The HanLP Solr plugin replaces Solr's character-by-character Chinese tokenization with HanLP's dictionary- and model-driven word segmentation. Instead of 商品和服务 collapsing into individual characters, you get 商品, 和, 服务 as real index terms — which is what recall and precision on Chinese queries actually depend on. It ships as two JARs (hanlp-portable.jar and hanlp-solr-plugin.jar) dropped into ${webapp}/WEB-INF/lib and wired in via a fieldType using com.hankcs.lucene.HanLPTokenizerFactory. The vendor's English-language walkthrough uses Solr 5.2.1 as the reference install and claims compatibility with Solr 5.x and Lucene 5.x. Setup is deliberately minimal: define text_cn (or patch text_general), assign it to every field that holds Chinese text, and restart Solr. Custom dictionaries and HanLP settings live in hanlp.properties under the Solr resources directory, alongside log4j.properties. Because the tokenizer sits inside Solr's standard analyzer chain, StopFilterFactory with stopwords.txt, SynonymFilterFactory for index- and query-time synonyms, and LowerCaseFilterFactory keep working without modification. One configuration rule gets repeated in the tutorial: enableIndexMode belongs on the index analyzer only. Turning it on for the query analyzer interferes with PhraseQuery. In index mode HanLP full-segments long compounds — 中医药大学附属医院 expands to 中医药, 中医, 医药, 大学, 附属医院, 附属, 医院 — so partial-word queries still land. The documented worked example indexes five sample documents and shows 和服 matching the correct row rather than 商品 和服 务. This is a self-hosted Java plugin for search engineers already running a Solr 5.x cluster, not a hosted API. In the same slot, IK Analyzer and the Jieba Solr plugin are the usual comparisons; HanLP's edge is its dictionary breadth and index-mode sub-word expansion. On newer Solr branches, treat the 2015 tutorial as a starting point and verify the factory class still loads before committing.
Key features
- Chinese word segmentation via HanLP dictionary- and model-based tokenizer
- Schema-driven setup with com.hankcs.lucene.HanLPTokenizerFactory
- enableIndexMode full-segments long compounds into sub-words at index time
- Vendor warns against enabling indexMode on the query analyzer (affects PhraseQuery)
- Custom dictionaries and settings via hanlp.properties in the Solr resources directory
- Two-JAR deployment: hanlp-portable.jar and hanlp-solr-plugin.jar
- Drop into ${webapp}/WEB-INF/lib followed by a Solr restart
- Compatible with Solr StopFilterFactory and stopwords.txt
- Works with SynonymFilterFactory for index- and query-time synonyms
- Runs alongside Solr LowerCaseFilterFactory in the analyzer chain
- Resolves boundaries like 商品和服务 without the 和服 false positive
- Offline, self-hosted tokenization with no external API calls
- Apache Solr 5.x support, compatible with Lucene 5.x
- Assign every Chinese field a text_cn or patched text_general type to avoid default tokenization
Behind the verdict
Reach for this plugin when your stack is Solr 5.x, your content is Chinese, and you want HanLP's segmentation without running a separate tokenization service. The appeal is operational: no new process, no network hop, no external dependency — just a tokenizer class in an analyzer chain you already understand. The index-mode behavior is the feature worth understanding before you deploy. Full-segmenting long compounds at index time means a query for 医院 can still hit a document containing 附属医院, because 医院 was indexed as a sub-token alongside the full term. It's a recall lever, and it's why the tutorial is adamant that indexMode stays off across the query analyzer — you'll break PhraseQuery otherwise. Where it bites: the documentation is a 2015-08-23 post written around Solr 5.2.1. There's no changelog on the page, and no third-party signal in the last 90 days to confirm newer Solr versions were validated. If you're on Solr 7, 8, or 9, plan a short spike — drop the JARs into WEB-INF/lib, point one core at text_cn, and confirm the factory class instantiates — before you migrate production cores. We'd pick HanLP over IK Analyzer when dictionary coverage and index-mode sub-word expansion matter more than a larger install base. IK has more field mileage; HanLP gives you the full-segmentation behavior and custom dictionary control through hanlp.properties in one package. The Jieba Solr plugin is the other neighbor — leaner word list, less configuration surface. If you need synonyms or stopwords, HanLP plays fine with Solr's StopFilterFactory and SynonymFilterFactory in the same chain, which is often what decides it. A practical caveat from the tutorial itself: every field holding Chinese has to be explicitly typed text_cn (or text_general after you patch it). Miss one and
Models under the hood
as of 2026-11-08
Limitations
- Manual setup: two JARs (hanlp-portable.jar, hanlp-solr-plugin.jar) into ${webapp}/WEB-INF/lib, an edit to the core's schema.xml, then a Solr restart.
- The vendor's step-by-step tutorial is dated 2015-08-23 and documented against Solr 5.2.1, with compatibility claimed only for Solr 5.x and Lucene 5.x — newer branches are unproven and need a smoke test.
- Custom dictionaries depend on placing hanlp.properties in the Solr resources directory. enableIndexMode must stay off on the query analyzer or PhraseQuery behavior is affected.
as of 2026-10-30
Researching Hanlp Lucene Plugin? Get your full AI stack in 60 seconds.
Free, no signup — tell us your goal and get tools matched to your budget & existing stack.
Is Hanlp Lucene Plugin still active?
Hanlp Lucene Plugin is live · free · last verified 4 Nov 2026 · viability monitor.
Viability score
How well maintained and how widely used is Hanlp Lucene Plugin? Built from what the vendor actually publishes (docs, changelog, tutorials, integrations, pricing), whether the site is live, and how much real users discuss it. How we calculate this
Last calculated: November 2026
How we score →What do users say about Hanlp Lucene Plugin?
What people actually say about Hanlp Lucene Plugin — is it worth it?
Our community sentiment research written Jul 5, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
How we verified this
Every listed fact about Hanlp Lucene Plugin — pricing, features, links, status — is re-read from the vendor's own pages by our verification pipeline and each change is logged with a date; the last pass ran on 4 Nov 2026. Analysis is drafted with AI models and checked against our editorial standards before publishing; see how we verify.
Verification history
We have re-verified Hanlp Lucene Plugin 12 times since . Each pass re-reads the vendor's own pages and re-checks every listed field against that evidence; passes where nothing had changed are marked as such.
- — changed pricing page, limitations
- — changed description, pricing tiers, features, our verdict, summary
- — changed pricing page
- — changed who should skip it, pricing tiers, summary, our verdict, features, use cases, setup time, who it suits, hidden costs, pricing fit, limitations, description, switching in, switching out
- — changed description, summary, our verdict, who it suits, features, who should skip it, pricing tiers, pricing page
- — changed description, features, who should skip it, summary, our verdict, who it suits, pricing tiers
Showing the 6 most recent of 12 verification passes.
Free to cite with attribution — this page re-verifies continuously.
How much does Hanlp Lucene Plugin cost in 2026?
Hanlp Lucene Plugin: Free to use. Pricing last verified 4 Nov 2026.
Plans compared
Every published Hanlp Lucene Plugin tier, its price as the vendor publishes it, who it fits, and what it adds over the tier below. The 12-month cost projection follows.
| Plan | Price | Billing | Who it's for |
|---|---|---|---|
| Free | Free | — | Search engineers running a self-hosted Solr 5.x cluster with Chinese content who can own the schema edit and reindex themselvesAdds: Free entry point: the open-source plugin on GitHub, with no per-request or per-seat charge |
12-month cost
Project the real annual outlay, including the implied monthly cost when only an annual tier is published.
Vendor list price only. Add-on usage, seat overages, and contract minimums are surfaced under Hidden costs & gotchas.
Where the pricing makes sense
The company stage and team size where Hanlp Lucene Plugin's pricing actually pencils out — and where peers do it cheaper.
Free and open-source, hosted on GitHub, so the cost comparison isn't licence spend — it's engineering time. A Solr 5.x shop pays nothing and spends a schema migration plus dictionary tuning. On a newer branch the cheaper-looking free plugin can cost more than a paid tokenizer that ships current-version support, because the compatibility spike is unbilled until it overruns.
Has Hanlp Lucene Plugin's pricing changed?
No plan price for Hanlp Lucene Plugin has moved since we began logging in Aug 2026; the pricing page is re-read on every verification pass.
Who should pick Hanlp Lucene Plugin?
Pick Hanlp Lucene Plugin if you are Search engineers running Apache Solr 5.x with Chinese-language content who need word-level indexing, Java developers who want HanLP tokenization configured entirely through schema.xml, Teams needing domain-specific custom dictionaries to lift Chinese recall, Catalogs where ambiguous Chinese word boundaries (和服 vs 商品和服务) cause false-positive hits.
Look elsewhere if you are Solr deployments on versions newer than 5.x that can't budget a compatibility spike first, Non-Lucene search platforms such as Elasticsearch, which need a separate adapter, Teams wanting a managed or hosted Chinese tokenization service, Developers unfamiliar with Java deployment and Solr schema configuration.
Skip it if Skip this plugin if you're on a modern Solr branch and can't spend a day smoke-testing whether a tokenizer documented against Solr 5.2.1 still loads, or if you want Chinese tokenization delivered as a hosted service.
GeneratedReal-world workflow fit
Concrete scenarios for the personas Hanlp Lucene Plugin actually fits — and what changes day-one when you adopt it.
Drop hanlp-portable.jar and hanlp-solr-plugin.jar into ${webapp}/WEB-INF/lib, define a text_cn fieldType with com.hankcs.lucene.HanLPTokenizerFactory (enableIndexMode=true on index, false on query), assign it to every Chinese field, then restart Solr and reindex.
Outcome: Chinese fields return word-level matches instead of single-character noise, and existing StopFilterFactory and LowerCaseFilterFactory stages behave as before.
Add the domain's compound terms to a custom dictionary via hanlp.properties in the Solr resources directory, and keep indexMode on so long compounds expand into sub-words at index time.
Outcome: Queries like 商品和服务 resolve to the intended boundary rather than triggering a 和服 match, lifting relevance on catalog search.
Stand up a single Solr core from the sample config, swap the text_general fieldType for the HanLP tokenizer, and load a test corpus before touching production schema.
Outcome: A working Chinese-segmented index on one core that you can judge on real queries before migrating every field.
Use cases
- Convert an existing Solr text_general fieldType to HanLP segmentation so Chinese fields become searchable
- Add a separate text_cn fieldType and re-type only the fields that need Chinese tokenization
- Index a Chinese product catalog where ambiguous boundaries like 商品和服务 cause false hits
- Raise recall on compound domain terms by enabling indexMode full segmentation at index time
- Keep Solr stop word and synonym filtering working while swapping in HanLP tokenization
- Run Chinese tokenization fully offline inside a self-hosted Solr deployment
Setup time & first value
How long it actually takes to get something useful out of Hanlp Lucene Plugin — broken out by persona, not the marketing-page minute.
A Solr 5.x engineer who already owns schema.xml: minutes to drop the two JARs and define the fieldType, then a Solr restart and a full reindex. Add an afternoon for re-typing every Chinese field and spot-checking recall. On a Solr branch newer than 5.x, plan a half-day to a day proving the tokenizer loads before you commit.
Switching to or from Hanlp Lucene Plugin
How to bring data in from common predecessors and how to get it back out — written for the switcher, not the buyer.
- →From Solr's default analyzer: replace the text_general fieldType body with HanLPTokenizerFactory and re-type every Chinese field explicitly, then reindex
- →From IK Analyzer: swap the tokenizer class to com.hankcs.lucene.HanLPTokenizerFactory in the same fieldType and move dictionary terms into hanlp.properties
- →From the Jieba Solr plugin: replace the tokenizer class in schema.xml, carry custom terms into a HanLP custom dictionary, and reindex
- ↗To IK Analyzer: swap the tokenizer class in schema.xml and rebuild your custom dictionary in IK's format, then reindex
- ↗To the Jieba Solr plugin: replace the tokenizer class and port custom dictionary entries, then reindex
- ↗To Elasticsearch: this Solr plugin doesn't carry over — you need a separate HanLP adapter for the Elasticsearch analyzer chain
Integrations
Resources & guides
Tutorials & Learning
YouTube returned 6 videos for “Hanlp Lucene Plugin”, and we withheld 6: 6 did not mention Hanlp Lucene Plugin. We are showing none, because we could not prove any of them are about Hanlp Lucene Plugin.
Official links
What are the best Hanlp Lucene Plugin alternatives?
The closest alternatives to Hanlp Lucene Plugin we list are React Email Editor, Spacelift and Bluehost. Ranked by direct product-type match, not category overlap.
| Alternative | Pricing | Starts at | Last verified |
|---|---|---|---|
| React Email Editor | Freemium | Pricing not published | — |
| Spacelift | Freemium | Pricing not published | — |
| Bluehost | Paid | Pricing not published | — |
Alternatives to Hanlp Lucene Plugin
View all
React Email Editor
Embed Unlayer's email, page, popup, and document builders, plus AI Assistant, into your own SaaS via one SDK and JSON schema.
Tools that pair well with Hanlp Lucene Plugin
Common stack mates teams adopt alongside Hanlp Lucene Plugin, with the specific reason each pairing earns its keep.
React Email Editor
Embed Unlayer's email, page, popup, and document builders, plus AI Assistant, into your own SaaS via one SDK and JSON schema.
Spacelift
Spacelift runs Terraform, OpenTofu, Pulumi, CloudFormation and Kubernetes IaC plus Day 2 ops through one governed GitOps pipeline.
Bluehost
Bluehost's AI Site Builder turns one sentence into a working WordPress site, store or app on managed hosting.
Hanlp Lucene Plugin vs its closest rival
Hanlp Lucene Plugin's closest head-to-head is with Spider Cloud.
Our Hanlp Lucene Plugin vs Spider Cloud verdict written Jul 5, 2026 is more than 90 days old, so it is being re-reviewed against current data and is not shown.
Head-to-head comparisons
Frequently asked questions
Categories
For makers of Hanlp Lucene Plugin
- Get a Verified Listing for Hanlp Lucene Plugin ($39): a written decision within 1 working day.
- Free listing for another tool: Free reviews are decided in order, within 3 weeks of the review starting.
Used Hanlp Lucene Plugin? Help shape our editorial sentiment research.