# Typesense Guide for v0.21.0
The guide section of the documentation walks you through how to use Typesense
v0.21.0 in different scenarios. Use the links on the side navigation bar to get to the appropriate section you're looking for.
For a detailed dive into the Typesense API, refer to our API documentation.
# What's new
This release contains new features, performance improvements and important bug fixes.
# New Features
- Geosearch: Use the
geopointdata type to index locations, filter and sort on them. We support filtering on records within a given radius and as well as within any arbitrarily defined geo polygon.
- Wrap literal strings in
filter_byvalues using backticks to ensure that the commas in filter values don't get parsed as a list separator. Example:
filter_by: primary_artist_name:=[`Apple, Inc.`]
- Support exclude / not equals operator for filtering string and boolean facets. Example:
filter_by=author:!= JK Rowling
- Ability to turn off prefix search on a per field basis. For example, if you are querying 3 fields and want to enable
prefix searching only on the first field, use
?prefix=true,false,false. The order should match the order in
- You can now highlight fields that you don't query for. Use
?highlight_fields=titleto specify a custom list of fields that should be highlighted.
- Increased maximum supported length of HTTP query string to 4K characters: if you wish to send larger payloads, use the multi-search end-point.
nullvalues for optional fields (opens new window).
- Support for indexing pre-segmented text: you can now index content from any logographic language into Typesense
if you are able to segment / split the text into space-separated words yourself before indexing and querying. You
should also set
- If you have some overrides defined but want to disable all of them during query time, you can now do that
# Bug Fixes
- Fixed some edge cases with typo correction not finding the correct matches
- Ensure that exact matches are ranked above others (opens new window).
?prioritize_exact_match=falseto disable this behavior.
collections:*API key permission which was not previously being recognized by the authentication engine.
- Fixed float facets being displayed with imprecise precision when displayed as string.
- There is a change in the
upsertbehavior to conform to existing popular conventions: The upsert action now requires the whole document to be sent for indexing. If you wish to update part of a document, use the
This documentation itself is open source. If you find any issues, click on the Edit page button at the bottom of the page and send us a Pull Request.