Pavel

JanusGraph 0.3.0 implementation

@farodin91 TP tests are skipped It would be nice to run it by adding `[tp-tests]` into commit message

@farodin91 Some info about hbase issue Scan for janusgraph hbase return some data, but metadata say no data exists Scan response ``` hbase:003:0> scan 'janusgraph', {LIMIT => 10} ROW COLUMN+CELL...

@farodin91 Actually root cause is spark https://spark.apache.org/docs/3.2.0/core-migration-guide.html#upgrading-from-core-31-to-32 ``` Since Spark 3.2, spark.hadoopRDD.ignoreEmptySplits is set to true by default which means Spark will not create empty partitions for empty input splits....

@farodin91 3.6 has some breaking changes https://github.com/apache/tinkerpop/blob/master/CHANGELOG.asciidoc - (breaking) mark Do we need to take this into account?

JG has special job for removing ghost vertices `GhostVertexRemover` that job was fixed in here #1731

This type of errors produced because schema removed but data is exists with deleted schema Here snippet that remove entities without schema https://gist.github.com/mad/fdbc29215bc223f7ec33c0eb75d406cb

Berkeleydb just [not implement locking mechanism](https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-berkeleyje/src/main/java/org/janusgraph/diskstorage/berkeleyje/BerkeleyJEKeyValueStore.java#L122) but enable [locking feature](https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-berkeleyje/src/main/java/org/janusgraph/diskstorage/berkeleyje/BerkeleyJEStoreManager.java#L86). And berkeleydb has not test suites for `LockKeyColumnValueStoreTest` JG has [ExpectedValueCheckingStore](https://github.com/JanusGraph/janusgraph/blob/master/janusgraph-core/src/main/java/org/janusgraph/diskstorage/locking/consistentkey/ExpectedValueCheckingStore.java#L55) that's implement locking for store without locking support. Default...

Root cause is it added relations container We use multiples EventListener in our traversal that do some work on newly added/changed vertices. When we add multuple vertices with properties and...

I think current approach may be simplified, for avoid redundant operation we need use `SimpleVertexQueryProcessor` for this label query. I will try this and test And remove new field from...