YUKI Hiroshi
null+****@clear*****
Tue Nov 18 12:17:05 JST 2014
YUKI Hiroshi 2014-11-18 12:17:05 +0900 (Tue, 18 Nov 2014) New Revision: f59fc5ffb10b02160c7adbc19827e4a95011a69f https://github.com/droonga/droonga.org/commit/f59fc5ffb10b02160c7adbc19827e4a95011a69f Message: Update release announcement for Droonga 1.0.8 Modified files: news/_posts/2014-11-29-release.md Modified: news/_posts/2014-11-29-release.md (+49 -15) =================================================================== --- news/_posts/2014-11-29-release.md 2014-11-08 16:06:49 +0900 (9021cd6) +++ news/_posts/2014-11-29-release.md 2014-11-18 12:17:05 +0900 (0e3beed) @@ -12,30 +12,66 @@ A Droonga cluster works like an HTTP server compatible to [Groonga][groonga] wit Are you interested in Droonga: how it works and how useful? Let's try the [tutorial][] for an introduction, and see the [overview][] to understand Droonga's design strategy more and more. -## Orchestration of front-end HTTP server nodes, better compatibility to Groonga, and more! +## Improvements in Droonga 1.0.8 This release Droonga 1.0.8 contains many improvements. +Major topics are here: -Now, a front-end HTTP server node (protocol adapter, aka `droonga-http-server`) works as a member of the Droonga cluster truly. -Even if one of `droonga-engine` node become unavailable, HTTP servers automatically keep working with active `droonga-engine` nodes. -Moreover, An HTTP server automatically distributes requests from clients to multiple `droonga-engine` nodes. In other words, now it works like a load balancer. +### Orchestration of front-end HTTP server nodes +Now, a front-end HTTP server node based on `droonga-http-server` works as a member of the Droonga cluster truly. +Even if one of `droonga-engine` node become unavailable, `droonga-http-server` nodes keep them working with active `droonga-engine` nodes automatically. +Moreover, a `droonga-http-server` node distributes requests from clients to multiple `droonga-engine` nodes. +In other words, now it works like a simple load balancer. -(TBD) +### Better compatibility to Groonga -## Detailed list of improvements +Some minor incompatibilities have been corrected. - * [Droonga-engine ][droonga-engine] - * [Droonga-http-server ][droonga-http-server] - * [Express-droonga ][express-droonga] - * [Drnbench ][drnbench] - * [Drntest ][drntest] - * [Grn2drn ][grn2drn] + * `select` command: + * The `output_columns` option accepts whitespace-separated list of column names (compatible to Groonga's `command_version=1` form.) + * `output_columns=*` works correctly for `TABLE_NO_KEY` tables. + * `column_list` command: + * A `_key` virtual column is correctly appear in the result, for tables with one of flags: `TABLE_HASH_KEY`, `TABLE_PAT_KEY`, and `TABLE_DAT_KEY`. + * `table_create` command: + * The `key_type` parameter becomes required for `TABLE_HASH_KEY`, `TABLE_PAT_KEY`, and `TABLE_DAT_KEY` tables. + You'll get an error response, if the parameter is not given. + (Groonga unexpectedly accepts `table_create` requests without `key_type` parameter, but it is a known issue.) + +### Detailed list of all improvements + + * [Droonga-engine ][droonga-engine] 1.0.8 + * Better compatibility to Groonga's `select`, `column_list`, and `table_create` commands. + (See above) + * The `daemon` option is now ignored in the static configuration file. + Now, you always have to specify `--daemon` option for the `droonga-engine` command + to start it as a daemon. + * The `droonga-engine-configure` command now shows prompts for all options always. + * [Droonga-http-server ][droonga-http-server] 1.0.9 + * A new `--host` option is available to restrict the listening IP address. + The default value is `0.0.0.0` (meaning `listen all IP addresses`). + * A new `--disable-trust-proxy` option is available to disable the feature + even if it is activated by the static configuration file. + * The `daemon` option is now ignored in the static configuration file. + Now, you always have to specify `--daemon` option for the `droonga-http-server` command + to start it as a daemon. + * The `droonga-http-server-configure` command now shows prompts for all options always. + * Improvements from `express-droonga` itself. + (See below) + * [Express-droonga ][express-droonga] 1.0.7 + * Supports multiple Droonga Engine nodes as its backends. + Now `express-droonga` can work like a load balancer. + * The list of connecting Droonga Engine nodes can be automatically updated + based on the actual list of active members in the cluster. + This feature is activated by the `syncHostNames` option for the `application.droonga()` method. + * [Drntest ][drntest] 1.1.7 (released at 2014-11-18) ## Conclusion * Droonga 1.0.8 has been released! - * (TBD: TODO summarize this release) + * Front-end HTTP server nodes are now orchestrated as nodes in the cluster. + Droonga clusters now work more robustly. + * It becomes more compatible to Groonga. * Droonga project will release a new version every month! Droonga project welcomes you to join us as a user and/or a developer! See [community][] to contact us! @@ -47,6 +83,4 @@ Droonga project welcomes you to join us as a user and/or a developer! See [commu [droonga-engine]: https://github.com/droonga/droonga-engine [droonga-http-server]: https://github.com/droonga/droonga-http-server [express-droonga]: https://github.com/droonga/express-droonga - [drnbench]: https://github.com/droonga/drnbench [drntest]: https://github.com/droonga/drntest - [grn2drn]: https://github.com/droonga/grn2drn -------------- next part -------------- HTML����������������������������...下載
