Hiroshi Hatake
null+****@clear*****
Fri Oct 28 16:12:23 JST 2016
Hiroshi Hatake 2016-10-28 16:12:23 +0900 (Fri, 28 Oct 2016) New Revision: 97b43d1d46e64e1a438812ad6c553b70e987e058 https://github.com/groonga/groonga.org/commit/97b43d1d46e64e1a438812ad6c553b70e987e058 Merged 990b1e5: Merge pull request #32 from cosmo0920/blog-en-6.1.0 Message: blog en: Add 6.1.0 article Added files: en/_posts/2016-10-29-groonga-6.1.0.md Added: en/_posts/2016-10-29-groonga-6.1.0.md (+56 -0) 100644 =================================================================== --- /dev/null +++ en/_posts/2016-10-29-groonga-6.1.0.md 2016-10-28 16:12:23 +0900 (e5a6b12) @@ -0,0 +1,56 @@ +--- +layout: post.en +title: Groonga 6.1.0 has been released! +description: Groonga 6.1.0 has been released! +published: false +--- + +## Groonga 6.1.0 has been released! + +[Groonga 6.1.0](/docs/news.html#release-6-1-0) has been released! + +How to install in each environment: [Install](/docs/install.html) + +In this release, documents about index columns has been added. Using this column type makes reducing memory usage. + +### Changes + +Here are important changes in this release: + +* Supported to sort load table names by key instead of ID to make output stable +* Added document about index columns + +#### Supported to sort load table names by key instead of ID to make output stable + +Before this release, dump command result of tables had been sorted by ID. Thus, when changin schema by adding and removing tables, it sometimes happens that a result of dumping database differs from without changing schema database. (Even if both of final difinitions are same.) This is not preferable behavior to compare dumping results. + +Then, in this release, dumping results are output to be sorted by table name. When they contain reference type columns, it will be taken into consideration. This is incompatible change but it makes easy to compare result of dump command. + +#### Added document about index columns + +In this release, documents added about small/medium index columns. This feature had been implemented in eariler version, but it had been missing its concrete usage document. + +Then, in this time, we describe its usage. This method can apply indexing target to be reasonably small within data saved in database. If you make a good use of this feature, it makes reducing memory usage. There are two ways to use it. + +* small index column +* medium index column + +Small index column can use when this column usage will not reach 1 billion records. It will reduce memory consumption by 1/256 compared with default index column's usage. +Fot example, specify `COLUMN_INDEX|INDEX_SMALL` in `flags` parameter as follows: + + column_create --table Ages --name people_age_small_index --flags COLUMN_INDEX|INDEX_SMALL --type People --source age + +It can apply when number of `People` table records is at most a few million. + + +When using medium size index column, it can be made number of 1 billion records which contains a fixed size scalar column. It reduces memory comsumption by 5/24 compared with default index column's usage. There are some constraints to apply this type of column. In more detail, please refer to the [Create a medium index column](/docs/reference/commands/column_create.html#create-a-medium-index-column) section. + +Fot example, specify `COLUMN_INDEX|INDEX_MEDIUM` in `flags` parameter as follows: + + column_create --table Ages --name people_age_medium_index --flags COLUMN_INDEX|INDEX_MEDIUM --type People --source age + +### Conclusions + +Please refer to [Release 6.1.0 - 2016-10-29](/docs/news.html#release-6-1-0) about detailed changes since 6.0.9. + +Then, let's go all out to search by Groonga! -------------- next part -------------- HTML����������������������������...Download