Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add an article for Groonga CloudSearch 1.2.0.
- Loading branch information
Showing
1 changed file
with
39 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,39 @@ | ||
| --- | ||
| title: Groonga CloudSearch 1.2.0 is out! | ||
| 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](/). | ||
|
|
||
| ### What's new? | ||
|
|
||
| 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. | ||
|
|
||
| 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> | ||
|
|
||
| #### 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. | ||
|
|
||
| #### Easy configuration | ||
|
|
||
| Groonga CloudSearch now includes following commands: | ||
|
|
||
| * gcs-create-domain | ||
| * gcs-delete-domain | ||
| * gcs-describe-domain | ||
| * gcs-configure-field (create, update, and delete) | ||
| * gcs-configure-text-options (for synonyms) | ||
| * 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. | ||
|
|
||
| ### 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. |