⚠️ BREAKING CHANGE: Index meta file format change.You need to use stored_fields = (empty value) to make all fields non-stored (i.e.
⚠️ BREAKING CHANGE: All full-text fields are now stored by default. To retain the previous behaviour you can use search option cutoff=0, which makes total_relation always eq. 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. The downside is that it affects total_found in SHOW META and hits.total in JSON output. Manticore now doesn't spend time and resources processing data you don't need in the result set which will be returned. You can now use Manticore even in cases not having anything to do with full-text search.įast fetching for attributes backed by Manticore Columnar Library: queries like select * from are now much faster than previously, especially if there are many fields in the schema. Having at least one full-text field in a real-time/plain index is not mandatory anymore. If you want to disable it make sure you add pseudo_sharding = 0 to section searchd of your Manticore configuration file. ⚠️ BREAKING CHANGE: Pseudo sharding is enabled by default. Previously you had to add Expect: header, now it's not needed. #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. lets you overcome max_packet_size and transfer batches much larger than the largest allowed value of max_packet_size (128MB), e.g.decreases response time (our tests showed 11% decrease for processing a 100MB batch).decreases peak RAM consumption, which lowers a chance of OOM.
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: 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). Support for Chunked transfer encoding in HTTP protocol.
#WISE MEMORY OPTIMIZER 3.5.2 CODE#
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. #720 Nested filters support in JSON protocol. New /cli endpoint for running SQL queries over HTTP even easier.įaster 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. Read-only mode: you can now specify listeners that process only read queries discarding any writes. The new functionality is supported in all operating systems except old Debian Stretch and Ubuntu Xenial. 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. 🔬 Support for Manticore Columnar Library 1.15.2, which enables Secondary indexes beta version.
0 kommentar(er)
