goriak changelog

Changelog History

• v3.2.4 Changes

  December 18, 2018

  🛠 This release contains #63 which adds a bugfix to SetJSON() and Secondary Indexes (2i) when passing a pointer to a value to SetJSON(), before this fix goriak would silently skip adding the value to the index.

  Thanks to @Shkurpylo for finding and fixing this bug.

• v3.2.3

  July 26, 2018

• v3.2.2

  July 26, 2018

• v3.2.1 Changes

  March 18, 2017

  🛠 Fixes issue in AllKeys() caused by riak-go-client 1.9.0 not being backwards compatible with 1.8.0 or earlier. 1.9.0 of riak-go-client is now required.

• v3.2.0 Changes

  February 15, 2017

  ✅ The main new functionality in v3.2.0 is the addition of middleware. The middleware functionality is a test and so far only a read-only RunMiddleware is available. This middleware enables you to easily gather statistics about how fast the executed commands are, and which keys you fetch the most, among other things.

  If the middleware functionality is a success RunMiddleware will be enabled on all commands, and more middleware types can be added, to allow things such as pre and post command rewriting.

• v3.1.1 Changes

  February 09, 2017

  🛠 Bugfixes

  • 🛠 Fixes issue with conflict resolution in GetRaw().

• v3.1.0 Changes

  February 07, 2017

  🆕 News

  • 🆕 New command: KeysInIndexRange()
  • 🔒 More advanced ConnectOpts with support for Riak security and password based authentication.

• v3.0.0 Changes

  January 27, 2017

  💥 Breaking changes

  • 🏗 The API builder now returns a pointer to the builder object, instead of the whole object. (Command -> *Command.
  • 🏗 The query builder has been split into multiple different types. Generally the API is still the same, but the order of which the builder methods are available is more strict. The most specific command such as GetRaw, Set, and KeysInIndex must go directly after Bucket().
  • 🚚 Sets without any value will no longer be saved (and the empty placeholder value has been removed). This means that empty Sets no longer can be saved, and that Riak will return NotFound if you try to get the object afterwards. Empty values are still not returned from Values() or Strings(), which means that your code will not break if you had values in the Set from an earlier version of goriak.

• v3.0.0-beta1

  January 27, 2017