Description

• Support multi vid_ref_expression in from clause.
• Support uuid in where clause.

issue from vesoft-inc/nebula-java#81

The doc on https://docs.janusgraph.org/basics/schema/#automatic-schema-maker says automatically created property key has data type Object.class

By default, implicitly created edge labels have multiplicity MULTI and implicitly created property keys have cardinality SINGLE and data type Object.class.

However, my testing shows that Default Schema Maker automatically infers the type of propert

This will be a breaking change so needs to be done with a major release.

Currently OperationDetail and OperationField are inner classes within OperationServiceV2. These should be in their own outer classes for ease of serialisation and consistency.

If you do object.association.distinct.other_association, the distinct goes away.

This is probably good for the simple implementation, but we could have a WITH DISTINCT automatically go in there on the second association

2 * X queries vs. 1

currently a single transaction with a batch X of documents does 2 * X SQL queries.
it looks whether the document exists first and then inserts or updates it:

(defrecord JdbcDocumentStore [ds dbtype]
  db/DocumentStore
  (submit-docs [this id-and-docs]            ;;    batch of documents
    ;; ...
    (doseq [[id doc] id-and-docs
      (if-not (do

all of the cors_catch wrapper stuff should be moved to http_request_expansion

Example
https://github.com/Anniepoo/identity/blob/master/prolog/identity/identity.pl

Per discussion in #2743 this class is mis-named.

Also, rename LinkStreamValue to just plain LinkStream.