Orient Technologies - OrientDB Distributed Graph Database http://www.orientechnologies.com OrientDB Distributed Graph Database Tue, 15 Apr 2014 19:38:03 +0000 en-US hourly 1 Transaction Lockshttp://www.orientechnologies.com/pessimistic-optimistic/?utm_source=rss&utm_medium=rss&utm_campaign=pessimistic-optimistic http://www.orientechnologies.com/pessimistic-optimistic/#comments Mon, 31 Mar 2014 22:17:08 +0000 http://www.orientechnologies.com/?p=9182 London, March 31st 2014   I’ve silently introduced a new feature in OrientDB (well, there was an issue, but I know somebody is not […]

The post Transaction Locks appeared first on Orient Technologies - OrientDB Distributed Graph Database.

]]>
London, March 31st 2014
 

I’ve silently introduced a new feature in OrientDB (well, there was an issue, but I know somebody is not registered to GitHub notification). It’s about Transactions and Locking. Now every time you expressly lock records, all the locks are kept on the current transaction until the closing by commit() or rollback(). This means that it’s finally possible avoiding concurrent updates.

The real question is: “Is it better to be Optimistic or Pessimistic with transactions?”

  • Optimistic (like CAS) avoiding locking and resolve conflicts by re-executing the transaction with a retry policy or
  • Pessimistic by locking the records, apply changes and then unlock them

 

The response is up to you, or better, to your use case. In general the Optimistic approach is preferable on modern multi-core architecture, but on massive updates against few records locking could take the best performance.

Look at this micro-benchmark.

This feature along with the new server side SQL batch, give us a lot of power. Let’s see how to create an edge with Pessimistic approach (locking) and with Optimistic approach (CAS).

Pessimistic approach

begin
let $client = create vertex Client set name = ‘Luca’
let $city = select from City where name = ‘London’ lock record
let $e = create edge Lives from $client to $city
commit

 

Optimistic approach

begin
let $client = create vertex Client set name = ‘Luca’
let $city = select from City where name = ‘London’
let $e = create edge Lives from $client to $city retry 100
commit

 
Now it’s up to you choosing the best approach for your use case.
 
Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

http://about.me/luca.garulli

 

 

The post Transaction Locks appeared first on Orient Technologies - OrientDB Distributed Graph Database.

]]>
http://www.orientechnologies.com/pessimistic-optimistic/feed/ 0
New SQL command batchhttp://www.orientechnologies.com/new-sql-command-batch/?utm_source=rss&utm_medium=rss&utm_campaign=new-sql-command-batch http://www.orientechnologies.com/new-sql-command-batch/#comments Mon, 31 Mar 2014 18:54:01 +0000 http://www.orientechnologies.com/?p=9169 Hi all, OrientDB allowed to execute arbitrary script written in Javascript or any scripting language installed in the JVM. Well, starting from now we […]

The post New SQL command batch appeared first on Orient Technologies - OrientDB Distributed Graph Database.

]]>
Hi all,

OrientDB allowed to execute arbitrary script written in Javascript or any scripting language installed in the JVM. Well, starting from now we created a minimal SQL engine to allow batch of commands. Batch of commands are very useful when you have to execute multiple things at the server side avoiding the network roundtrip for each command. Example to create a new vertex in a transaction and attach it to an existent vertex by creating a new edge between them:

 

begin
let account = create vertex Account set name = ‘Luke’
let city = select from City where name = ‘London’
let edge = create edge Lives from $account to $city retry 100
commit
return $edge

 

It’s plain OrientDB SQL, but with a few news:
  • begin -> begins a transaction
  • rollback -> rollbacks an active transaction
  • commit -> commits an active transaction
  • let <variable> = <command> -> executes a command and assign it in the context as . That variable can be used in further commands by prefixing it with $
  • return <variable>|<value>|null -> returns a value instead of last command result (default)
Note also the usage of $account and $city on further SQL commands.

 

Java API

 

This can be used by Java API with:
database.open("admin", "admin");

String cmd = "begin\n";
cmd += "let a = create vertex set script = true\n";
cmd += "let b = select from v limit 1\n";
cmd += "let e = create edge from $a to $b retry 100\n";
cmd += "commit\n";
cmd += "return $e";

OIdentifiable edge = database.command(new OCommandScript("sql", cmd)).execute();

 

Remember to put one command per line (postfix it with \n).

 

HTTP REST API

 

