YUKI Hiroshi
null+****@clear*****
Fri Dec 7 18:51:55 JST 2012
YUKI Hiroshi 2012-12-07 18:51:55 +0900 (Fri, 07 Dec 2012) New Revision: 76ff8ec2f4be446ceb98cc2b3cf1e9866736ed19 https://github.com/groonga/gcs.groonga.org/commit/76ff8ec2f4be446ceb98cc2b3cf1e9866736ed19 Log: Add a blog post for 1.5.0 (and new roadmap) Added files: _posts/2012-12-26-1.5.0-release.md Added: _posts/2012-12-26-1.5.0-release.md (+82 -0) 100644 =================================================================== --- /dev/null +++ _posts/2012-12-26-1.5.0-release.md 2012-12-07 18:51:55 +0900 (945a0ed) @@ -0,0 +1,82 @@ +--- +title: Groonga CloudSearch 1.5.0 and Groonga CloudSearch Console 1.2.0 is out, and new roadmap +layout: post +description: We've shipped Groonga CloudSearch version 1.5.0 and Groonga CloudSearch Console 1.2.0. New features come with the release, and there is our new roadmap. +--- + +Today, we've shipped Groonga CloudSearch version 1.5.0 and Groonga CloudSearch +Console 1.2.0. You can download the packages and read the tutorial on +[the home page of this project site](/). + +### What's new? : Groonga CloudSearch + +#### Better compatibility to the Amazon CloudSearch + + * "DocService/Endpoint" and "SearchService/Endpoint" disappear from domain + statuses. You have to guess endpoints from the "arn" or other informations. + * "DefineIndexField" never merges newly specified options with previously + defined options. (In other words, now "DefineIndexField" always cleared old + options at old versions.) + +#### CLI tool changes + +Now `gcs-configure-fields` command becomes more compatible to `cs-configure-fields`. +Existing field options are always cleared, so you have to set multiple field +options at once. For this change, now the command accepts multiple "--option" +options, like: + + $ gcs-configure-fields -d domain --name field --type literal --option search result + +or + + $ gcs-configure-fields -d domain --name field --type literal --option search --option result + +#### Changes as a daemon + +Because no API returns any information including actual host name, "--base-host" +command line option for bin/gcs and GCS_BASE_HOST environment variable are now +obsolete. You don't need to give a base host name of the server to Groonga +CloudSearch processes anymore. + +#### Better security + +Now Groonga CloudSearch creates the directory to store data with the permission +0700 (full access by author, otherwise no access). If you use old versions of +Groonga CloudSearch, you should set the permission of the data directory +(~gcs/.gcs, ~/.gcs, and so on) to 0700 to the data directory +by the `chmod` command. + +### What's new? : Groonga CloudSearch Console + +#### Better authentication + +Groonga CloudSearch Console now activates BASIC Auth always. So it asks you to +register account name and password for the administration user on the initial +access. The web console can't be accessed without authentication anymore. + +#### Flexible "--endpoint" option + +Simple host name is now acceptable for the "--endpoint" option (and +GCS_CONSOLE_ENDPOINT environment variable) like "--endpoint gcs-console.example.com:7575". +In old versions, you always had to specify full URL like "http://gcs-console.example.com:7575". + +### New roadmap + +Now we are planning to suspend this project and concentrate human resources to the +[fluent-plugin-groonga project](http://b.hatena.ne.jp/entry/s/github.com/groonga/fluent-plugin-groonga) +for scalable backend based on groonga. After that, we'll be back and work to +improve Groonga CloudSearch with scalable backends. + +Currently Groonga CloudSearch doesn't support default value, source attribute, +and more features of Amazon CloudSearch. We have to re-construct the database +layer of Groonga CloudSearch to support these features. + +On the other hand, now groonga project has started a search system based on +scalable backends, with fluentd. It is the most important feature of Amazon +CondSearch but not supported by Groonga CloudSearch. + +Because both changes require many many codes around the database layer. We'll +need to rewrite codes for the scalable backends in the feature, even if we now +implement default value and other features. So we've decided to suspend +this Groonga CloudSearch project for a while and concentrate development +resources to the scalable backend. -------------- next part -------------- HTML����������������������������...Download