forked from arangodb/arangodb
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CHANGELOG
4913 lines (3226 loc) · 193 KB
/
CHANGELOG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
v2.6.0 (XXXX-XX-XX)
-------------------
* fixed issue #1247: debian init script problems
* multi-threaded index creation on collection load
When a collection contains more than one secondary index, they can be built in memory in
parallel when the collection is loaded. How many threads are used for parallel index creation
is determined by the new configuration parameter `--database.index-threads`. If this is set
to 0, indexes are built by the opening thread only and sequentially. This is equivalent to
the behavior in 2.5 and before.
* speed up building up primary index when loading collections
* added `count` attribute to `parameters.json` file. This attribute indicates the number of
live documents in the collection on unload. It is read when the collection is (re)loaded to
determine the initial size for the collection's primary index
* removed remainders of MRuby integration, removed arangoirb
* fixed issue #1258: http pipelining not working?
v2.5.0-beta4 (2015-03-05)
-------------------------
* fixed issue #1247: debian init script problems
v2.5.0-beta3 (2015-02-27)
-------------------------
* fix windows install path calculation in arango
* fix windows logging of long strings
* fix possible undefinedness of const strings in windows
v2.5.0-beta1 (2015-02-23)
-------------------------
* fixed issue #1256: agency binary not found #1256
* fixed issue #1230: API: document/col-name/_key and cursor return different floats
* front-end: dashboard tries not to (re)load statistics if user has no access
* V8: Upgrade to version 3.31.74.1
* etcd: Upgrade to version 2.0 - This requires go 1.3 to compile at least.
* refuse to startup if ICU wasn't initialized, this will i.e. prevent errors from being printed,
and libraries from being loaded.
* front-end: unwanted removal of index table header after creating new index
* fixed issue #1248: chrome: applications filtering not working
* fixed issue #1198: queries remain in aql editor (front-end) if you navigate through different tabs
* Simplify usage of Foxx
Thanks to our user feedback we learned that Foxx is a powerful, yet rather complicated concept.
With this release we tried to make it less complicated while keeping all its strength.
That includes a rewrite of the documentation as well as some code changes as listed below:
* Moved Foxx applications to a different folder.
The naming convention now is: <app-path>/_db/<dbname>/<mountpoint>/APP
Before it was: <app-path>/databases/<dbname>/<appname>:<appversion>
This caused some trouble as apps where cached based on name and version and updates did not apply.
Hence the path on filesystem and the app's access URL had no relation to one another.
Now the path on filesystem is identical to the URL (except for slashes and the appended APP)
* Rewrite of Foxx routing
The routing of Foxx has been exposed to major internal changes we adjusted because of user feedback.
This allows us to set the development mode per mountpoint without having to change pathes and hold
apps at seperate locations.
* Foxx Development mode
The development mode used until 2.4 is gone. It has been replaced by a much more mature version.
This includes the deprecation of the javascript.dev-app-path parameter, which is useless since 2.5.
Instead of having two separate app directories for production and development, apps now reside in
one place, which is used for production as well as for development.
Apps can still be put into development mode, changing their behavior compared to production mode.
Development mode apps are still reread from disk at every request, and still they ship more debug
output.
This change has also made the startup options `--javascript.frontend-development-mode` and
`--javascript.dev-app-path` obsolete. The former option will not have any effect when set, and the
latter option is only read and used during the upgrade to 2.5 and does not have any effects later.
* Foxx install process
Installing Foxx apps has been a two step process: import them into ArangoDB and mount them at a
specific mountpoint. These operations have been joined together. You can install an app at one
mountpoint, that's it. No fetch, mount, unmount, purge cycle anymore. The commands have been
simplified to just:
* install: get your Foxx app up and running
* uninstall: shut it down and erase it from disk
* Foxx error output
Until 2.4 the errors produced by Foxx were not optimal. Often, the error message was just
`unable to parse manifest` and contained only an internal stack trace.
In 2.5 we made major improvements there, including a much more finegrained error output that
helps you debug your Foxx apps. The error message printed is now much closer to its source and
should help you track it down.
Also we added the default handlers for unhandled errors in Foxx apps:
* You will get a nice internal error page whenever your Foxx app is called but was not installed
due to any error
* You will get a proper error message when having an uncaught error appears in any app route
In production mode the messages above will NOT contain any information about your Foxx internals
and are safe to be exposed to third party users.
In development mode the messages above will contain the stacktrace (if available), making it easier for
your in-house devs to track down errors in the application.
* added `console` object to Foxx apps. All Foxx apps now have a console object implementing
the familiar Console API in their global scope, which can be used to log diagnostic
messages to the database.
* added `org/arangodb/request` module, which provides a simple API for making HTTP requests
to external services.
* added optimizer rule `propagate-constant-attributes`
This rule will look inside `FILTER` conditions for constant value equality comparisons,
and insert the constant values in other places in `FILTER`s. For example, the rule will
insert `42` instead of `i.value` in the second `FILTER` of the following query:
FOR i IN c1 FOR j IN c2 FILTER i.value == 42 FILTER j.value == i.value RETURN 1
* added `filtered` value to AQL query execution statistics
This value indicates how many documents were filtered by `FilterNode`s in the AQL query.
Note that `IndexRangeNode`s can also filter documents by selecting only the required ranges
from the index. The `filtered` value will not include the work done by `IndexRangeNode`s,
but only the work performed by `FilterNode`s.
* added support for sparse hash and skiplist indexes
Hash and skiplist indexes can optionally be made sparse. Sparse indexes exclude documents
in which at least one of the index attributes is either not set or has a value of `null`.
As such documents are excluded from sparse indexes, they may contain fewer documents than
their non-sparse counterparts. This enables faster indexing and can lead to reduced memory
usage in case the indexed attribute does occur only in some, but not all documents of the
collection. Sparse indexes will also reduce the number of collisions in non-unique hash
indexes in case non-existing or optional attributes are indexed.
In order to create a sparse index, an object with the attribute `sparse` can be added to
the index creation commands:
db.collection.ensureHashIndex(attributeName, { sparse: true });
db.collection.ensureHashIndex(attributeName1, attributeName2, { sparse: true });
db.collection.ensureUniqueConstraint(attributeName, { sparse: true });
db.collection.ensureUniqueConstraint(attributeName1, attributeName2, { sparse: true });
db.collection.ensureSkiplist(attributeName, { sparse: true });
db.collection.ensureSkiplist(attributeName1, attributeName2, { sparse: true });
db.collection.ensureUniqueSkiplist(attributeName, { sparse: true });
db.collection.ensureUniqueSkiplist(attributeName1, attributeName2, { sparse: true });
Note that in place of the above specialized index creation commands, it is recommended to use
the more general index creation command `ensureIndex`:
```js
db.collection.ensureIndex({ type: "hash", sparse: true, unique: true, fields: [ attributeName ] });
db.collection.ensureIndex({ type: "skiplist", sparse: false, unique: false, fields: [ "a", "b" ] });
```
When not explicitly set, the `sparse` attribute defaults to `false` for new indexes.
This causes a change in behavior when creating a unique hash index without specifying the
sparse flag: in 2.4, unique hash indexes were implicitly sparse, always excluding `null` values.
There was no option to control this behavior, and sparsity was neither supported for non-unique
hash indexes nor skiplists in 2.4. This implicit sparsity of unique hash indexes was considered
an inconsistency, and therefore the behavior was cleaned up in 2.5. As of 2.5, indexes will
only be created sparse if sparsity is explicitly requested. Existing unique hash indexes from 2.4
or before will automatically be migrated so they are still sparse after the upgrade to 2.5.
Geo indexes are implicitly sparse, meaning documents without the indexed location attribute or
containing invalid location coordinate values will be excluded from the index automatically. This
is also a change when compared to pre-2.5 behavior, when documents with missing or invalid
coordinate values may have caused errors on insertion when the geo index' `unique` flag was set
and its `ignoreNull` flag was not.
This was confusing and has been rectified in 2.5. The method `ensureGeoConstaint()` now does the
same as `ensureGeoIndex()`. Furthermore, the attributes `constraint`, `unique`, `ignoreNull` and
`sparse` flags are now completely ignored when creating geo indexes.
The same is true for fulltext indexes. There is no need to specify non-uniqueness or sparsity for
geo or fulltext indexes. They will always be non-unique and sparse.
As sparse indexes may exclude some documents, they cannot be used for every type of query.
Sparse hash indexes cannot be used to find documents for which at least one of the indexed
attributes has a value of `null`. For example, the following AQL query cannot use a sparse
index, even if one was created on attribute `attr`:
FOR doc In collection
FILTER doc.attr == null
RETURN doc
If the lookup value is non-constant, a sparse index may or may not be used, depending on
the other types of conditions in the query. If the optimizer can safely determine that
the lookup value cannot be `null`, a sparse index may be used. When uncertain, the optimizer
will not make use of a sparse index in a query in order to produce correct results.
For example, the following queries cannot use a sparse index on `attr` because the optimizer
will not know beforehand whether the comparsion values for `doc.attr` will include `null`:
FOR doc In collection
FILTER doc.attr == SOME_FUNCTION(...)
RETURN doc
FOR other IN otherCollection
FOR doc In collection
FILTER doc.attr == other.attr
RETURN doc
Sparse skiplist indexes can be used for sorting if the optimizer can safely detect that the
index range does not include `null` for any of the index attributes.
* inspection of AQL data-modification queries will now detect if the data-modification part
of the query can run in lockstep with the data retrieval part of the query, or if the data
retrieval part must be executed before the data modification can start.
Executing the two in lockstep allows using much smaller buffers for intermediate results
and starts the actual data-modification operations much earlier than if the two phases
were executed seperately.
* Allow dynamic attribute names in AQL object literals
This allows using arbitrary expressions to construct attribute names in object
literals specified in AQL queries. To disambiguate expressions and other unquoted
attribute names, dynamic attribute names need to be enclosed in brackets (`[` and `]`).
Example:
FOR i IN 1..100
RETURN { [ CONCAT('value-of-', i) ] : i }
* make AQL optimizer rule "use-index-for-sort" remove sort also in case a non-sorted
index (e.g. a hash index) is used for only equality lookups and all sort attributes
are covered by the index.
Example that does not require an extra sort (needs hash index on `value`):
FOR doc IN collection FILTER doc.value == 1 SORT doc.value RETURN doc
Another example that does not require an extra sort (with hash index on `value1`, `value2`):
FOR doc IN collection FILTER doc.value1 == 1 && doc.value2 == 2 SORT doc.value1, doc.value2 RETURN doc
* make AQL optimizer rule "use-index-for-sort" remove sort also in case the sort critieria
excludes the left-most index attributes, but the left-most index attributes are used
by the index for equality-only lookups.
Example that can use the index for sorting (needs skiplist index on `value1`, `value2`):
FOR doc IN collection FILTER doc.value1 == 1 SORT doc.value2 RETURN doc
* added selectivity estimates for primary index, edge index, and hash index
The selectivity estimates are returned by the `GET /_api/index` REST API method
in a sub-attribute `selectivityEstimate` for each index that supports it. This
attribute will be omitted for indexes that do not provide selectivity estimates.
If provided, the selectivity estimate will be a numeric value between 0 and 1.
Selectivity estimates will also be reported in the result of `collection.getIndexes()`
for all indexes that support this. If no selectivity estimate can be determined for
an index, the attribute `selectivityEstimate` will be omitted here, too.
The web interface also shows selectivity estimates for each index that supports this.
Currently the following index types can provide selectivity estimates:
- primary index
- edge index
- hash index (unique and non-unique)
No selectivity estimates will be provided when running in cluster mode.
* fixed issue #1226: arangod log issues
* added additional logger if arangod is started in foreground mode on a tty
* added AQL optimizer rule "move-calculations-down"
* use exclusive native SRWLocks on Windows instead of native mutexes
* added AQL functions MD5, SHA1, and RANDOM_TOKEN.
* reduced number of string allocations when parsing certain AQL queries
parsing numbers (integers or doubles) does not require a string allocation
per number anymore
* RequestContext#bodyParam now accepts arbitrary joi schemas and rejects invalid (but well-formed) request bodies.
* enforce that AQL user functions are wrapped inside JavaScript function () declarations
AQL user functions were always expected to be wrapped inside a JavaScript function, but previously
this was not enforced when registering a user function. Enforcing the AQL user functions to be contained
inside functions prevents functions from doing some unexpected things that may have led to undefined
behavior.
* Windows service uninstalling: only remove service if it points to the currently running binary,
or --force was specified.
* Windows (debug only): print stacktraces on crash and run minidump
* Windows (cygwin): if you run arangosh in a cygwin shell or via ssh we will detect this and use
the appropriate output functions.
* Windows: improve process management
* fix ipv6 reverse ip lookups - so far we only did ipv4 addresses.
* improve join documentation, add outer join example
* run jslint for unit tests too, to prevent "memory leaks" by global js objects with native code.
* fix error logging for exceptions - we wouldn't log the exception message itself so far.
* improve error reporting in the http client (windows & *nix)
* improve error reports in cluster
* Standard errors can now contain custom messages.
v2.4.5 (XXXX-XX-XX)
-------------------
* added elapsed time to HTTP request logging output (`--log.requests-file`)
* added AQL current and slow query tracking, killing of AQL queries
This change enables retrieving the list of currently running AQL queries inside the selected database.
AQL queries with an execution time beyond a certain threshold can be moved to a "slow query" facility
and retrieved from there. Queries can also be killed by specifying the query id.
This change adds the following HTTP REST APIs:
- `GET /_api/query/current`: for retrieving the list of currently running queries
- `GET /_api/query/slow`: for retrieving the list of slow queries
- `DELETE /_api/query/slow`: for clearing the list of slow queries
- `GET /_api/query/properties`: for retrieving the properties for query tracking
- `PUT /_api/query/properties`: for adjusting the properties for query tracking
- `DELETE /_api/query/<id>`: for killing an AQL query
The following JavaScript APIs have been added:
- require("org/arangodb/aql/queries").current();
- require("org/arangodb/aql/queries").slow();
- require("org/arangodb/aql/queries").clearSlow();
- require("org/arangodb/aql/queries").properties();
- require("org/arangodb/aql/queries").kill();
* fixed issue #1265: arangod crashed with SIGSEGV
* fixed issue #1241: Wildcards in examples
* fixed comment parsing in Foxx controllers
v2.4.4 (2015-02-24)
-------------------
* fixed the generation template for foxx apps. It now does not create deprecated functions anymore
* add custom visitor functionality for `GRAPH_NEIGHBORS` function, too
* increased default value of traversal option *maxIterations* to 100 times of its previous
default value
v2.4.3 (2015-02-06)
-------------------
* fix multi-threading with openssl when running under Windows
* fix timeout on socket operations when running under Windows
* Fixed an error in Foxx routing which caused some apps that worked in 2.4.1 to fail with status 500: `undefined is not a function` errors in 2.4.2
This error was occurring due to seldom internal rerouting introduced by the malformed application handler.
v2.4.2 (2015-01-30)
-------------------
* added custom visitor functionality for AQL traversals
This allows more complex result processing in traversals triggered by AQL. A few examples
are shown in [this article](https://jsteemann.github.io/blog/2015/01/28/using-custom-visitors-in-aql-graph-traversals/).
* improved number of results estimated for nodes of type EnumerateListNode and SubqueryNode
in AQL explain output
* added AQL explain helper to explain arbitrary AQL queries
The helper function prints the query execution plan and the indexes to be used in the
query. It can be invoked from the ArangoShell or the web interface as follows:
require("org/arangodb/aql/explainer").explain(query);
* enable use of indexes for certain AQL conditions with non-equality predicates, in
case the condition(s) also refer to indexed attributes
The following queries will now be able to use indexes:
FILTER a.indexed == ... && a.indexed != ...
FILTER a.indexed == ... && a.nonIndexed != ...
FILTER a.indexed == ... && ! (a.indexed == ...)
FILTER a.indexed == ... && ! (a.nonIndexed == ...)
FILTER a.indexed == ... && ! (a.indexed != ...)
FILTER a.indexed == ... && ! (a.nonIndexed != ...)
FILTER (a.indexed == ... && a.nonIndexed == ...) || (a.indexed == ... && a.nonIndexed == ...)
FILTER (a.indexed == ... && a.nonIndexed != ...) || (a.indexed == ... && a.nonIndexed != ...)
* Fixed spuriously occurring "collection not found" errors when running queries on local
collections on a cluster DB server
* Fixed upload of Foxx applications to the server for apps exceeding approx. 1 MB zipped.
* Malformed Foxx applications will now return a more useful error when any route is requested.
In Production a Foxx app mounted on /app will display an html page on /app/* stating a 503 Service temporarily not available.
It will not state any information about your Application.
Before it was a 404 Not Found without any information and not distinguishable from a correct not found on your route.
In Development Mode the html page also contains information about the error occured.
* Unhandled errors thrown in Foxx routes are now handled by the Foxx framework itself.
In Production the route will return a status 500 with a body {error: "Error statement"}.
In Development the route will return a status 500 with a body {error: "Error statement", stack: "..."}
Before, it was status 500 with a plain text stack including ArangoDB internal routing information.
* The Applications tab in web interface will now request development apps more often.
So if you have a fixed a syntax error in your app it should always be visible after reload.
v2.4.1 (2015-01-19)
-------------------
* improved WAL recovery output
* fixed certain OR optimizations in AQL optimizer
* better diagnostics for arangoimp
* fixed invalid result of HTTP REST API method `/_admin/foxx/rescan`
* fixed possible segmentation fault when passing a Buffer object into a V8 function
as a parameter
* updated AQB module to 1.8.0.
v2.4.0 (2015-01-13)
-------------------
* updated AQB module to 1.7.0.
* fixed V8 integration-related crashes
* make `fs.move(src, dest)` also fail when both `src` and `dest` are
existing directories. This ensures the same behavior of the move operation
on different platforms.
* fixed AQL insert operation for multi-shard collections in cluster
* added optional return value for AQL data-modification queries.
This allows returning the documents inserted, removed or updated with the query, e.g.
FOR doc IN docs REMOVE doc._key IN docs LET removed = OLD RETURN removed
FOR doc IN docs INSERT { } IN docs LET inserted = NEW RETURN inserted
FOR doc IN docs UPDATE doc._key WITH { } IN docs LET previous = OLD RETURN previous
FOR doc IN docs UPDATE doc._key WITH { } IN docs LET updated = NEW RETURN updated
The variables `OLD` and `NEW` are automatically available when a `REMOVE`, `INSERT`,
`UPDATE` or `REPLACE` statement is immediately followed by a `LET` statement.
Note that the `LET` and `RETURN` statements in data-modification queries are not as
flexible as the general versions of `LET` and `RETURN`. When returning documents from
data-modification operations, only a single variable can be assigned using `LET`, and
the assignment can only be either `OLD` or `NEW`, but not an arbitrary expression. The
`RETURN` statement also allows using the just-created variable only, and no arbitrary
expressions.
v2.4.0-beta1 (2014-12-26)
--------------------------
* fixed superstates in FoxxGenerator
* fixed issue #1065: Aardvark: added creation of documents and edges with _key property
* fixed issue #1198: Aardvark: current AQL editor query is now cached
* Upgraded V8 version from 3.16.14 to 3.29.59
The built-in version of V8 has been upgraded from 3.16.14 to 3.29.59.
This activates several ES6 (also dubbed *Harmony* or *ES.next*) features in
ArangoDB, both in the ArangoShell and the ArangoDB server. They can be
used for scripting and in server-side actions such as Foxx routes, traversals
etc.
The following ES6 features are available in ArangoDB 2.4 by default:
* iterators
* the `of` operator
* symbols
* predefined collections types (Map, Set etc.)
* typed arrays
Many other ES6 features are disabled by default, but can be made available by
starting arangod or arangosh with the appropriate options:
* arrow functions
* proxies
* generators
* String, Array, and Number enhancements
* constants
* enhanced object and numeric literals
To activate all these ES6 features in arangod or arangosh, start it with
the following options:
arangosh --javascript.v8-options="--harmony --harmony_generators"
More details on the available ES6 features can be found in
[this blog](https://jsteemann.github.io/blog/2014/12/19/using-es6-features-in-arangodb/).
* Added Foxx generator for building Hypermedia APIs
A more detailed description is [here](https://www.arangodb.com/2014/12/08/building-hypermedia-apis-foxxgenerator)
* New `Applications` tab in web interface:
The `applications` tab got a complete redesign.
It will now only show applications that are currently running on ArangoDB.
For a selected application, a new detailed view has been created.
This view provides a better overview of the app:
* author
* license
* version
* contributors
* download links
* API documentation
To install a new application, a new dialogue is now available.
It provides the features already available in the console application `foxx-manager` plus some more:
* install an application from Github
* install an application from a zip file
* install an application from ArangoDB's application store
* create a new application from scratch: this feature uses a generator to
create a Foxx application with pre-defined CRUD methods for a given list
of collections. The generated Foxx app can either be downloaded as a zip file or
be installed on the server. Starting with a new Foxx app has never been easier.
* fixed issue #1102: Aardvark: Layout bug in documents overview
The documents overview was entirely destroyed in some situations on Firefox.
We replaced the plugin we used there.
* fixed issue #1168: Aardvark: pagination buttons jumping
* fixed issue #1161: Aardvark: Click on Import JSON imports previously uploaded file
* removed configure options `--enable-all-in-one-v8`, `--enable-all-in-one-icu`,
and `--enable-all-in-one-libev`.
* global internal rename to fix naming incompatibilities with JSON:
Internal functions with names containing `array` have been renamed to `object`,
internal functions with names containing `list` have been renamed to `array`.
The renaming was mainly done in the C++ parts. The documentation has also been
adjusted so that the correct JSON type names are used in most places.
The change also led to the addition of a few function aliases in AQL:
* `TO_LIST` now is an alias of the new `TO_ARRAY`
* `IS_LIST` now is an alias of the new `IS_ARRAY`
* `IS_DOCUMENT` now is an alias of the new `IS_OBJECT`
The changed also renamed the option `mergeArrays` to `mergeObjects` for AQL
data-modification query options and HTTP document modification API
* AQL: added optimizer rule "remove-filter-covered-by-index"
This rule removes FilterNodes and CalculationNodes from an execution plan if the
filter is already covered by a previous IndexRangeNode. Removing the CalculationNode
and the FilterNode will speed up query execution because the query requires less
computation.
* AQL: added optimizer rule "remove-sort-rand"
This rule removes a `SORT RAND()` expression from a query and moves the random
iteration into the appropriate `EnumerateCollectionNode`. This is more efficient
than individually enumerating and then sorting randomly.
* AQL: range optimizations for IN and OR
This change enables usage of indexes for several additional cases. Filters containing
the `IN` operator can now make use of indexes, and multiple OR- or AND-combined filter
conditions can now also use indexes if the filters are accessing the same indexed
attribute.
Here are a few examples of queries that can now use indexes but couldn't before:
FOR doc IN collection
FILTER doc.indexedAttribute == 1 || doc.indexedAttribute > 99
RETURN doc
FOR doc IN collection
FILTER doc.indexedAttribute IN [ 3, 42 ] || doc.indexedAttribute > 99
RETURN doc
FOR doc IN collection
FILTER (doc.indexedAttribute > 2 && doc.indexedAttribute < 10) ||
(doc.indexedAttribute > 23 && doc.indexedAttribute < 42)
RETURN doc
* fixed issue #500: AQL parentheses issue
This change allows passing subqueries as AQL function parameters without using
duplicate brackets (e.g. `FUNC(query)` instead of `FUNC((query))`
* added optional `COUNT` clause to AQL `COLLECT`
This allows more efficient group count calculation queries, e.g.
FOR doc IN collection
COLLECT age = doc.age WITH COUNT INTO length
RETURN { age: age, count: length }
A count-only query is also possible:
FOR doc IN collection
COLLECT WITH COUNT INTO length
RETURN length
* fixed missing makeDirectory when fetching a Foxx application from a zip file
* fixed issue #1134: Change the default endpoint to localhost
This change will modify the IP address ArangoDB listens on to 127.0.0.1 by default.
This will make new ArangoDB installations unaccessible from clients other than
localhost unless changed. This is a security feature.
To make ArangoDB accessible from any client, change the server's configuration
(`--server.endpoint`) to either `tcp:https://0.0.0.0:8529` or the server's publicly
visible IP address.
* deprecated `Repository#modelPrototype`. Use `Repository#model` instead.
* IMPORTANT CHANGE: by default, system collections are included in replication and all
replication API return values. This will lead to user accounts and credentials
data being replicated from master to slave servers. This may overwrite
slave-specific database users.
If this is undesired, the `_users` collection can be excluded from replication
easily by setting the `includeSystem` attribute to `false` in the following commands:
* replication.sync({ includeSystem: false });
* replication.applier.properties({ includeSystem: false });
This will exclude all system collections (including `_aqlfunctions`, `_graphs` etc.)
from the initial synchronisation and the continuous replication.
If this is also undesired, it is also possible to specify a list of collections to
exclude from the initial synchronisation and the continuous replication using the
`restrictCollections` attribute, e.g.:
replication.applier.properties({
includeSystem: true,
restrictType: "exclude",
restrictCollections: [ "_users", "_graphs", "foo" ]
});
The HTTP API methods for fetching the replication inventory and for dumping collections
also support the `includeSystem` control flag via a URL parameter.
* removed DEPRECATED replication methods:
* `replication.logger.start()`
* `replication.logger.stop()`
* `replication.logger.properties()`
* HTTP PUT `/_api/replication/logger-start`
* HTTP PUT `/_api/replication/logger-stop`
* HTTP GET `/_api/replication/logger-config`
* HTTP PUT `/_api/replication/logger-config`
* fixed issue #1174, which was due to locking problems in distributed
AQL execution
* improved cluster locking for AQL avoiding deadlocks
* use DistributeNode for modifying queries with REPLACE and UPDATE, if
possible
v2.3.6 (2015-XX-XX)
-------------------
* fixed AQL subquery optimization that produced wrong result when multiple subqueries
directly followed each other and and a directly following `LET` statement did refer
to any but the first subquery.
v2.3.5 (2015-01-16)
-------------------
* fixed intermittent 404 errors in Foxx apps after mounting or unmounting apps
* fixed issue #1200: Expansion operator results in "Cannot call method 'forEach' of null"
* fixed issue #1199: Cannot unlink root node of plan
v2.3.4 (2014-12-23)
-------------------
* fixed cerberus path for MyArangoDB
v2.3.3 (2014-12-17)
-------------------
* fixed error handling in instanciation of distributed AQL queries, this
also fixes a bug in cluster startup with many servers
* issue #1185: parse non-fractional JSON numbers with exponent (e.g. `4e-261`)
* issue #1159: allow --server.request-timeout and --server.connect-timeout of 0
v2.3.2 (2014-12-09)
-------------------
* fixed issue #1177: Fix bug in the user app's storage
* fixed issue #1173: AQL Editor "Save current query" resets user password
* fixed missing makeDirectory when fetching a Foxx application from a zip file
* put in warning about default changed: fixed issue #1134: Change the default endpoint to localhost
* fixed issue #1163: invalid fullCount value returned from AQL
* fixed range operator precedence
* limit default maximum number of plans created by AQL optimizer to 256 (from 1024)
* make AQL optimizer not generate an extra plan if an index can be used, but modify
existing plans in place
* fixed AQL cursor ttl (time-to-live) issue
Any user-specified cursor ttl value was not honored since 2.3.0.
* fixed segfault in AQL query hash index setup with unknown shapes
* fixed memleaks
* added AQL optimizer rule for removing `INTO` from a `COLLECT` statement if not needed
* fixed issue #1131
This change provides the `KEEP` clause for `COLLECT ... INTO`. The `KEEP` clause
allows controlling which variables will be kept in the variable created by `INTO`.
* fixed issue #1147, must protect dispatcher ID for etcd
v2.3.1 (2014-11-28)
-------------------
* recreate password if missing during upgrade
* fixed issue #1126
* fixed non-working subquery index optimizations
* do not restrict summary of Foxx applications to 60 characters
* fixed display of "required" path parameters in Foxx application documentation
* added more optimizations of constants values in AQL FILTER conditions
* fixed invalid or-to-in optimization for FILTERs containing comparisons
with boolean values
* fixed replication of `_graphs` collection
* added AQL list functions `PUSH`, `POP`, `UNSHIFT`, `SHIFT`, `REMOVE_VALUES`,
`REMOVE_VALUE`, `REMOVE_NTH` and `APPEND`
* added AQL functions `CALL` and `APPLY` to dynamically call other functions
* fixed AQL optimizer cost estimation for LIMIT node
* prevent Foxx queues from permanently writing to the journal even when
server is idle
* fixed AQL COLLECT statement with INTO clause, which copied more variables
than v2.2 and thus lead to too much memory consumption.
This deals with #1107.
* fixed AQL COLLECT statement, this concerned every COLLECT statement,
only the first group had access to the values of the variables before
the COLLECT statement. This deals with #1127.
* fixed some AQL internals, where sometimes too many items were
fetched from upstream in the presence of a LIMIT clause. This should
generally improve performance.
v2.3.0 (2014-11-18)
-------------------
* fixed syslog flags. `--log.syslog` is deprecated and setting it has no effect,
`--log.facility` now works as described. Application name has been changed from
`triagens` to `arangod`. It can be changed using `--log.application`. The syslog
will only contain the actual log message. The datetime prefix is omiited.
* fixed deflate in SimpleHttpClient
* fixed issue #1104: edgeExamples broken or changed
* fixed issue #1103: Error while importing user queries
* fixed issue #1100: AQL: HAS() fails on doc[attribute_name]
* fixed issue #1098: runtime error when creating graph vertex
* hide system applications in **Applications** tab by default
Display of system applications can be toggled by using the *system applications*
toggle in the UI.
* added HTTP REST API for managing tasks (`/_api/tasks`)
* allow passing character lists as optional parameter to AQL functions `TRIM`,
`LTRIM` and `RTRIM`
These functions now support trimming using custom character lists. If no character
lists are specified, all whitespace characters will be removed as previously:
TRIM(" foobar\t \r\n ") // "foobar"
TRIM(";foo;bar;baz, ", "; ") // "foo;bar;baz"
* added AQL string functions `LTRIM`, `RTRIM`, `FIND_FIRST`, `FIND_LAST`, `SPLIT`,
`SUBSTITUTE`
* added AQL functions `ZIP`, `VALUES` and `PERCENTILE`
* made AQL functions `CONCAT` and `CONCAT_SEPARATOR` work with list arguments
* dynamically create extra dispatcher threads if required
* fixed issue #1097: schemas in the API docs no longer show required properties as optional
v2.3.0-beta2 (2014-11-08)
-------------------------
* front-end: new icons for uploading and downloading JSON documents into a collection
* front-end: fixed documents pagination css display error
* front-end: fixed flickering of the progress view
* front-end: fixed missing event for documents filter function
* front-end: jsoneditor: added CMD+Return (Mac) CTRL+Return (Linux/Win) shortkey for
saving a document
* front-end: added information tooltip for uploading json documents.
* front-end: added database management view to the collapsed navigation menu
* front-end: added collection truncation feature
* fixed issue #1086: arangoimp: Odd errors if arguments are not given properly
* performance improvements for AQL queries that use JavaScript-based expressions
internally
* added AQL geo functions `WITHIN_RECTANGLE` and `IS_IN_POLYGON`
* fixed non-working query results download in AQL editor of web interface
* removed debug print message in AQL editor query export routine
* fixed issue #1075: Aardvark: user name required even if auth is off #1075
The fix for this prefills the username input field with the current user's
accout name if any and `root` (the default username) otherwise. Additionally,
the tooltip text has been slightly adjusted.
* fixed issue #1069: Add 'raw' link to swagger ui so that the raw swagger
json can easily be retrieved
This adds a link to the Swagger API docs to an application's detail view in
the **Applications** tab of the web interface. The link produces the Swagger
JSON directly. If authentication is turned on, the link requires authentication,
too.
* documentation updates
v2.3.0-beta1 (2014-11-01)
-------------------------
* added dedicated `NOT IN` operator for AQL
Previously, a `NOT IN` was only achievable by writing a negated `IN` condition:
FOR i IN ... FILTER ! (i IN [ 23, 42 ]) ...
This can now alternatively be expressed more intuitively as follows:
FOR i IN ... FILTER i NOT IN [ 23, 42 ] ...
* added alternative logical operator syntax for AQL
Previously, the logical operators in AQL could only be written as:
- `&&`: logical and
- `||`: logical or
- `!`: negation
ArangoDB 2.3 introduces the alternative variants for these operators:
- `AND`: logical and
- `OR`: logical or
- `NOT`: negation
The new syntax is just an alternative to the old syntax, allowing easier
migration from SQL. The old syntax is still fully supported and will be.
* improved output of `ArangoStatement.parse()` and POST `/_api/query`
If an AQL query can be parsed without problems, The return value of
`ArangoStatement.parse()` now contains an attribute `ast` with the abstract
syntax tree of the query (before optimizations). Though this is an internal
representation of the query and is subject to change, it can be used to inspect
how ArangoDB interprets a given query.
* improved `ArangoStatement.explain()` and POST `/_api/explain`
The commands for explaining AQL queries have been improved.
* added command-line option `--javascript.v8-contexts` to control the number of
V8 contexts created in arangod.
Previously, the number of V8 contexts was equal to the number of server threads
(as specified by option `--server.threads`).
However, it may be sensible to create different amounts of threads and V8
contexts. If the option is not specified, the number of V8 contexts created
will be equal to the number of server threads. Thus no change in configuration
is required to keep the old behavior.
If you are using the default config files or merge them with your local config
files, please review if the default number of server threads is okay in your
environment. Additionally you should verify that the number of V8 contexts
created (as specified in option `--javascript.v8-contexts`) is okay.
* the number of server.threads specified is now the minimum of threads
started. There are situation in which threads are waiting for results of
distributed database servers. In this case the number of threads is
dynamically increased.
* removed index type "bitarray"
Bitarray indexes were only half-way documented and integrated in previous versions
of ArangoDB so their benefit was limited. The support for bitarray indexes has
thus been removed in ArangoDB 2.3. It is not possible to create indexes of type
"bitarray" with ArangoDB 2.3.
When a collection is openend that contains a bitarray index definition created
with a previous version of ArangoDB, ArangoDB will ignore it and log the following
warning:
index type 'bitarray' is not supported in this version of ArangoDB and is ignored
Future versions of ArangoDB may automatically remove such index definitions so the
warnings will eventually disappear.
* removed internal "_admin/modules/flush" in order to fix requireApp
* added basic support for handling binary data in Foxx