Skip to content

⚠️ Version 0.9.0-beta

Pre-release
Pre-release
Compare
Choose a tag to compare
@ChillFish8 ChillFish8 released this 23 Jan 23:15
· 15 commits to master since this release
0.9.0-beta
79903fe
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Version 0.9.0-beta

This is a beta version/pre-release of version 0.9.0 so that people are to make use and test some of the nicer quality of life changes like the new schema conversion, more sane defaulting behaviour and synonym support.

This release won't have any documentation to go with it directly as technically it's a pre-release. That being said this is a breaking release and will require you you re-index your data and re-create schemas.

What's new

  • Synonym support is now added! Finally! My life is complete! I can Retire! On a more serious note yes it's added and can be adjusted using the /indexes/:index/synonyms endpoint via POST, GET and DELETE requests respectively. there's also a /indexes/:index/synonyms/clear DELETE endpoint which allows you to clear all synonyms. The syntax for adding synonyms is a semi-relation structure where you provide a list of strings in the format of <word>,<word>:<synonym>, <synonym>,<synonym> which will set all the words on the left of the : to have the given synonyms. This allows you to define synonyms fairly easy for related words e.g. iphone,apple,phone:apple,phone,iphone
  • All loaded stop words can be viewed via the /indexes/:index/stopwords GET endpoint.
  • Returned documents are now converted to be in line with the defined schema i.e fields with multi set to false will be returned as single values and if no value is set it will be returned as null rather than just missing the field entirely.
  • You can now mark fields as required which will cause lnx to reject any documents that are missing required fields (this will also reject fields that are provided but have empty values i.e "foo": []

What's different

  • Fields now have a multi attribute to set them as being multi-value. If they're not multi-value but multiple values are provided, the system will take the last value in the provided array.
  • The fast attribute for fields are now a bool rather than single/multi this because generally, it was a bit confusing to users to know when they wanted single or when they wanted multi, now this is an internal thing and you only have to worry about saying if you want it to be a fast field or not.

What's fixed

  • lnx will now return an error if you try and sort by multi-value fields, this was a panic if you had the fast-field cardinality set correctly.

What's Changed

  • Improve schema validations and Query logic in #68
  • Implement schema conversion to returned docs and general improvements in #69
  • Cleanup query info, hint and add synonym support in #71

Full Changelog: 0.8.1...0.9.0-beta

Assets 2
Loading