Releases: RediSearch/redisearch-go
Version 2.1.1
Version 2.1.0
Changes
- Added support for hash_indexing_failures on Info() wrapper (#107)
- Added example to demonstrate use georadius. (#104)
- Added support for FT._LIST (#103)
- Added support for SLOP (#97)
- Add index_type JSON (#111)
- Add AS to fields and new test to check FT.SERCH after JSON.SET (#115)
- Support RETURN AS in SEARCH (#119)
- Support NOHL and SKIPINITIALSCAN tags on FT.CREATE (#125)
- Fix types not being recogized properly (#134))
- FILTER should not have white space from the EXCLUDE
(
(#145) - Support LOAD * in FT.AGGREGATE (#147)
- Change "Fields" to "Attributes" in info function (#153)
- Support Vector Similarity (#151)
- Support NOSTOPWORDS tag in FT.SEARCH command (#155)
Version 1.1.0
This Version follows the release of RediSearch 2.0.
RediSearch 2.0, marks the re-architecture of the way indices are kept in sync with the data. Instead of having to write data through the index (using the FT.ADD command), RediSearch will now follow the data written in hashes (HSET) and automatically index it.
Read it all in the following link.
Notwithstanding, this redisearch-go version will still work as expected on previous RediSearch versions (v1.4 and v1.6).
Thanks to @mixadior, @hualoqueros, @is-a-gamer and @shumin1027 for the contributing and reviews!
Version 2.0.2
This is a maintenance release for redisearch-go version compatible with RediSearch v 2.0.
Update urgency: Low
Features
Thank you to @is-a-gamer and @shumin1027 for the contributing!
Version 2.0.1
This PR follows the release of RediSearch 2.0.
Apart from the features already added on redisearch-go v2.0.0-M3, it includes:
Features
- Added support for Phonetic Matching (#92)
Bug Fixes
- Fixed tests internal method to retrieve module version (#84)
Thanks to @hualoqueros and @shumin1027 for the contributing and reviews!
2.0.0-M3
This PR follows the release of the third milestone in the development of RediSearch 2.0.
RediSearch 2.0, marks the re-architecture of the way indices are kept in sync with the data. Instead of having to write data through the index (using the FT.ADD command), RediSearch will now follow the data written in hashes (HSET) and automatically index it.
Read it all in the following link.
Notwithstanding, this redisearch-go version will still work as expected on previous RediSearch versions (v1.4 and v1.6).
Major updates:
- Added support for RediSearch v2.0 Index Definition (#81)
Enhancements:
- Added support for MAXTEXTFIELDS on FT.CREATE. (#83)
- Enabled Go Modules. (#78)
- Enabled INCR parameter in SUGADD (#74)
Fixes:
- Fixes Client.Delete() behaves opposite to spec. Deprecates Client.Delete() in favor of Cliente.DeleteDocument() for RediSearch >=v2.0 (#80)
Thanks @joshuaray and @TropicalPenguin for the contributing!
1.0.1
Enhancements:
- Added support for temporary index creation - #70
- Extended the examples folder and godoc with 3 examples on how to connect to the RediSearch Server. ( simplest way possible, with pool, and with SSL ) - #68
- Added support for the INFIELDS query parameter #72
Thanks @joshuaray for the contributing!
1.0.0
0.9.2
Enhancements:
- Added support for FT.SYNADD, FT.SYNUPDATE, and FT.SYNDUMP - #55
- Added support for FT.ADDHASH - #57
- Extended coverage
Bug Fixes:
- Fixed "NewSchema ignores opts arg" - #56
Thanks to: @dengliming for the contributing!
0.9.1
Enhancements:
- Added option to create clients with shared pool, via
NewClientFromPool(pool *redis.Pool, name string) *Client
- #51 - Added option to releases the resources used by the pool ( single, and multi-host ) via
Close()
- #51 - Added support for FT.CONFIG - #50
- Added support for FT.TAGVALS - #52
Thanks to: @dengliming and @ericfengchao for the contributing!