mirror of https://gitee.com/bigwinds/arangodb
updated CHANGELOG
This commit is contained in:
parent
de6a93b506
commit
ae292e0a32
|
@ -1,3 +1,9 @@
|
||||||
|
v3.4.0-preview.2
|
||||||
|
----------------
|
||||||
|
|
||||||
|
* preview for testing
|
||||||
|
|
||||||
|
|
||||||
v3.4.0-preview.1
|
v3.4.0-preview.1
|
||||||
----------------
|
----------------
|
||||||
|
|
||||||
|
|
|
@ -84,14 +84,14 @@ add_definitions("-DFUERTE_STANDALONE_ASIO=1")
|
||||||
# ARANGODB_RPM_UPSTREAM
|
# ARANGODB_RPM_UPSTREAM
|
||||||
# ARANGODB_RPM_REVISION
|
# ARANGODB_RPM_REVISION
|
||||||
|
|
||||||
set(ARANGODB_VERSION_MAJOR "3")
|
set(ARANGODB_VERSION_MAJOR "3")
|
||||||
set(ARANGODB_VERSION_MINOR "4")
|
set(ARANGODB_VERSION_MINOR "4")
|
||||||
|
|
||||||
# when building the nightly ARANGODB_VERSION_PATCH will be set
|
# when building the nightly ARANGODB_VERSION_PATCH will be set
|
||||||
if (NOT DEFINED ARANGODB_VERSION_PATCH)
|
if (NOT DEFINED ARANGODB_VERSION_PATCH)
|
||||||
set(ARANGODB_VERSION_PATCH "0")
|
set(ARANGODB_VERSION_PATCH "0")
|
||||||
set(ARANGODB_VERSION_RELEASE_TYPE "preview")
|
set(ARANGODB_VERSION_RELEASE_TYPE "")
|
||||||
set(ARANGODB_VERSION_RELEASE_NUMBER "1")
|
set(ARANGODB_VERSION_RELEASE_NUMBER "")
|
||||||
else()
|
else()
|
||||||
unset (ARANGODB_VERSION_RELEASE_TYPE) # do not remove space
|
unset (ARANGODB_VERSION_RELEASE_TYPE) # do not remove space
|
||||||
unset (ARANGODB_VERSION_RELEASE_NUMBER) # do not remove space
|
unset (ARANGODB_VERSION_RELEASE_NUMBER) # do not remove space
|
||||||
|
|
|
@ -1,16 +0,0 @@
|
||||||
.TH arangobench 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangobench - the ArangoDB benchmark and test tool
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangobench [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangob binary can be used to issue test requests to the
|
|
||||||
ArangoDB database. It can be used for benchmarks or server function
|
|
||||||
testing. It supports parallel querying and batch requests.
|
|
||||||
.SH OPTIONS
|
|
||||||
For a complete list of options, please refer to the ArangoDB
|
|
||||||
online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,31 +0,0 @@
|
||||||
.TH arangodump 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangodump - a tool to create logical dumps of an ArangoDB database
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangodump [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangodump binary can be used to create logical dumps of collection
|
|
||||||
meta information and collection data (documents) of an ArangoDB database.
|
|
||||||
By default, all non-system collections of the specified ArangoDB database
|
|
||||||
will be dumped with structural information and data.
|
|
||||||
|
|
||||||
For each collection, a file named "<collection>.structure.json" will be
|
|
||||||
created with information about the collection. When data is also dumped,
|
|
||||||
an additional file "<collection>.data.json" will also be created.
|
|
||||||
All dump files will be placed in a directory, which will be created by
|
|
||||||
arangodump when run. If the directory already exists, arangodump will refuse to
|
|
||||||
work unless started with the option "--overwrite true".
|
|
||||||
|
|
||||||
arangodump will work on the specified database only. If no database name
|
|
||||||
is specified, arangodump will work on the default database ("_system").
|
|
||||||
|
|
||||||
The dumped files can be re-stored in an ArangoDB database using the
|
|
||||||
arangorestore tool.
|
|
||||||
.SH OPTIONS
|
|
||||||
The arangodump binary has many options that can be used to control its
|
|
||||||
behavior. For a complete list of options, please refer to the
|
|
||||||
ArangoDB online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,24 +0,0 @@
|
||||||
.TH arangoexport 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangoexport - a tool to export collections of an ArangoDB database
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangoexport [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangoexport binary can be used to export collections of an ArangoDB
|
|
||||||
database to json and jsonl. It can also export a graph or collections
|
|
||||||
to xgmml.
|
|
||||||
|
|
||||||
arangoexport will work on the specified database only. If no database name
|
|
||||||
is specified, arangoexport will work on the default database ("_system").
|
|
||||||
|
|
||||||
The exported jsonl files can be re-imported in an ArangoDB database
|
|
||||||
using the arangoimport tool.
|
|
||||||
.SH OPTIONS
|
|
||||||
The arangoexport binary has many options that can be used to control its
|
|
||||||
behavior. For a complete list of options, please refer to the
|
|
||||||
ArangoDB online manual, available at https://www.arangodb.com/ or run
|
|
||||||
arangoexport --help.
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,19 +0,0 @@
|
||||||
.TH arangoimport 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangoimport - a bulk importer for the ArangoDB database
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangoimport [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangoimport binary can be used to bulk import data from a file into the
|
|
||||||
ArangoDB database. Input data be present in the input file in either CSV
|
|
||||||
format with column headlines, or in JSON format. If JSON format is used,
|
|
||||||
each line in the input file must contain exactly one JSON document with
|
|
||||||
the attribute name/value pairs to import.
|
|
||||||
.SH OPTIONS
|
|
||||||
The arangoimport binary has many options that can be used to control its
|
|
||||||
behavior. For a complete list of options, please refer to the
|
|
||||||
ArangoDB online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,18 +0,0 @@
|
||||||
.TH arangorestore 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangorestore - a data restore tool for the ArangoDB database
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangorestore [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangorestore binary can be used to restore data from logical dumps
|
|
||||||
created with the arangodump tool. Input data be present in the input
|
|
||||||
file in either CSV format with column headlines, or in JSON format. If
|
|
||||||
JSON format is used, each line in the input file must contain exactly
|
|
||||||
one JSON document with the attribute name/value pairs to import.
|
|
||||||
.SH OPTIONS
|
|
||||||
For a complete list of options, please refer to the ArangoDB
|
|
||||||
online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,16 +0,0 @@
|
||||||
.TH arangosh 1 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangosh - the ArangoDB shell
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangosh [options]
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangosh binary can be used to establish an interactive
|
|
||||||
client connection to the ArangoDB database. When the connection
|
|
||||||
is established, it can be used to execute actions on the server.
|
|
||||||
.SH OPTIONS
|
|
||||||
For a complete list of options, please refer to the ArangoDB
|
|
||||||
online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,18 +0,0 @@
|
||||||
.TH arango-dfdb 8 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arango-dfdb - a datafile debugger for ArangoDB
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arango-dfdb options
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arango-dfdb binary can be used to verify the datafiles of an
|
|
||||||
ArangoDB database server. The script must be run with exclusive access
|
|
||||||
to the server's data directory, meaning the ArangoDB server must not
|
|
||||||
be running and accessing the datafiles in the specified data
|
|
||||||
directory.
|
|
||||||
.SH OPTIONS
|
|
||||||
For a complete list of options, please refer to the ArangoDB
|
|
||||||
online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,22 +0,0 @@
|
||||||
.TH arangod 8 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
arangod - the ArangoDB database server
|
|
||||||
.SH SYNOPSIS
|
|
||||||
arangod [options] database-directory
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The arangod binary can be used to start the ArangoDB database
|
|
||||||
server. By default, the server will run in a mode that allows clients
|
|
||||||
to connect to it via the network. The server also has an emergency
|
|
||||||
console mode that can be used for any sort of maintenance
|
|
||||||
operations. In the emergency console mode, the server does not allow
|
|
||||||
any clients to connect. The server can be stopped gracefully at any
|
|
||||||
time by pressing CTRL-C or by sending the SIGINT signal to the
|
|
||||||
process.
|
|
||||||
.SH OPTIONS
|
|
||||||
The arangod binary has many options that can be used to control its
|
|
||||||
behavior. For a complete list of options, please refer to the
|
|
||||||
ArangoDB online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,16 +0,0 @@
|
||||||
.TH foxx-manager 8 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
foxx-manager - a Foxx application manager for ArangoDB
|
|
||||||
.SH SYNOPSIS
|
|
||||||
foxx-manager options
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The foxx-manager binary can be used to manage Foxx applications in the
|
|
||||||
ArangoDB database server. Foxx applications can be installed and
|
|
||||||
uninstalled.
|
|
||||||
.SH OPTIONS
|
|
||||||
For a complete list of options, please refer to the ArangoDB
|
|
||||||
online manual, available at https://www.arangodb.com/
|
|
||||||
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
|
@ -1,16 +0,0 @@
|
||||||
.TH rcarangod 8 "3.4.0-preview-rc.1" "ArangoDB" "ArangoDB"
|
|
||||||
.SH NAME
|
|
||||||
rcarangod - control script for the ArangoDB database server
|
|
||||||
.SH SYNOPSIS
|
|
||||||
rcarangod start|stop
|
|
||||||
.SH DESCRIPTION
|
|
||||||
The rcarangod script controls the operation of the ArangoDB database
|
|
||||||
server daemon running on the system. The rcarangod script is normally
|
|
||||||
run at system boot time with the "start" argument, and at system
|
|
||||||
shutdown time with the "stop" argument. It can also be invoked
|
|
||||||
manually at any time to start or stop the ArangoDB database server.
|
|
||||||
.SH SEE ALSO
|
|
||||||
.BR arangod "(8), "
|
|
||||||
.SH AUTHOR
|
|
||||||
Copyright ArangoDB GmbH, Cologne, Germany
|
|
||||||
|
|
Loading…
Reference in New Issue