使用 Homebrew 安装 groonga

项目链接

• 主页
• 仓库

命令和别名

• groonga
• groonga-suggest-create-dataset

项目历史

Groonga grew out of the Senna search-engine lineage. The Groonga news archive records a 'Senna -> groonga' transition on 2009-01-14, followed by 0.x releases in 2010 and the Groonga 1.0.0 release on 2010-08-29.

The 2.0.0 release announcement in 2012 framed the major-version bump as a signal that Groonga had become practical enough for wider use after steady feature additions and bug fixes. From that point the project kept a long-running monthly-ish release culture, visible in the official news archive across the 2.x through later numbered series.

The core documentation describes Groonga as both a fast full-text search engine based on inverted indexes and a column-oriented DBMS. It exposes basic functionality as a C library, provides a server command, and is used by related projects as a library, a server, or a storage engine.

采用历史

Groonga adoption spread through integrations rather than only through the standalone executable. The official related-projects page lists Mroonga for MySQL, PGroonga for PostgreSQL, Rroonga for Ruby, Nroonga for Node.js, Perl/PHP/Haskell/GObject bindings, client libraries, server utilities, and command-line helpers.

The official users page documents production-style uses such as PatentField using Groonga and Mroonga for full-text search, drilldown search, near search, snippets, and column-store features over large patent data, plus smaller web and command-line tools using Rroonga, Mroonga, and other bindings.

For package ecosystems, Groonga matters because the same engine appears as a direct package, a dependency of database extensions, and a dependency of language bindings. Installing the formula can support standalone experiments, local indexing tools, or native dependencies for higher-level search stacks.

使用方式

The Homebrew package installs the `groonga` command and related tooling. Users can create and query Groonga databases directly, run the built-in server, or use the C library and protocol endpoints through bindings and clients.

Groonga is commonly chosen when an application needs immediate index updates, concurrent reads while updating, multilingual tokenization choices, drilldown/aggregation, or geo search without handing all data to a separate general-purpose search cluster.

The project has no general user credential file in the official package-level curation. Configuration is more database/server specific than a single dotfile convention, so this batch leaves config and credentials locations null.

为什么软件包爱好者会关心

Groonga is package-nerd interesting because it is a native C search engine with a broad integration surface: command-line executable, embeddable library, database storage-engine base, PostgreSQL extension base, and language-binding target.

Its release cadence and source-package archive make it visible in Unix packaging culture: distributors can package the core engine once, then layer Mroonga, PGroonga, Rroonga, and other related packages on top.

It also represents a non-English-first search problem space in package indexes. Tokenizers, MeCab integration, n-gram behavior, and Japanese/Chinese-friendly search are not add-ons; they are central to why the package exists.

时间线

• 2009: Official news records the transition from Senna to Groonga.
• 2010: Groonga 1.0.0 was released on 2010-08-29.
• 2012: Groonga 2.0.0 was released, with the announcement emphasizing maturity after steady 1.x development.
• 2014: Droonga 1.0.0 was released as a distributed Groonga-related data processing engine.
• 2015: PGroonga 1.0.0 was released for PostgreSQL full-text search backed by Groonga.
• 2020s: The official news archive shows continued major-series releases and ongoing PGroonga activity.

Related projects

• Mroonga is the MySQL/MariaDB storage-engine integration built on Groonga.
• PGroonga is the PostgreSQL extension that uses Groonga as an index for fast multilingual full-text search.
• Rroonga, Nroonga, p5-Groonga, Ploonga, Proonga, Haroonga, and Groonga-GObject expose Groonga to language runtimes.
• Groonga-client, GQTP clients, and command-line utilities such as grnwrap sit around the standalone server and CLI workflow.

来源

• https://groonga.org/
• https://groonga.org/docs/characteristic.html
• https://groonga.org/docs/news.html
• https://groonga.org/ja/blog/2012/02/29/release.html
• https://groonga.org/related-projects.html
• https://groonga.org/users/
• https://mroonga.org/
• https://pgroonga.github.io/