[Groonga-commit] droonga/droonga.org at 68c184d [gh-pages] Complete release entry for 1.1.0

Zurück zum Archiv-Index

YUKI Hiroshi null+****@clear*****
Thu Apr 30 00:10:05 JST 2015


YUKI Hiroshi	2015-04-30 00:10:05 +0900 (Thu, 30 Apr 2015)

  New Revision: 68c184d3f5e65096eccee2c83ad3e7bf1050c164
  https://github.com/droonga/droonga.org/commit/68c184d3f5e65096eccee2c83ad3e7bf1050c164

  Message:
    Complete release entry for 1.1.0

  Modified files:
    news/_posts/2015-04-29-release.md

  Modified: news/_posts/2015-04-29-release.md (+17 -8)
===================================================================
--- news/_posts/2015-04-29-release.md    2015-04-29 23:08:34 +0900 (46d914c)
+++ news/_posts/2015-04-29-release.md    2015-04-30 00:10:05 +0900 (ff20ca8)
@@ -4,6 +4,8 @@ layout: news-item
 published: false
 ---
 
+Very sorry for this delay, now we've released Droonga 1.1.0 with a long-cherished feature!
+
 ## What's Droonga?
 
 Droonga is a distributed full text search engine, compatible to [Groonga][groonga].
@@ -12,20 +14,26 @@ 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.
 
-## (summary of this release)
+## True hot-add of replica nodes is now available!
 
-The most important topic on this release Droonga 1.1.0 is the *(something)*.
+The most important topic on this release Droonga 1.1.0 is *true hot-add of replica nodes*.
+It was one of long-planned features of Droonga, but we've got it.
+Now you can add new replica nodes to your Droonga cluster without any downtime, even if you don't stop crawling/adding new data!
 
-(TBD)
+To do it, you have to have two or more replicas in the cluster, except the new adding replica node.
+For more information, see [tutorial for adding replica nodes](/tutorial/add-replica/).
 
 ## Detailed list of improvements
 
  * [Droonga-engine 1.1.0][droonga-engine]
    * General:
      * Graceful stopping/restarting works correctly with continual inpouring messages.
-     * A new parameter `random` is introduced to single step definitions.
+     * A new parameter `single_operation` is introduced to single step definitions.
        If you set it to `true`, messages for the handler will be delivered to just single volume (one of replicas and slices).
        It is useful for commands which has to be executed only once in a cluster, like `system.status`.
+     * A new parameter `use_all_replicas` is introduced to single step definitions.
+       If you set it to `true`, messages for the handler will be delivered to all replica volumes always.
+       It is useful for commands which has to be executed all replicas, like `system.statistics.object.count.per-volume`.
      * `add` command now accepts requests with automatically-convertible mismatched type keys.
        For example, a string key `"1"` is available for a table with the key type `UInt32`.
      * `dump` command: the value of a column referring any record of another table are correctly exported as its key string, instead of object value (it's invalid value for a message of the `add` command).
@@ -35,6 +43,7 @@ The most important topic on this release Droonga 1.1.0 is the *(something)*.
      * `Collectors::RecursiveSum` is introduced.
      * `system.status` command: now the reporter node and its internal name is reported as a part of response body.
      * `system.statistics.object.count` command is now available. It is used by command line utilities internally.
+     * `system.statistics.object.count.per-volume` command is now available. It is useful to confirm equivalence of replicas.
      * `system.absorb-data` command is now available. It is used by command line utilities internally.
    * Message format:
      * `targetRole` field is introduced to the envelope.
@@ -64,9 +73,6 @@ The most important topic on this release Droonga 1.1.0 is the *(something)*.
    * Query parameters for `/droonga/*` endpoints are used as the message body.
  * [Drndump 1.0.1][drndump]
    * Becomes modulable. You can use internal libraries for other products.
-   * Supports new `@subscribe-until` directive, for subscription type commands like `dump`.
-     You can unsubscribe the next request following to the directive automatically with given timeout, like:
-     `#@subscribe-until 10s`
  * [Drntest 1.2.0][drntest]
    * Improvements
      * Supported new directives to activate/diactivate completion and validation of messages.
@@ -74,6 +80,9 @@ The most important topic on this release Droonga 1.1.0 is the *(something)*.
          Required fields of request messages are automatically completed by default.
        * `#@enable_validation` and `#@disable_validation` controls validation of request messages.
          Messages are validated by default.
+       * `#@subscribe-until` directive, for subscription type commands like `dump`.
+         You can unsubscribe the next request following to the directive automatically with given timeout, like:
+         `#@subscribe-until 10s`
      * A `NO RESPONSE` result is now returned immediately, for a stalled engine process.
      * Invalid format responses for Groonga commands are now ignored.
  * [Droonga-client-ruby 0.2.1][droonga-client-ruby]
@@ -101,7 +110,7 @@ The most important topic on this release Droonga 1.1.0 is the *(something)*.
 ## Conclusion
 
  * Droonga 1.1.0 has been released!
- * (TBD: TODO summarize this release)
+ * Now you can add new replica to the cluster without any downtime.
  * 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!
-------------- next part --------------
HTML����������������������������...
Download 



More information about the Groonga-commit mailing list
Zurück zum Archiv-Index