RC1 ArangoDB 3.4 – What’s new? • Hacker News Board

Re: RC1 ArangoDB 3.4 – What’s new?

#11

Post by e12e » Thu, Sep 06, 2018, 5:52 PM UTC

fulafel wrote: post #10

janemanos wrote: post #9

Earlier quoted context omitted.

The simplest explanation is that ArangoDB uses JSON as dataformat to the outside world. JSON doesn't support these types like arbitrary exact decimal, or timestamps. Despite ArangoDB using VelocyPack internally, which is capabable of much more than JSON, a user will import JSON and get JSON back. You can of course use datetime https://docs.arangodb.com/3.3/AQL/Functions/Date.html and decimals with a precision of 10E3…

MongoDB uses this to express decimals as JSON: { "$numberDecimal": " " }

I suspect creating a specification based on what mongodb does/did might be the better approach - but a quick search for "typed json" turned up:

https://www.tjson.org/

Not sure if I'm a fan of the syntax - but some kind of open, sane, standard would be nice.

Re: RC1 ArangoDB 3.4 – What’s new?

#12

Post by lbhnact » Thu, Sep 06, 2018, 9:33 PM UTC

spamizbad wrote: post #4

Graph database aficionados, I have a question: What's the deal with most graph databases having a very limited number of types? It would be nice if we had more robust numeric types (integers and decimals rather than just doubles) and timestamps for example.

I can't speak for all graph stores, but in addition to ADB being json-native as described below, many graph users describe the types of any value, not just floats or ints, as a relation or property to the value itself.

So you'd never have any value; object, key, value of a string, int, float, or reference, without associated meta-data typing it elsewhere in the graph, and would be unlikely to operate on that data without making reference to those properties.

Re: RC1 ArangoDB 3.4 – What’s new?

#13

Post by emmanueloga_ » Fri, Sep 07, 2018, 12:18 AM UTC

I'm new to ArangoDB but this release looks impressive just by the sheer number of new features. Congrats!

I was wondering if this release allows FULLTEXT indexes when the backend is RocksDB (now that it is the default storage engine)? The new ArangoSearch features look cool, but honestly a bit daunting vs the simple setup of a FULLTEXT index.

By the way, the ArangoSearch tutorial casually talks about "ArangoDB views of type 'arangosearch'", but I haven't come across the concept of views before in the documentation. Are there other types of views?

Re: RC1 ArangoDB 3.4 – What’s new?

#14

Post by hkernbach » Fri, Sep 07, 2018, 2:21 PM UTC

emmanueloga_ wrote: post #13

I'm new to ArangoDB but this release looks impressive just by the sheer number of new features. Congrats! I was wondering if this release allows FULLTEXT indexes when the backend is RocksDB (now that it is the default storage engine)? The new ArangoSearch features look cool, but honestly a bit daunting vs the simple setup of a FULLTEXT index. By the way, the ArangoSearch tutorial casually talks about "ArangoDB views…

Currently there are no other types of views. But they are planned and will follow.