BloGroonga

2017-01-18

Groonga 6.1.4 has been released!

Groonga 6.1.4 has been released.

How to install in each environment: Install

Changes

It's a bug fix release of 6.1.3. It's recommend that Groonga 6.1.2 and 6.1.3 users upgrade to 6.1.4.

This release fixes an index search bug that index search may not return records that should be matched. This bug doesn't break index. You don't need to rebuild your indexes.

If you can't upgrade to 6.1.3, set the following environment variable:

GRN_II_CURSOR_SET_MIN_ENABLE=no

This is a workaround of this bug.

This release includes an improvements for index update performance. This isn't effective for normal use cases. This is effective for multiple column index for Mroonga. If you're using Mroonga's multiple column index, try this release.

Conclusions

Once again, we recommend that Groonga 6.1.2 and 6.1.3 users upgrade to 6.1.4.

Please refer to Release 6.1.4 about detailed changes since 6.1.3.

Then, let's go all out to search by Groonga!

2017-01-06

Groonga 6.1.3 has been released!

Groonga 6.1.3 has been released.

How to install in each environment: Install

Changes

It's a bug fix release of 6.1.2. It's recommend that Groonga 6.1.2 users upgrade to 6.1.3. This release fixes an inverted index related problems.

  • Reverted "Improved performance of updating inverted indexes in the worst case". It had reported error when key has multibyte character. This change was included in 6.1.2.

Conclusions

Once again, we recommend that Groonga 6.1.2 users upgrade to 6.1.3.

Please refer to Release 6.1.3 about detailed changes since 6.1.2.

Then, let's go all out to search by Groonga!

2016-12-31

Groonga 6.1.2 has been released!

Groonga 6.1.2 has been released!

How to install in each environment: Install

Changes

Here are important changes in this release:

  • [load] Supported to show {"n_loaded_records": N} in response
  • [load] Supported --output_ids yes parameter

[load] Supported to show {"n_loaded_records": N} in response

In this release, load command supports to show how many records are loaded in response.

Here is the example which shows number of loaded records.

{
  "header": {
    "return_code": 0,
    "start_time": 0.0,
    "elapsed_time": 0.0
  },
  "body": {
    "n_loaded_records": 2
  }
}

It shows that 2 records are loaded.

Note that n_loaded_records is supported by command version 3 or later.

[load] Supported --output_ids yes parameter

In this release, --output_ids yes paremeter is supported.

If --output_ids yes is specified, loaded record IDs(loaded_ids) are also returned. ID is 0 for record that is failed to add.

{
  "header": {
    "return_code": 0,
    "start_time": 0.0,
    "elapsed_time": 0.0
  },
  "body": {
    "n_loaded_records": 2,
    "loaded_ids": [
      1,
      0,
      2
    ]
  }
}

Note that --output_ids yes parameter is supported by command version 3 or later and it is not recommended to use --output_ids yes when you loads large number of records in the point of view of performance.

Conclusions

Please refer to Release 6.1.2 - 2016-12-31 about detailed changes since 6.1.1.

Then, let's go all out to search by Groonga!