Skip to content

πŸš€ Version 0.7.0

Compare
Choose a tag to compare
@ChillFish8 ChillFish8 released this 21 Nov 16:06
· 37 commits to master since this release
0c77ccf

Version 0.7.0

0.7 brings with it a lot of quality of life changes, bug fixes and features. Unlike previous releases, this has backwards compatibility with 0.6.x systems.

What's New

  • Sentence suggestion endpoint:
    This gives you the ability to suggest sentences based on the corpus data, although this does not guarantee that the corrections will be correct according to the language, instead it will correct words to inline with sentences within the corpus data itself. (This is not a Grammarly system)
  • Multi-Field term handling:
    This allows you to now specify multiple fields for a single term by passing an array of field names rather than a single string on the term query kind.
  • Sensible Defaults:
    This now allows you to skip the writer_threads and writer_buffer fields should you choose and a sensible set of defaults will be calculated based on your current system's specs. This typically will allocate either n number of threads where n is the number of logical CPU cores or 8 is the absolute max. The writer buffer is generally going to be 10% of your total memory or the bare minimum buffer size for the number of threads, whatever is higher.
  • New Allocator:
    We now use MiMalloc allocator which not only means performance consistency across operating systems and containers but also adds a slight boost to performance.
  • Auto Commit:
    You can now set an auto_commit value on an index in seconds determining how much time no more operations be submitted should elapse before lnx automatically begins processing and committing documents. If this value is 0 (default) this is disabled.

What's Fixed

  • Index frequencies now save properly:
    The bug where index frequencies were not correctly being persisted to and from disk has been fixed.
  • lnx no longer uses 100% of one core per index:
    Before for every index or more specifically writer-actor, there was it would max that given thread out due to an infinite loop of checking the channels without blocking.

Full Changelog: 0.6.2...0.7.0