Hawkin
/
arangodb
mirror of https://gitee.com/bigwinds/arangodb
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

updated CHANGELOG

This commit is contained in:
jsteemann 2016-02-06 00:48:26 +01:00
parent f5ad2f0d75
commit 6a6e2f212c
1 changed files with 29 additions and 33 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

62
CHANGELOG
View File

@ -1,8 +1,20 @@
v3.0.0 (XXXX-XX-XX) v3.0.0 (XXXX-XX-XX)
------------------- -------------------
* added a new log option "--log.output <definition>". The output definition * make logging configurable per log "topic"
"<definition>" can either
`--log.level <level>` sets the global log level to <level>, e.g. `info`,
`debug`, `trace`.
`--log.level topic=<level>` sets the log level for a specific topic.
Currently, the following topics exist: `collector`, `compactor`, `mmap`,
`performance`, `queries`, and `requests`. `performance` and `requests` are
set to FATAL by default. `queries` is set to info. All others are
set to the global level by default.
The new log option `--log.output <definition>` allows directing the global
or per-topic log output to different outputs. The output definition
"<definition>" can be one of
"-" for stdin "-" for stdin
"+" for stderr "+" for stderr
@ -10,46 +22,31 @@ v3.0.0 (XXXX-XX-XX)
"syslog://<syslog-facility>/<application-name>" "syslog://<syslog-facility>/<application-name>"
"file://<relative-path>" "file://<relative-path>"
"--log.level <level>" sets the global log level to <level>. The option can be specified multiple times in order to configure the output
for different log topics. To set up a per-topic output configuration, use
It is also possible to configure logging for topics. `--log.output <topic>=<definition>`, e.g.
"--log.level topic=<level>" sets the log level for a specific topic.
Currently, the following topics exists: collector, compactor, mmap,
performance, queries, and requests. Performance and requests are
set to FATAL by default. Queries is set to info. All others are
set to the global level by default.
You can also output specicify topics to specicify output channels.
For example
queries=file://queries.txt queries=file://queries.txt
logs all queries requests to the file "queries.txt". logs all queries to the file "queries.txt".
"--log.requests" is now deprecated. Use * the option `--log.requests-file` is now deprecated. Instead use
"--log.level requests=info" `--log.level requests=info`
"--log.output requests=file://requests.txt" `--log.output requests=file://requests.txt`
instead. * the option `--log.facility` is now deprecated. Instead use
"--log.facility" is now deprected. Use `--log.output requests=syslog://facility`
"--log.output requests=syslog://facility" * the option `--log.performance` is now deprecated. Instead use
instead. `--log.level performance=trace`
"--log.performance" is now deprected. Use * removed option `--log.source-filter`
"--log.level requests=trace"
instead.
* removed configure option `--enable-logger` * removed configure option `--enable-logger`
* removed startup option `--log.source-filter`
* change collection directory names to include a random id component at the end * change collection directory names to include a random id component at the end
The new pattern is `collection-<id>-<random>`, where `<id>` is the collection The new pattern is `collection-<id>-<random>`, where `<id>` is the collection
@ -100,7 +97,7 @@ v2.8.2 (XXXX-XX-XX)
* added all-in-one function *setupReplication* to synchronize data from master * added all-in-one function *setupReplication* to synchronize data from master
to slave and start the continuous replication: to slave and start the continuous replication:
require("org/arangodb/replication").setupReplication(configuration); require("@arangodb/replication").setupReplication(configuration);
The command will return when the initial synchronization is finished and the The command will return when the initial synchronization is finished and the
continuous replication has been started, or in case the initial synchronization continuous replication has been started, or in case the initial synchronization
@ -120,7 +117,7 @@ v2.8.2 (XXXX-XX-XX)
master: master:
db._useDatabase("_system"); db._useDatabase("_system");
require("org/arangodb/replication").setupReplication({ require("@arangodb/replication").setupReplication({
endpoint: "tcp://master.domain.org:8529", endpoint: "tcp://master.domain.org:8529",
username: "myuser", username: "myuser",
password: "mypasswd", password: "mypasswd",
@ -469,7 +466,7 @@ v2.8.0-alpha1 (2015-12-03)
ArangoShell like this: ArangoShell like this:
/* starts initial synchronization */ /* starts initial synchronization */
var replication = require("org/arangodb/replication"); var replication = require("@arangodb/replication");
var id = replication.sync({ var id = replication.sync({
endpoint: "tcp://master.domain.org:8529", endpoint: "tcp://master.domain.org:8529",
username: "myuser", username: "myuser",
@ -486,7 +483,6 @@ v2.8.0-alpha1 (2015-12-03)
* fixed non-deterministic query results in some cluster queries * fixed non-deterministic query results in some cluster queries
>>>>>>> 181db60b494097080cc1fac0a50895794eb91a57
* fixed issue #1589 * fixed issue #1589