And via HTTP REST interface (https://github.com/orientechnologies/orientdb/issues/2056). Execute a POST against /batch URL by sending this payload:

 

{ "transaction" : true, 
  "operations" : [ 
    {
      "type" : "script",
      "language" : "sql",
      "script" : [ "let account = create vertex Account set name = 'Luke'",
                   "let city =select from City where name = 'London'",
                   "create edge Lives from $account to $city retry 100" ]
    }
  ]
}

 

Hope this new feature will simplify your development improving performance.

 

What about having more complex constructs like IF, FOR, etc? If you need more complexity, I suggest you to use Javascript as language that already support all these concepts.

 

Luca Garulli
CEO at Orient Technologies
the Company behind OrientDB

http://about.me/luca.garulli

 

 

The post New SQL command batch appeared first on Orient Technologies - OrientDB Distributed Graph Database.

]]>
http://www.orientechnologies.com/new-sql-command-batch/feed/ 0
Released OrientDB 1.7-rc2: new Query Timeline in Studio and 62 bug fixedhttp://www.orientechnologies.com/released-orientdb-1-7-rc2-new-query-timeline-studio-62-bug-fixed/?utm_source=rss&utm_medium=rss&utm_campaign=released-orientdb-1-7-rc2-new-query-timeline-studio-62-bug-fixed http://www.orientechnologies.com/released-orientdb-1-7-rc2-new-query-timeline-studio-62-bug-fixed/#comments Tue, 25 Mar 2014 16:03:49 +0000 http://www.orientechnologies.com/?p=8980 Orient Technologies has just released the second and last Release Candidate for OrientDB v1.7. To download OrientDB 1.7-rc2 goto: http://www.orientechnologies.com/download/ So what’s new? This […]

The post Released OrientDB 1.7-rc2: new Query Timeline in Studio and 62 bug fixed appeared first on Orient Technologies - OrientDB Distributed Graph Database.

]]>
Orient Technologies has just released the second and last Release Candidate for OrientDB v1.7.

To download OrientDB 1.7-rc2 goto:

http://www.orientechnologies.com/download/

So what’s new?

This release is more focused on bug fixing. We fixed a total of 62 bugs! Then we provided a brand new GUI in the Query panel of Studio by using a Timeline-like approach (taken by social networks) to manage the query history. I hope this will improve your productivity with queries.

