Manticore Search 6.0.2-extra2

Manticore Search 6.0.2-extra2

Released: March 2 2023

Improvements

• Improve entrypoint.sh by checking the EXTRA flag on each call.

Manticore Search 6.0.2-extra

Manticore Search 6.0.2-extra

Released: Feb 27 2023

Improvements

• When running docker run ... indexer, it now also takes into account the EXTRA environment variable.

Manticore Search 6.0.2

Manticore Search 6.0.2

Released: Feb 10 2023

Bugfixes

• Issue #1024 crash 2 Crash / Segmentation Fault on Facet search with larger number of results
• ❗Issue #1029 - WARNING: Compiled-in value KNOWN_CREATE_SIZE (16) is less than measured (208). Consider to fix the value!
• ❗Issue #1032 - Manticore 6.0.0 plain index crashes
• ❗Issue #1033 - multiple distributed lost on daemon restart

Manticore Search 6.0.0

Manticore Search 6.0.0

Released: Feb 7 2023

Starting with this release, Manticore Search comes with Manticore Buddy, a sidecar daemon written in PHP that handles high-level functionality that does not require super low latency or high throughput. Manticore Buddy operates behind the scenes, and you may not even realize it is running. Although it is invisible to the end user, it was a significant challenge to make Manticore Buddy easily installable and compatible with the main C++-based daemon. This major change will allow the team to develop a wide range of new high-level features, such as shards orchestration, access control and authentication, and various integrations like mysqldump, DBeaver, Grafana mysql connector. For now it already handles SHOW QUERIES, BACKUP and Auto schema.

This release also includes more than 130 bug fixes and numerous features, many of which can be considered major.

Major Changes

• 🔬 Experimental: you can now execute Elasticsearch-compatible insert and replace JSON queries which enables using Manticore with tools like Logstash (version < 7.13), Filebeat and other tools from the Beats family. Enabled by default. You can disable it using SET GLOBAL ES_COMPAT=off.
• Support for Manticore Columnar Library 2.0.0 with numerous fixes and improvements in Secondary indexes. ⚠️ BREAKING CHANGE: Secondary indexes are ON by default as of this release. Make sure you do ALTER TABLE table_name REBUILD SECONDARY if you are upgrading from Manticore 5. See below for more details.
• Commit c436 Auto-schema: you can now skip creating a table, just insert the first document and Manticore will create the table automatically based on its fields. Read more about this in detail here. You can turn it on/off using searchd.auto_schema.
• Vast revamp of cost-based optimizer which lowers query response time in many cases.
  • Issue #1008 Parallelization performance estimate in CBO.
  • Issue #1014 CBO is now aware of secondary indexes and can act smarter.
  • Commit cef9 Encoding stats of columnar tables/fields are now stored in the meta data to help CBO make smarter decisions.
  • Commit 2b95 Added CBO hints for fine-tuning its behaviour.
• Telemetry: we are excited to announce the addition of telemetry in this release. This feature allows us to collect anonymous and depersonalized metrics that will help us improve the performance and user experience of our product. Rest assured, all data collected is completely anonymous and will not be linked to any personal information. This feature can be easily turned off in the settings if desired.
• Commit 5aaf ALTER TABLE table_name REBUILD SECONDARY to rebuild secondary indexes whenever you want, for example:
  • when you migrate from Manticore 5 to the newer version,
  • when you did UPDATE (i.e. in-place update, not replace) of an attribute in the index
• Issue #821 New tool manticore-backup for backing up and restoring Manticore instance
• SQL command BACKUP to do backups from inside Manticore.
• SQL command SHOW QUERIES as an easy way to see running queries rather than threads.
• Issue #551 SQL command KILL to kill a long-running SELECT.
• Dynamic max_matches for aggregation queries to increase accuracy and lower response time.

Minor changes

• Issue #822 SQL commands FREEZE/UNFREEZE to prepare a real-time/plain table for a backup.

• Commit c470 New settings accurate_aggregation and max_matches_increase_threshold for controlled aggregation accuracy.

• Issue #718 Support for signed negative 64-bit IDs. Note, you still can't use IDs > 2^63, but you can now use ids in the range of from -2^63 to 0.

