* 'devel' of https://github.com/arangodb/arangodb:
Enabled modification nodes in spliced subqueries again (#10499)
Set internal state to DONE when upstream is DONE (#10513)
Put the write into the IoContext. (#10511)
fix the default case, if we guess that we have structured post data, actually parse it. (#10508)
metricsfeature cleanup in unprepare (#10514)
Updated CHANGELOG (#10509)
Bug fix/input row serialization (#10502)
feature/metrics (#10423)
fix compilation on mac (#10505)
* Unified toVelocyPack of InputRow and AqlItemBlock. We can now velocypack any range within an AqlItemBlock as a new block.
* This is the fix required here. We now end exhausted false in initialize cursor. For some reason the other side checks this hard-coded value and if it is not the expected value it does ignore the send body ¯\_(ツ)_/¯
* Added test for range-based serialization
* late document materialization for view draft
* MaterializeType
* asserts and removed std::function
* std::map -> std::array
* Common search ast nodes code to a separate file
* Unit tests for create and clone a node
* js tests
* tmp unfinished
* Replace variables for late materialization
* Move removing
* Removed wrong clears
* Fixed variable replacement
* removed old tests (for separate materialization)
* check if late materialization arangosearch rule is enabled
* js test. added space
* moved a function to anonym namespace
* Subquery assert
* Review improvements
* Review improvements 2
* View node state to a separate var (microoptimization)
* Fixed index assert
* alignment
* C++ unit tests
* Fix bug in SubqueryEndExecutor
If a subquery was spliced, and did not get any input rows, the SubqueryEnd
executor still expected a relevant ShadowRow to be handed through, and ran into
an assertion (or otherwise crashed the server) if it didn't get one.
* Add regression test for SubqueryEndExecutor fix
* make replication timeouts configurable via startup options
The following options are available (for active failover
and master-slave replication):
--replication.connect-timeout
--replication.request-timeout
Values can be specified in seconds. If these options are used, they will
be used for replication requests, overriding any hard-coded defaults or
explicitly configured timeouts.