Below the main enhancements:

    • Core:
      • supported retro-compatibility for databases created with OrientDB v1.5 or further (#1899)
      • improved performance on ORDER BY against indexes (#1843)
      • improved performance on RENAME CLASS (#1818)
    • Graph:
      • added support for vertex-centric traversal by using SQL (#2079)
    • SQL:
      • new UPSERT keyword to execute an INSERT or UPDATE based on a condition (#2032)
      • UPDATE now can ADD also to sub-document fields (#2031)
    • Indexes:
      • added support for external engines (#1774)
    • Studio:
      • new Query Timeline to the History, new Index Panel, Fixed many bugs

     

    Full list of closed issues.
     

    Enterprise Edition

    OrientDB Community Edition is FREE for any usage. If you wan additional features and Professional support, ask for a trial of Enterprise Edition: Enterprise Edition.

    Have fun with Graphs,

    Luca Garulli
    CEO at Orient Technologies
    the Company behind OrientDB

    http://about.me/luca.garulli

     

    The post Released OrientDB 1.7-rc2: new Query Timeline in Studio and 62 bug fixed appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]> http://www.orientechnologies.com/released-orientdb-1-7-rc2-new-query-timeline-studio-62-bug-fixed/feed/ 0 Walk through the graphhttp://www.orientechnologies.com/walk-graph/?utm_source=rss&utm_medium=rss&utm_campaign=walk-graph http://www.orientechnologies.com/walk-graph/#comments Sun, 02 Mar 2014 00:28:58 +0000 http://www.orientechnologies.com/?p=8392 The release of OrientDB 1.7-rc2 is very close. We’ve fixed many bugs, supported binary compatibility against older versions (up to v1.5) and we introduced […]

    The post Walk through the graph appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    The release of OrientDB 1.7-rc2 is very close. We’ve fixed many bugs, supported binary compatibility against older versions (up to v1.5) and we introduced a new interesting feature: walking into the graph. When you execute a query you get back a resultset:

    orientdb {GratefulDeadConcerts}> select from v where type = ’artist’

    ________________________________________________________________
    #   |@RID  |in_written_by|in_sung_by|name                |type  
    ________________________________________________________________
    0   |#9:7  |[size=9]     |[size=7]  |Bo_Diddley          |artist
    1   |#9:8  |[size=4]     |[size=146]|Garcia              |artist
    2   |#9:9  |#9:2         |[size=2]  |Spencer_Davis       |artist
    3   |#9:27 |#9:3         |null      |Hardin_Petty        |artist
    4   |#9:50 |[size=4]     |[size=99] |Weir                |artist
    5   |#9:93 |[size=96]    |[size=3]  |Hunter              |artist
    6   |#9:131|[size=39]    |null      |Traditional         |artist
    7   |#9:136|#9:135       |null      |West_Tilghman_Holly |artist
    8   |#9:169|[size=2]     |null      |Jesse_Fuller        |artist
    9   |#9:174|[size=28]    |null      |Barlow              |artist
    10  |#9:179|#9:88        |null      |John_Phillips       |artist
    11  |#9:183|null         |[size=3]  |Weir_Hart           |artist
    12  |#9:208|#9:99        |null      |Johnny_Cash         |artist
    13  |#9:218|#9:102       |null      |Marty_Robbins       |artist
    14  |#9:222|#9:139       |null      |Don_Rollins         |artist
    15  |#9:223|null         |#9:14     |Garcia_Lesh_Weir    |artist
    16  |#9:233|#9:96        |null      |Kristofferson_Foster|artist
    17  |#9:245|[size=5]     |null      |Chuck_Berry         |artist
    18  |#9:258|null         |[size=8]  |Pigpen_Weir         |artist
    19  |#9:261|#9:69        |null      |Robert_Johnson      |artist
    ________________________________________________________________
    LIMIT EXCEEDED: resultset contains more items not displayed (limit=20)

    20 item(s) found. Query executed in 0.031 sec(s).

     
    After a query, the current record is always the first one in the resultset. To display it, use the new “current” command:
     

    orientdb {GratefulDeadConcerts}> current

    __________________________________________________
    ODocument _ Class: V   id: #9:7   v.19
    __________________________________________________
           in_written_by : [size=9]            
              in_sung_by : [size=7]            
                    name : Bo_Diddley          
                    type : artist

     
    To move to the next record, use the new “next” command:
     

    __________________________________________________
    ODocument _ Class: V   id: #9:8   v.153
    __________________________________________________
              in_sung_by : [size=146]          
           in_written_by : [size=4]            
                    name : Garcia              
                    type : artist              

     
    To go back in the result, use “prev”. Now, to move to the incoming ‘written_by’ vertices, before 1.7-rc2 we had to issue another query by using the current RID:

    select in(‘written_by’) from #9:8



    But now we can simply “move” to them by using the new “move” console command:
     

    orientdb {GratefulDeadConcerts}> move in(‘written_by’)

    _______________________________________________________________________________________________________________________
    @RID  |#   |type|in_followed_by|name                 |song_type|performances|out_followed_by|out_sung_by|out_written_by
    _______________________________________________________________________________________________________________________
    #9:461|1   |song|null          |CANT COME DOWN       |original |1           |null           |#9:335     |#9:8          
    #9:465|2   |song|null          |CREAM PUFF WAR       |original |7           |null           |#9:8       |#9:8          
    #9:494|3   |song|null          |THE ONLY TIME IS NOW |original |1           |null           |#9:335     |#9:8          
    _______________________________________________________________________________________________________________________


    After this command, the resultset has been updated with those records and the current record is the first one. Now we can continue walking into the graph, through incoming or outgoing edges, vertices or even links.

    Cool, right?

    Have fun with Graphs,
    Luca Garulli
    CEO at Orient Technologies
    the Company behind OrientDB

    http://about.me/luca.garulli

    The post Walk through the graph appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/walk-graph/feed/ 0
    Released OrientDB v1.7 rc1: new relationship engine, improved SQL and Graph APIhttp://www.orientechnologies.com/released-orientdb-v1-7-rc1-new-relationship-engine-improved-sql-graph-api/?utm_source=rss&utm_medium=rss&utm_campaign=released-orientdb-v1-7-rc1-new-relationship-engine-improved-sql-graph-api http://www.orientechnologies.com/released-orientdb-v1-7-rc1-new-relationship-engine-improved-sql-graph-api/#comments Thu, 06 Feb 2014 11:56:27 +0000 http://www.orientechnologies.com/?p=7787 Orient Technologies has just released OrientDB v1.7-rc1. This is the first Release Candidate of the version 1.7, other Release Candidate will follow in the […]

    The post Released OrientDB v1.7 rc1: new relationship engine, improved SQL and Graph API appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    Orient Technologies has just released OrientDB v1.7-rc1. This is the first Release Candidate of the version 1.7, other Release Candidate will follow in the next weeks.

    To download OrientDB 1.7 rc1 goto:

    http://www.orientechnologies.com/download/

    So what’s new?

    The most important news is the new engine to manage Relationships. We knew the biggest OrientDB’s bottleneck was on management of vertices with many edges. Andrey posted a benchmark about importing Wikipedia dataset comparing the new OrientDB 1.7-rc1 and previous OrientDB 1.6.4. In all the tests the new version outperforms the previous one, even 15x! No more pain on managing many edges!

    Benchmark OrientDB v1.7-rc1 vc 1.6.4: http://www.orientechnologies.com/first-benchmark-new-architecture-relationship-management/

    Other news are mostly related to increase the power and expressiveness of OrientDB SQL language and Graph model.

    Below all the enhancements:

      • Engine:
        • new LINKBag to manage LINKS by using SBTree indexes. This drastically improved performance
      • SQL:
        • new LOCK keyword to specify locking strategy
        • new RETURNING keyword to let to UPDATE and DELETE commands to return modified records
        • new include() and exclude() to respectively include or exclude fields of documents
        • operator [] now can be used in chain, also with functions
        • projections can be reused as variables
        • support for LET also in UPDATE and DELETE commands
      • Graph API:
        • support for ordered edge list
        • new detach() and attach() method to work with Graph Element offline
        • new OrientGraphFactory to manage pooled instances
      • HTTP:
        • new support for ETagIf-Match and If-None-Match headers
        • new PATCH method against /document command and /documentbyclass for partial updates
      • Distributed: database deploy now is chunked to avoid RAM saturation
      • Backup and Restore: improved speed from 5x to 50x
      • Studio:
        • new CSV download of Query result
        • Query can return non shallowed collections
      • Fixed reported bugs

     

    Full list of closed issues: https://github.com/orientechnologies/orientdb/issues?milestone=15&page=1&state=closed

    Enterprise Edition

    OrientDB Community Edition is FREE for any usage. If you wan additional features and Professional support, ask for a trial of Enterprise Edition: Enterprise Edition.

    Enjoy Graphs,

    Luca Garulli
    CEO at Orient Technologies
    the Company behind OrientDB

    http://about.me/luca.garulli

     

    The post Released OrientDB v1.7 rc1: new relationship engine, improved SQL and Graph API appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/released-orientdb-v1-7-rc1-new-relationship-engine-improved-sql-graph-api/feed/ 0
    OrientDB 1.7rc1 sneak peek on benchmarkshttp://www.orientechnologies.com/first-benchmark-new-architecture-relationship-management/?utm_source=rss&utm_medium=rss&utm_campaign=first-benchmark-new-architecture-relationship-management http://www.orientechnologies.com/first-benchmark-new-architecture-relationship-management/#comments Wed, 05 Feb 2014 23:26:31 +0000 http://www.orientechnologies.com/?p=7697 London, February 6th 2014   We are glad to announce the new engine to manage relationships in graph database. According to data loading benchmark it […]

    The post OrientDB 1.7rc1 sneak peek on benchmarks appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    London, February 6th 2014

     
    We are glad to announce the new engine to manage relationships in graph database. According to data loading benchmark it can be up to 15 times faster than current implementation!

    The new architecture is based on new data structure SB-Tree and optimized for usage not only for embedded, but for remote storage too. To achieve such kind of optimization we have introduced new data type LINKBAG, it represents set of RIDs, but allows duplication of values, also it does not implement Collection interface. LINKBAG has two binary presentations, in form of modified B-Tree and in form of collection managed as embedded in document, but collection is deserialized only on demand, in case of iteration for example.

    Below the comparison on load speed on importing Wikipedia page structure (without page content) which consist of 130 millions of vertexes and more than 1 billion of edges.

    To prevent duplication of vertexes we used unique index by page key. Data were taken from http://downloads.dbpedia.org/3.6/en/page_links_en.nt.bz2. Load test was ran on PC with 24 Gb RAM, 7500 RPM HDD, Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz.

    Test 1 consists on loading data in Transactional mode, blue line is OrientDB 1.6.x, the red line is OrientDB 1.7-rc1 with the new LINKBAG structure.

    On the X axis there is the amount of imported pages, on the Y axis the time which was spent to import these pages.

    mvrbtree-ridbag-unique-tx

    Test 1 – OrientDB 1.6.x vs OrientDB 1.7-rc1 TX Mode

    As you can see after 6,300,000th imported records the current implementation suffers of dramatic slow down, so we interrupted the test after a while.
    Test 2 is like the previous test, but in non Transactional mode.
    mvrbtree-ridbag-unique-notx

    Test 2 – OrientDB 1.6.x vs OrientDB 1.7-rc1 No-TX Mode

    Test 3 is a comparison between a full import of whole Wikipedia dataset using new LINKBAG implementation. Here the blue line is the Transactional mode and the red line is Non-Transactional mode.
    ridbag-tx-notx

    Test 3 – OrientDB 1.7-rc1 TX vs OrientDB 1.7-rc1 No-TX

    In Non-Transactional mode test was completed in only 6.5 hours and in Transactional mode took 14 hours.

     
    Andrey Lomakin
    Orient Technologies LTD

    The post OrientDB 1.7rc1 sneak peek on benchmarks appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/first-benchmark-new-architecture-relationship-management/feed/ 0
    New OrientDB Graph Factoryhttp://www.orientechnologies.com/new-orientdb-graph-factory/?utm_source=rss&utm_medium=rss&utm_campaign=new-orientdb-graph-factory http://www.orientechnologies.com/new-orientdb-graph-factory/#comments Fri, 31 Jan 2014 11:07:00 +0000 http://www.orientechnologies.com/?p=7630 TinkerPop Blueprints standard doesn’t define a proper “Factory” to get graph instances. For this reason OrientDB users that wanted to use a pool of […]

    The post New OrientDB Graph Factory appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    TinkerPop Blueprints standard doesn’t define a proper “Factory” to get graph instances. For this reason OrientDB users that wanted to use a pool of instances had to mix 2 different API: Graph and Document one. Example:
     

    ODatabaseDocumentPool pool = new ODatabaseDocumentPool(“plocal:/temp/mydb”);
    OrientGraph g = new OrientGraph(pool.acquire());

     
    NOTE: You could also use a OGraphDatabase instance in place of ODatabaseDocumentPool, but this API has been deprecated since a long time and will be removed in v1.7.

     
    Now everything is simpler, thanks to the new OrientGraphFactory class to manage graphs in easy way (Issue #1971). These the main features:
    - by default acts as a factory by creating new database instances every time
    - can be configured to work as a pool, by recycling database instances
    - if the database doesn’t exist, it’s created automatically (but in “remote” mode)
    - returns transactional and non-transactional instances
     
    This is the basic way to create the factory, by using the default “admin” user (with “admin” password by default):
     

    OrientGraphFactory factory = new OrientGraphFactory(“plocal:/temp/mydb”);

     
    But you can also pass user and password:
     

    OrientGraphFactory factory = new OrientGraphFactory(“plocal:/temp/mydb”, “jayminer”, “amigarocks”);

     
    To work with a recyclable pool of instances with minimum 1, maximum 10 instances:
     

    OrientGraphFactory factory = new OrientGraphFactory(“plocal:/temp/mydb”).setupPool(1, 10);

     
    Once the factory is configured you can get a Graph instance to start working. OrientGraphFactory has 2 methods to retrieve a Transactional and Non-Transactional instance:
     

    OrientGraph txGraph = factory.getTx();
    OrientGraphNoTx noTxGraph = factory.getNoTx();

     
    Or again you can configure in the factory the instances you want and use the get() method everytime:
     

    factory.setTransactional(false);
    OrientGraphNoTx noTxGraph = (OrientGraphNoTx) factory.get();

     
    Once finished to free all the resources (in case of pool usage), call the close():
     

    factory.close();

     

    The post New OrientDB Graph Factory appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/new-orientdb-graph-factory/feed/ 0
    New detach() and attach() methods on Graph APIhttp://www.orientechnologies.com/new-detach-attach-methods-graph-api/?utm_source=rss&utm_medium=rss&utm_campaign=new-detach-attach-methods-graph-api http://www.orientechnologies.com/new-detach-attach-methods-graph-api/#comments Thu, 30 Jan 2014 16:03:07 +0000 http://www.orientechnologies.com/?p=7606 When you work with Web Applications, it’s very common to query elements and render them to the user to let him to apply some […]

    The post New detach() and attach() methods on Graph API appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    When you work with Web Applications, it’s very common to query elements and render them to the user to let him to apply some changes. Once the user updates some fields and press the “save” button, what happens?

    Before now the developer had to track the changes in a separate structure, load the vertex/edge from the database and apply the changes to the element.

    Starting from OrientDB v1.7 we added 2 new methods to the Graph API against OrientElement and OrientBaseGraph classes:

    • - OrientElement.detach()
    • - OrientElement.attach()
    • - OrientBaseGraph.detach( OrientElement )
    • - OrientBaseGraph.attach( OrientElement )

    Detach

    Detach methods fetch all the record content in RAM and reset the connection to the Graph instance. This allow to modify the element off-line and re-attach it once finished.

    Attach

    Once the detached element has been modified, to be saved back to the database you need to call the attach() method. It restore back the connection between the Graph Element and the Graph Instance.

    Example

    The first step is load some vertex and detach them.

     

    OrientGraph g = OrientGraph(“plocal:/temp/db”);
    try{
      Iterable<OrientVertex> results = g.query().has(“name”, EQUALS, ‘fast’);
      for( OrientVertex v : results )
        v.detach();
    } finally {
      g.shutdown();
    }

    After a while the element is updated (from GUI or by application)

     

    v.setProperty(“name”, “super fast!”);

    On “save” button re-attach the element and save it to the database.

     

    OrientGraph g = OrientGraph(“plocal:/temp/db”);
    try{
      v.attach( g ); v.save();
    } finally {
      g.shutdown();
    }

    FAQ

    Does detach go recursively to detach all connected elements?

    No, it works only at the current element level.

    Can I add edge against detached elements?

    No, you can only get/set/remove property while is detached. Any other operation that requires the database will throw an IllegalStateException.

     

    The post New detach() and attach() methods on Graph API appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/new-detach-attach-methods-graph-api/feed/ 0
    Released OrientDB 1.6.4: hot-fix + merged Blueprintshttp://www.orientechnologies.com/released-orientdb-1-6-4/?utm_source=rss&utm_medium=rss&utm_campaign=released-orientdb-1-6-4 http://www.orientechnologies.com/released-orientdb-1-6-4/#comments Wed, 15 Jan 2014 23:32:23 +0000 http://www.orientechnologies.com/?p=7221 London, January 16 2014 Orient Technologies has just released OrientDB 1.6.4 as hot-fix + the integration with Blueprints. Yes, starting from 1.6.4 the Blueprints […]

    The post Released OrientDB 1.6.4: hot-fix + merged Blueprints appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    London, January 16 2014

    Orient Technologies has just released OrientDB 1.6.4 as hot-fix + the integration with Blueprints.

    Yes, starting from 1.6.4 the Blueprints implementation has been moved inside the “graphdb” module to avoid all the alignment problems between OrientDB and Blueprints versions.

    To download it: Download. For the complete list of fixed issues: Change Log.

    Luca Garulli
    CEO at Orient Technologies
    the Company behind OrientDB

    http://about.me/luca.garulli

     

    The post Released OrientDB 1.6.4: hot-fix + merged Blueprints appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/released-orientdb-1-6-4/feed/ 0
    Released OrientDB 1.6.3http://www.orientechnologies.com/released-orientdb-1-6-3/?utm_source=rss&utm_medium=rss&utm_campaign=released-orientdb-1-6-3 http://www.orientechnologies.com/released-orientdb-1-6-3/#comments Fri, 27 Dec 2013 19:11:18 +0000 http://www.orientechnologies.com/?p=6613 London, December 27th, 2013 Christmas time doesn’t stop OrientDB Team to work on releasing the new version 1.6.3! This is the third hot-fix for v1.6.x. This […]

    The post Released OrientDB 1.6.3 appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    London, December 27th, 2013

    Christmas time doesn’t stop OrientDB Team to work on releasing the new version 1.6.3! This is the third hot-fix for v1.6.x. This is the Change Log.
    To download it go to http://www.orientdb.org/download.htm or update your Maven pom.xml to point to the version 1.6.3.
    Merry Christmas and Happy New Year!
     
    Luca Garulli
    CEO at Orient Technologies
    the Company behind OrientDB

    The post Released OrientDB 1.6.3 appeared first on Orient Technologies - OrientDB Distributed Graph Database.

    ]]>
    http://www.orientechnologies.com/released-orientdb-1-6-3/feed/ 0