Skip to content

Version Features Summary

Jump to bottom
YANGDB edited this page Sep 28, 2020 · 12 revisions

Plannen Features V0.53

  • Add DDL (SQL schema) to V1 ontology conversion
  • Add DB import table support data ingestion
  • Add physical DB schema creation based on V1 ontology (concrete entity to index mapping)
  • Add nested document physical schema structure support for yangDb concrete mapping with E/S
  • Add support for sniffer yangDb-client access to a yangDb cluster
  • replace restAsure with gRPC support for better serialization and compression

Plannen Features V0.52

  • Add Temporal Event Processing Predicates such as: EVERY, FOLLOWED_BY, WITHIN to support time based patterns operators
  • Adding facets & aggregation language support to V1 language - simplify query for none graph queries
  • Adding support for materializaiton (persist) of a query cursor data (projection) into non-volotile DB such as Redis or apache-Ignite or Elastic temp Index
  • Adding support for structured cache of query cursor results (projection) into a structured index representing the actual logical hirarchy (tree-like graph projection) of the data - in order to enable E/S piped aggregations and facets queries

Adding concrete implementation for specific columns projections according to Query

  • Implementing the projected columns according to the fields projected in the actual query
  • Adding CSV to RDF support for data ingestion
  • Adding JSON to RDF support for data ingestion
  • Adding XML to RDF support for data ingestion

Enable multi sources federated query against external schemas / API

Plannen Features V0.51 - Currently - Work In Progress

multi-QL endpoint - this will enable any type of graph based language (cypher, gremlin, V1, Sparql, graphQL) to run against yangDb and return the logical graph/assigbnments.

  • OWL ontology translator - this will translate to / from V1 ontology languege the OWL schema
  • SPARQL query translator - this will translate to V1 query language and enable query against the DB
  • JSONLD graph translation - this will translate JsonLD format to / from standard json query results

Adding GraphQL Internal Domain entities representation

  • All public domain entities & API will be translated into graphQL entities & mutations

Adding specific columns projections according to Query

  • Adding the projected columns according to the fields projected in the actual query

Adding parent type notion to V1 query (ETyped entity, Relation type)

  • Add explicit physical E/S schema mapping (GraphLayoutProviderFactory) for a single index support - relations are mapped into same index
  • Adding the parent type will produce and enable inference of properties from parents

Adding Cyber assembly resource with sample cyber ontology and index support

Adding OpenSource Visual Query tools support & Usage examples:

Completed Features V0.5

The Features just completed in the latest version:

Adding a profile ability to view cursors physical query against the actual E/S Database

  • Each Query Step is displayed with the tagged name it was assigned and shows the count of the elements (documents) fetched from the database along with the actual elasticsearch query that was called

Adding a Kibana operational dashboard to view yangDb realtime execution matrix Adding GraphQL query support

  • add GraphQL IDL schema translation into V1 Ontology
  • add GraphQL query translation into V1 query language
  • add input type where clause default support for every GraphQL entity

Inner Query support

  • add depended inner query - the inner query results are the base of the outer query constraints
  • add $eval evaluator that will evaluate constraint values in place during query execution
  • Fix: Fixed the findPath between two nodes so that any requeired constraint can be assigned to the relationship/s between the nodes
  • Fix: Fixed Cursor Type ForwardOnly to inspect cycles within the returning assignments
Clone this wiki locally