• As we recently added support for secondary indexes, things became confusing as "index" could refer to a secondary index, a full-text index, or a plain/real-time index. To reduce confusion, we are renaming the latter to "table". The following SQL/command line commands are affected by this change. Their old versions are deprecated, but still functional:

  • index <table name> => table <table name>,
  • searchd -i / --index => searchd -t / --table,
  • SHOW INDEX STATUS => SHOW TABLE STATUS,
  • SHOW INDEX SETTINGS => SHOW TABLE SETTINGS,
  • FLUSH RTINDEX => FLUSH TABLE,
  • OPTIMIZE INDEX => OPTIMIZE TABLE,
  • ATTACH TABLE plain TO RTINDEX rt => ATTACH TABLE plain TO TABLE rt,
  • RELOAD INDEX => RELOAD TABLE,
  • RELOAD INDEXES => RELOAD TABLES.

  We are not planning to make the old forms obsolete, but to ensure compatibility with the documentation, we recommend changing the names in your application. What will be changed in a future release is the "index" to "table" rename in the output of various SQL and JSON commands.

• Queries with stateful UDFs are now forced to be executed in a single thread.

• Issue #1011 Refactoring of all related to time scheduling as a prerequisite for parallel chunks merging.

• ⚠️ BREAKING CHANGE: Columnar storage format has been changed. You need to rebuild those tables that have columnar attributes.

• ⚠️ BREAKING CHANGE: Secondary indexes file format has been changed, so if you are using secondary indexes for searching and have searchd.secondary_indexes = 1 in your configuration file, be aware that the new Manticore version will skip loading the tables that have secondary indexes. It's recommended to:

  • Before you upgrade change searchd.secondary_indexes to 0 in the configuration file.
  • Run the instance. Manticore will load up the tables with a warning.
  • Run ALTER TABLE <table name> REBUILD SECONDARY for each index to rebuild secondary indexes.

  If you are running a replication cluster, you'll need to run ALTER TABLE <table name> REBUILD SECONDARY on all the nodes or follow this instruction with just change: run the ALTER .. REBUILD SECONDARY instead of the OPTIMIZE.

• ⚠️ BREAKING CHANGE: The binlog version has been updated, so any binlogs from previous versions will not be replayed. It is important to ensure that Manticore Search is stopped cleanly during the upgrade process. This means that there should be no binlog files in /var/lib/manticore/binlog/ except for binlog.meta after stopping the previous instance.

• Issue #849 SHOW SETTINGS: helper command for manticore-backup.

• Issue #1007 SET GLOBAL CPUSTATS=1/0 turns on/off cpu time tracking; SHOW THREADS now doesn't show CPU statistics when the cpu time tracking is off.

