8000 fixed ui behaviour when replacing a foxx app by hkernbach · Pull Request #9719 · arangodb/arangodb · GitHub
[go: up one dir, main page]

Skip to content

fixed ui behaviour when replacing a foxx app #9719

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 13 commits into from
Oct 10, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Merge branch 'devel' into bug-fix/replace-foxx-app-ui
  • Loading branch information
hkernbach authored Oct 10, 2019
commit 1de0dcf4c33103f6a5403cd334c6a3f170662b83
97 changes: 97 additions & 0 deletions CHANGELOG
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,103 @@ devel
were specified. Should the sharding keys not match the values in the actual document
a not found error will be returned.

* Bugfix: In an AQL cluster query, when gathering unsorted data in combination
with a LIMIT with non-zero offset, if this offset exactly matches the number
of documents in the first shards consumed, the rest of the documents was not
returned.

* Show shards of all collections (including system collections) in the web UI's shard
distribution view.

This is necessary to access the prototype collections of a collection sharded via
`distributeShardsLike` in case the prototype is a system collection, and the prototype
should be moved to another server.

* RCLone URL normalization

* Fixed Unintended multiple unlock commands from coordinator to
transaction locked db servers

* Disallow using `_id` or `_rev` as shard keys in clustered collections.

Using these attributes for sharding was not supported before, but didn't trigger
any errors. Instead, collections were created and silently using `_key` as
the shard key, without making the caller aware of that an unsupported shard
keys was used.

* DB server locking / unlocking for hot backup revisited and enhanced.

* Fixed unintended multiple unlock commands from coordinator to
transaction locked db servers.

* Use execvp instead of execv in hotbackup restore.

* Re-enabled the AQL sort-limit optimization rule in conjunction with fullCount
in the cluster. It now also may speed up fullCount with sorted indexes and a
limit.

* Fix config directory handling, so we don't trap into UNC path lookups on windows

* Prevent spurious log message "Scheduler queue is filled more than 50% in last x s"
from occurring when this is not the case. Due to a data race, the message could
previously also occur if the queue was empty.

* Make the scheduler enforce the configured queue lengths. The values of the options
`--server.scheduler-queue-size`, `--server.prio1-size` and `--server.maximal-queue-size`
will now be honored and not exceeded.

The default queue sizes in the scheduler for requests buffering have
also been changed as follows:

request type before now
-----------------------------------
high priority 128 4096
medium priority 1048576 4096
low priority 4096 4096

The queue sizes can still be adjusted at server start using the above-
mentioned startup options.

* Fix compilation issue with clang 10

* Fixed issue #10062: AQL: Could not extract custom attribute.

* Add replicationFactor, minReplicationFactor and sharding strategy to database creation
dialog in web UI. Preselect database default values for collection creation in web UI.

* Add new JavaScipt function `db._properties()` and REST route GET
`/_api/database/properties` that provides information about the current database's
properties.

* Add new options `sharding` and `replicationFactor` for database creation methods. The
specified values will provide the defaults for all collections created in a database.

Valid values for `sharding` are `""`, "flexible", "single". The first 2 values are
treated equally. Values for `replicationFactor` are natural numbers or the string
`satellite`.

* Add new server option `--cluster.default-replication-factor` that allows to set the
default replication factor for non-system collections (default: 1).

* Made the mechanism in the Web UI of replacing and upgrading a foxx app more clear.

* Fix a problem with AQL constrained sort in the cluster, which might abort
queries.

* Fix strange shutdown hanger which came from the fact that currently
libgcc/libmusl wrongly detect multi-threadedness in statically linked
executables.

* Enabled IPO with cmake as an option, default is on for release builds without
google tests.

* Bugfix: The AQL sort-limit optimization was applied in some cases it shouldn't,
resulting in undefined behaviour.

* Remove operations for documents in the cluster will now use an optimization,
if all sharding keys are specified. Should the sharding keys not match the values in
the actual document, a not found error will be returned.

* Fixed AQL constrained-heap sort in conjunction with fullCount.

* Fixed "ArangoDB is not running in cluster mode" errors in active failover setups.
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.
0