[Groonga-commit] groonga/gcs.groonga.org [gh-pages] Update release announcement of 1.2.0

Zurück zum Archiv-Index

YUKI Hiroshi null+****@clear*****
Mon Aug 27 14:46:22 JST 2012


YUKI Hiroshi	2012-08-27 14:46:22 +0900 (Mon, 27 Aug 2012)

  New Revision: de50f50619803c305b1f489adaf00dd9b73e2d9e
  https://github.com/groonga/gcs.groonga.org/commit/de50f50619803c305b1f489adaf00dd9b73e2d9e

  Log:
    Update release announcement of 1.2.0

  Modified files:
    _posts/2012-08-29-1.2.0-release.md

  Modified: _posts/2012-08-29-1.2.0-release.md (+34 -7)
===================================================================
--- _posts/2012-08-29-1.2.0-release.md    2012-08-23 18:49:08 +0900 (7a36e7b)
+++ _posts/2012-08-29-1.2.0-release.md    2012-08-27 14:46:22 +0900 (806f18f)
@@ -4,21 +4,45 @@ layout: post
 description: We've shipped Groonga CloudSearch version 1.2.0. New features come with the release!
 ---
 
-Today, we've shipped Groonga CloudSearch version 1.2.0. You can download the package and read the tutorial on [the home page of this project site](/).
+Today, we've shipped Groonga CloudSearch version 1.2.0. You can download
+the package and read the tutorial on [the home page of this project site](/).
 
 ### What's new?
 
-Groonga CloudSearch 1.2.0 includes many many improvements, and they can be described as following three topics.
+Groonga CloudSearch 1.2.0 includes many many improvements, and they can be
+described as following three topics.
 
 #### Becomes safer
 
-Now you can deploy Groonga CloudSearch to a public server safely. A search domain has its own unique ID. It guards a public Groonga CloudSearch server from unexpected accesses by any third person, because you have to access to your server with unique endpoints. Moreover the Configuration API (and the dashboard) became accessible only from privileged networks ("127.0.0.0/8" by default) which are specified by a command line parameter for the "gcs" command. No one except you can configure your Groonga CloudSearch server anymore.
+Simple access-control mechanism is now available, so you can deploy Groonga
+CloudSearch to a public server safely.
 
-By the way, you need to re-create the database before running Groonga CloudSearch 1.2.0. Run following command to clear the database: <kbd>rm -rf ~/.gcs</kbd>
+ * A search domain has its own unique ID.
+   It guards a public Groonga CloudSearch server from unexpected accesses
+   by any third person, because you have to access to your server with
+   unique endpoints.
+ * The Configuration API (and the dashboard) became accessible only from
+   privileged networks ("127.0.0.0/8" by default) which are specified by
+   a command line parameter for the "gcs" command. No one except you can
+   configure your Groonga CloudSearch server anymore.
+
+For the first change, you need to re-create the whole database before running
+Groonga CloudSearch 1.2.0.
+Run following command to clear the database: <kbd>rm -rf ~/.gcs</kbd>
 
 #### Facet
 
-You can store multiple values to an index field, and set the field to "facet returnable". Then you can get a facet information with a search result specifying the "facet" URL parameter, and you can use the result for a new search condition via the "bq" URL parameter. For example, if you have a literal field "tags", then <code>bq=tags:'science'</code> will return a search result including documents which have "science" as a value of its "tags" field.
+You can store multiple values to an index field, and set the field to
+"facet returnable".
+Then you can get a facet information with a part of a search result specifying
+the "facet" URL parameter, and you can use the result for a new search
+condition via the "bq" URL parameter.
+For example, if you have a literal field "tags", then
+<code>bq=tags:'science'</code> will return a search result including
+documents which have "science" as a member of its "tags" field.
+
+As above, Groonga CloudSearch 1.2.0 supports "bq" (complex queries), except
+the "not" operator.
 
 #### Easy configuration
 
@@ -32,8 +56,11 @@ Groonga CloudSearch now includes following commands:
  * gcs-configure-default-search-field (Groonga CloudSearch's extension)
  * gcs-post-sdf
 
-So, you can setup your search domains only with command line tools. You don't have to use the configuration API via HTTP anymore, for basic usecases.
+So, you can setup your search domains only with command line tools.
+You don't have to use the configuration API via HTTP anymore, for basic
+usecases.
 
 ### Sample implementation
 
-[Norema search (node reference manual search)](https://github.com/nroonga/norema) is now downloadable, it's an example application of Groonga CloudSearch. It will help you to build Web applications with Groonga CloudSearch.
+[Norema search (node reference manual search)](https://github.com/nroonga/norema) is now downloadable, it's an example application of Groonga CloudSearch.
+It will help you to build Web applications with Groonga CloudSearch.
-------------- next part --------------
HTML����������������������������...
Download 



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