• [Issue #100...

5.0.2-extra2

Release 5.0.2-extra2

Added possibility to run under non-root user (#22)

5.0.2-extra

• Manticore Columnar Library providing columnar storage and secondary indexes can be now enabled in the runtime. It will result in downloading the library and installing it. If you make /var/lib/manticore persistent the library will be downloaded only once.
• The base image was changed to Ubuntu Focal
• DAEMON_URL and MCL_URL build arguments so you can build packages of a specific version
• English, German and Russian languages morphology packages were aded to the image

Manticore Search 5.0.2

Manticore Search 5.0.2, May 30th 2022

• ❗Issue #791 - wrong stack size could cause a crash.

Manticore Search 5.0.0

Manticore Search 5.0.0, May 18th 2022

Release blogpost https://manticoresearch.com/blog/manticore-search-5-0-0/

Major new features

• 🔬 Support for Manticore Columnar Library 1.15.2, which enables Secondary indexes beta version. Building secondary indexes is on by default for plain and real-time columnar and row-wise indexes (if Manticore Columnar Library is in use), but to enable it for searching you need to set secondary_indexes = 1 either in your configuration file or using SET GLOBAL. The new functionality is supported in all operating systems except old Debian Stretch and Ubuntu Xenial.
• Read-only mode: you can now specify listeners that process only read queries discarding any writes.
• New /cli endpoint for running SQL queries over HTTP even easier.
• Faster bulk INSERT/REPLACE/DELETE via JSON over HTTP: previously you could provide multiple write commands via HTTP JSON protocol, but they were processed one by one, now they are handled as a single transaction.
• #720 Nested filters support in JSON protocol. Previously you couldn't code things like a=1 and (b=2 or c=3) in JSON: must (AND), should (OR) and must_not (NOT) worked only on the highest level. Now they can be nested.
• Support for Chunked transfer encoding in HTTP protocol. You can now use chunked transfer in your application to transfer large batches with lower resource consumption (since you don't need to calculate Content-Length). On the server's side Manticore now always processes incoming HTTP data in streaming fashion without waiting for the whole batch to be transferred as previously, which:
  • decreases peak RAM consumption, which lowers a chance of OOM
  • decreases response time (our tests showed 11% decrease for processing a 100MB batch)
  • lets you overcome max_packet_size and transfer batches much larger than the largest allowed value of max_packet_size (128MB), e.g. 1GB at once.
• #719 HTTP interface support of 100 Continue: now you can transfer large batches from curl (including curl libraries used by various programming languages) which by default does Expect: 100-continue and waits some time before actually sending the batch. Previously you had to add Expect: header, now it's not needed.
• • Pseudo sharding is enabled by default.
• Having at least one full-text field in a real-time/plain index is not mandatory anymore. You can now use Manticore even in cases not having anything to do with full-text search.
• Fast fetching for attributes backed by Manticore Columnar Library: queries like select * from <columnar table> are now much faster than previously, especially if there are many fields in the schema.
• ⚠️ BREAKING CHANGE: Implicit cutoff. Manticore now doesn't spend time and resources processing data you don't need in the result set which will be returned. The downside is that it affects total_found in SHOW META and hits.total in JSON output. It is now only accurate in case you see total_relation: eq while total_relation: gte means the actual number of matching documents is greater than the total_found value you've got. To retain the previous behaviour you can use search option cutoff=0, which makes total_relation always eq.
• ⚠️ BREAKING CHANGE: All full-text fields are now stored by default in plain indexes. You need to use stored_fields = (empty value) to make all fields non-stored (i.e. revert to the previous behaviour).
• #715 HTTP JSON supports search options.

Minor changes

• ⚠️ BREAKING CHANGE: Index meta file format change. Previously meta files (.meta, .sph) were in binary format, now it's just json. The new Manticore version will convert older indexes automatically, but:
  • you can get warning like WARNING: ... syntax error, unexpected TOK_IDENT
  • you won't be able to run the index with previous Manticore versions, make sure you have a backup
• ⚠️ BREAKING CHANGE: Session state support with help of HTTP keep-alive. This makes HTTP stateful when the client supports it too. For example, using the new /cli endpoint and HTTP keep-alive (which is on by default in all browsers) you can call SHOW META after SELECT and it will work the same way it works via mysql. Note, previously Connection: keep-alive HTTP header was supported too, but it only caused reusing the same connection. Since this version it also makes the session stateful.
• You can now specify columnar_attrs = * to define all your attributes as columnar in the plain mode which is useful in case the list is long.
• Faster replication SST
• ⚠️ BREAKING CHANGE: Replication protocol has been changed. If you are running a replication cluster, then when upgrading to Manticore 5 you need to:
  • stop all your nodes first cleanly
  • and then start the node which was stopped last with --new-cluster (run tool manticore_new_cluster in Linux).
  • read about restarting a cluster for more details.
• Replication improvements:
  • Faster SST
  • Noise resistance which can help in case of unstable network between replication nodes
  • Improved logging
• Security improvement: Manticore now listens on 127.0.0.1 instead of 0.0.0.0 in case no listen at all is specified in config. Even though in the default configuration which is shipped with Manticore Search the listen setting is specified and it's not typical to have a configuration with no listen at all, it's still possible. Previously Manticore would listen on 0.0.0.0 which is not secure, now it listens on 127.0.0.1 which is usually not exposed to the Internet.
• Faster aggregation over columnar attributes.
• Increased AVG() accuracy: previously Manticore used float internally for aggregations, now it uses double which increases the accuracy significantly.
• Improved support for JDBC MySQL driver.
• DEBUG malloc_stats support for jemalloc.
• optimize_cutoff is now available as a per-table setting which can be set when you CREATE or ALTER a table.
• ⚠️ BREAKING CHANGE: query_log_format is now sphinxql by default. If you are used to plain format you need to add query_log_format = plain to your configuration file.
• Significant memory consumption improvements: Manticore consumes significantly less RAM now in case of long and intensive insert/replace/optimize workload in case stored fields are used.
• shutdown_timeout default value was increased from 3 seconds to 60 seconds.
• Commit ffd0499d Support for Java mysql connector >= 6.0.3: in Java mysql connection 6.0.3 they changed the way they connect to mysql which broke compatibility with Manticore. The new behaviour is now supported.
• Commit 1da6dbec disabled saving a new disk chunk on loading an index (e.g. on searchd startup).
• Issue #746 Support for glibc >= 2.34.
• Issue #784 count 'VIP' connections separately from usual (non-VIP). Previously VIP connections were counted towards the max_connections limit, which could cause "maxed out" error for non-VIP connections. Now VIP connections are not counted towards the limit. Current number of VIP connections can be also seen in SHOW STATUS and status.
• ID can now be specified explicitly.

⚠️ Other minor breaking changes

• ⚠️ BM25F formula has been slightly updated to improve search relevance. This only affects search results in case you use function BM25F(), it doesn't change behaviour ...

Manticore Search 4.2.0

Manticore Search 4.2.0, Dec 23rd 2021

Release blogpost

Major new features

• Pseudo-sharding support for real-time indexes and full-text queries. In previous release we added limited pseudo sharding support. Starting from this version you can get all benefits of the pseudo sharding and your multi-core processor by just enabling searchd.pseudo_sharding. The coolest thing is that you don't need to do anything with your indexes or queries for that, just enable it and if you have free CPU it will be used to lower your response time. It supports plain and real-time indexes for full-text, filtering and analytical queries. For example, here is how enabling pseudo sharding can make most queries' response time in average about 10x lower on Hacker news curated comments dataset multiplied 100 times (116 million docs in a plain index).

• Debian Bullseye is now supported.

• PQ transactions are now atomic and isolated. Previously PQ transactions support was limited. It enables much faster REPLACE into PQ, especially when you need to replace a lot of rules at once. Performance details:

Previous version 4.0.2

It takes 48 seconds to insert 1M PQ rules and 406 seconds to REPLACE just 40K in 10K batches.

root@perf3 ~ # mysql -P9306 -h0 -e "drop table if exists pq; create table pq (f text, f2 text, j json, s string) type='percolate';"; date; for m in `seq 1 1000`; do (echo -n "insert into pq (id,query,filters,tags) values "; for n in `seq 1 1000`; do echo -n "(0,'@f (cat | ( angry dog ) | (cute mouse)) @f2 def', 'j.json.language=\"en\"', '{\"tag1\":\"tag1\",\"tag2\":\"tag2\"}')"; [ $n != 1000 ] && echo -n ","; done; echo ";")|mysql -P9306 -h0; done; date; mysql -P9306 -h0 -e "select count(*) from pq"

Wed Dec 22 10:24:30 AM CET 2021
Wed Dec 22 10:25:18 AM CET 2021
+----------+
| count(*) |
+----------+
|  1000000 |
+----------+

root@perf3 ~ # date; (echo "begin;"; for offset in `seq 0 10000 30000`; do n=0; echo "replace into pq (id,query,filters,tags) values "; for id in `mysql -P9306 -h0 -NB -e "select id from pq limit $offset, 10000 option max_matches=1000000"`; do echo "($id,'@f (tiger | ( angry bear ) | (cute panda)) @f2 def', 'j.json.language=\"de\"', '{\"tag1\":\"tag1\",\"tag2\":\"tag2\"}')"; n=$((n+1)); [ $n != 10000 ] && echo -n ","; done; echo ";"; done; echo "commit;") > /tmp/replace.sql; date
Wed Dec 22 10:26:23 AM CET 2021
Wed Dec 22 10:26:27 AM CET 2021
root@perf3 ~ # time mysql -P9306 -h0 < /tmp/replace.sql

real	6m46.195s
user	0m0.035s
sys	0m0.008s

Previous version 4.2.0

It takes 34 seconds to insert 1M PQ rules and 23 seconds to REPLACE them in 10K batches.

root@perf3 ~ # mysql -P9306 -h0 -e "drop table if exists pq; create table pq (f text, f2 text, j json, s string) type='percolate';"; date; for m in `seq 1 1000`; do (echo -n "insert into pq (id,query,filters,tags) values "; for n in `seq 1 1000`; do echo -n "(0,'@f (cat | ( angry dog ) | (cute mouse)) @f2 def', 'j.json.language=\"en\"', '{\"tag1\":\"tag1\",\"tag2\":\"tag2\"}')"; [ $n != 1000 ] && echo -n ","; done; echo ";")|mysql -P9306 -h0; done; date; mysql -P9306 -h0 -e "select count(*) from pq"

Wed Dec 22 10:06:38 AM CET 2021
Wed Dec 22 10:07:12 AM CET 2021
+----------+
| count(*) |
+----------+
|  1000000 |
+----------+

root@perf3 ~ # date; (echo "begin;"; for offset in `seq 0 10000 990000`; do n=0; echo "replace into pq (id,query,filters,tags) values "; for id in `mysql -P9306 -h0 -NB -e "select id from pq limit $offset, 10000 option max_matches=1000000"`; do echo "($id,'@f (tiger | ( angry bear ) | (cute panda)) @f2 def', 'j.json.language=\"de\"', '{\"tag1\":\"tag1\",\"tag2\":\"tag2\"}')"; n=$((n+1)); [ $n != 10000 ] && echo -n ","; done; echo ";"; done; echo "commit;") > /tmp/replace.sql; date
Wed Dec 22 10:12:31 AM CET 2021
Wed Dec 22 10:14:00 AM CET 2021
root@perf3 ~ # time mysql -P9306 -h0 < /tmp/replace.sql

real	0m23.248s
user	0m0.891s
sys	0m0.047s

Minor changes

• optimize_cutoff is now available as a configuration option in section searchd. It's useful when you want to limit the RT chunks count in all your indexes to a particular number globally.
• Commit 00874743 accurate count(distinct ...) and FACET ... distinct over several local physical indexes (real-time/plain) with identical fields set/order.
• PR #598 bigint support for YEAR() and other timestamp functions.
• Commit 8e85d4bc Adaptive rt_mem_limit. Previously Manticore Search was collecting exactly up to rt_mem_limit of data before saving a new disk chunk to disk, and while saving was still collecting up to 10% more (aka double-buffer) to minimize possible insert suspension. If that limit was also exhausted, adding new documents was blocked until the disk chunk was fully saved to disk. The new adaptive limit is built on the fact that we have auto-optimize now, so it's not a big deal if disk chunks do not fully respect rt_mem_limit and start flushing a disk chunk earlier. So, now we collect up to 50% of rt_mem_limit and save that as a disk chunk. Upon saving we look at the statistics (how much we've saved, how many new documents have arrived while saving) and recalculate the initial rate which will be used next time. For example, if we saved 90 million documents, and another 10 million docs arrived while saving, the rate is 90%, so we know that next time we can collect up to 90% of rt_mem_limit before starting flushing another disk chunk. The rate value is calculated automatically from 33.3% to 95%.
• Issue #628 unpack_zlib for PostgreSQL source. Thank you, Dmitry Voronin for the contribution.
• Commit 6d54cf2b indexer -v and --version. Previously you could still see indexer's version, but -v/--version were not supported.
• Issue #662 infinit mlock limit by default when Manticore is started via systemd.
• Commit 63c8cd05 spinlock -> op queue for coro rwlock.
• Commit 41130ce3 environment variable MANTICORE_TRACK_RT_ERRORS useful for debugging RT segments corruption.

Breaking changes

• Binlog version was increased, binlog from previous version won't be replayed, so make sure you stop Manticore Search cleanly during upgrade: no binlog files should be in /var/lib/manticore/binlog/ except binlog.meta after stopping the previous instance.
• Commit 3f659f36 new column "chain" in show threads option format=all. It shows stack of some task info tickets, most useful for profiling needs, so if you are parsing show threads output be aware of the new column.
• searchd.workers was obsoleted since 3.5.0, now it's deprecated, if you still have it in your configuration file it will trigger a warning on start. Manticore Search will start, but with a warning.

Bugfixes

• ❗Issue #650 Manticore 4.0.2 slower than Manticore 3.6.3. 4.0.2 was faster than previous versions in terms of bulk inserts, but significantly slower for single document inserts. It's been fixed in 4.2.0.
• ❗Commit 22f4141b RT index could get corrupted under intensive REPLACE load, or it could crash
• Commit 03be91e4 fixed average at merging groupers and group N sorter; fixed merge of aggregates
• Commit 2ea575d3 indextool --check could crash
• Commit 7ec76d4a RAM exhaustion issue caused by UPDATEs
• Commit 658a727e daemon could hang on INSER...

Manticore Search 3.6.0

Version 3.6.0, May 3rd 2021

Maintenance release before Manticore 4

Major new features

• Support for Manticore Columnar Library for plain indexes. New setting columnar_attrs for plain indexes
• Support for Ukrainian Lemmatizer
• Fully revised histograms. When building an index Manticore also builds histograms for each field in it, which it then uses for faster filtering. In 3.6.0 the algorithm was fully revised and you can get a higher performance if you have a lot of data and do a lot of filtering.

Minor changes

• tool manticore_new_cluster [--force] useful for restarting a replication cluster via systemd
• --drop-src for indexer --merge
• new mode blend_mode='trim_all'
• added support for escaping JSON path with backticks
• indextool --check can work in RT mode
• FORCE/IGNORE INDEX(id) for SELECT/UPDATE
• chunk id for a merged disk chunk is now unique
• indextool --check-disk-chunk CHUNK_NAME

Optimizations

• faster JSON parsing, our tests show 3-4% lower latency on queries like WHERE json.a = 1
• non-documented command DEBUG SPLIT as a prerequisite for automatic sharding/rebalancing

Bugfixes

• #584 - inaccurate and unstable FACET results
• #506 - Strange behavior when using MATCH: those who suffer from this issue need to rebuild the index as the problem was on the phase of building an index
• #387 - intermittent core dump when running query with SNIPPET() function
• Stack optimizations useful for processing complex queries:
  • #469 - SELECT results in CRASH DUMP
  • e8420cc7 - stack size detection for filter trees
• #461 - Update using the IN condition does not take effect correctly
• #464 - SHOW STATUS immediately after CALL PQ returns - #481 - Fixed static binary build
• #502 - bug in multi-queries
• #514 - Unable to use unusual names for columns when use 'create table'
• d1dbe771 - daemon crash on replay binlog with update of string attribute; set binlog version to 10
• 775d0555 - fixed expression stack frame detection runtime (test 207)
• 4795dc49 - percolate index filter and tags were empty for empty stored query (test 369)
• c3f0bf4d - breaks of replication SST flow at network with long latency and high error rate (different data centers replication); updated replication command version to 1.03
• ba2d6619 - joiner lock cluster on write operations after join into cluster (test 385)
• de4dcb9f - wildcards matching with exact modifier (test 321)
• 6524fc6a - docid checkpoints vs docstore
• f4ab83c2 - Inconsistent indexer behavior when parsing invalid xml
• 7b727e22 - Stored percolate query with NOTNEAR runs forever (test 349)
• 812dab74 - wrong weight for phrase starting with wildcard
• 1771afc6 - percolate query with wildcards generate terms without payload on matching causes interleaved hits and breaks matching (test 417)
• aa0d8c2b - fixed calculation of 'total' in case of parallelized query
• 18d81b3c - crash in Windows with multiple concurrent sessions at daemon
• 84432f23 - some index settings could not be replicated
• 93411fe6 - On high rate of adding new events netloop sometimes freeze because of atomic 'kick' event being processed once for several events a time and loosing actual actions from them
  status of the query, not the server status
• d805fc12 - New flushed disk chunk might be lost on commit
• 63cbf008 - inaccurate 'net_read' in profiler
• f5379bb2 - Percolate issue with arabic (right to left texts)
• 49eeb420 - id not picked correctly on duplicate column name
• refactoring of network events to fix a crash in rare cases
• e8420cc7 fix in indextool --dumpheader
• ff716353 - TRUNCATE WITH RECONFIGURE worked wrong with stored fields

Breaking changes:

• New binlog format: you need to make a clean stop of Manticore before upgrading
• Index format slightly changes: the new version can read you existing indexes fine, but if you decide to downgrade from 3.6.0 to an older version the newer indexes will be unreadable
• Replication format change: don't replicate from an older version to 3.6.0 and vice versa, switch to the new version on all your nodes at once
• reverse_scan is deprecated. Make sure you don't use this option in your queries since 3.6.0 since they will fail otherwise
• As of this release we don't provide builds for RHEL6, Debian Jessie and Ubuntu Trusty any more. If it's mission critical for you to have them supported contact us

Deprecations

• No more implicit sorting by id. If you rely on it make sure to update your queries accordingly
• Search option reverse_scan has been deprecated