Released OrientDB v2.2.22

London – June 20, 2017

The OrientDB Team has just released OrientDB v2.2.22

EE-2222

If you are using 2.2.x series, please upgrade your production environments to v2.2.22. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.22) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements, improvements and bug fixes, have a look at the complete OrientDB Changelog.

CORE

– Fixed bug on toLowerCase/toUpperCase that didn’t take care of Localeinfoicon

SERVER

– Fixed bug on server startup when automatic backup plugin is disabledinfoicon

HA

– Starting from this version hot upgrade of servers in cluster is supportedinfoicon

– Fixed issue with server restart in cluster that was stuck on STARTING status

SQL

– Use of indexes for range queries when >= and <= operators are used has been optimisedinfoicon

DOCKER

– Official OrientDB Docker images are now immediately available with the release of OrientDB 2.2.22.

 

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – June 1, 2017

The OrientDB Team has just released OrientDB v2.2.21

EE-2221

If you are using 2.2.x series, please upgrade your production environments to v2.2.21. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.21) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements, improvements and bug fixes, have a look at the complete OrientDB Changelog.

CORE

– Fixed bug on file management after restoring a 2.1.x backup on 2.2.x

STUDIO

– Fixed bug on client blocked in case of error on message reading

GRAPH

– Fixed integration with gremlin for result set of collectionsinfoicon

HIGH AVAILABILITY

– Improved performance of messages exchange
– Fixed locking problem with distributed transactions
– Fixed OSGi dependency of distributed module from graphdb

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – May 11, 2017

The OrientDB Team has just released OrientDB v2.2.20

EE-2220

If you are using 2.2.x series, please upgrade your production environments to v2.2.20. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.20) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements, improvements and bug fixes, have a look at the complete OrientDB Changelog.

CORE

– Fixed retain of storage instance in the profile after close/deleteinfoicon

STUDIO

– Fixed Bug in CSV downloadinfoicon

LUCENE

– Fixed bug on date range queriesinfoicon

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – April 26, 2017

The OrientDB Team has just released OrientDB v2.2.19

EE-2218

If you are using 2.2.x series, please upgrade your production environments to v2.2.19. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.19) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements, improvements and bug fixes, have a look at the complete OrientDB Changelog.

SQL

– Supported wildcards in exclude() and include() functionsinfoicon
– New -force and -full options in HA SYNC DATABASE commandinfoicon

HA

– Improved distributed logs. Information on who is the coordinator server are now printed
– Added timeout in every lock request

Core

– Improved statistic of byte buffer exposed through JMX

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – April 6, 2017

The OrientDB Team has just released OrientDB v2.2.18

EE-2218

If you are using 2.2.x series, please upgrade your production environments to v2.2.18. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.18) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements, improvements and bug fixes, have a look at the complete OrientDB Changelog.

Console

– New LOAD SCRIPT commandinfoicon

Studio

– New studio notifications and enhancements
– Fixed Match visualisation issues
– Fixed visibility issue in Backup Management with Firefox/IE

Core

– Added access of active Intent on database

Lucene

– Fixed NPE in index cursorinfoicon

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – February 17, 2017

The OrientDB Team has just released OrientDB v2.2.17

If you are using 2.2.x series, please upgrade your production environments to v2.2.17. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.17) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements and improvements, view the new OrientDB Changelog.

Important Notes

– A critical issue which may lead to corruption of records during update was fixed. We recommend all users and Customers running OrientDB 2.2 upgrade to v.2.2.17.

Scripts

– New ‘delay’ option in stresstester script.
– Increase the default heap size on console.sh/.bat to 1GB and let configure via variable ORIENTDB_OPTS_MEMORY.

JDBC

– Improve interaction with managemnt tools about database metadata.

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – February 3, 2017

The OrientDB Team has just released OrientDB v2.2.16.

 

If you are using 2.2.x series, please upgrade your production environments to v2.2.16. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.16) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

For a complete list of enhancements and improvements, view the new OrientDB Changelog.

Scripts

– “logs” command has been added in orientdb.sh – Community Contribution #7130.

HA

– More verbose logs when the download of a database is skipped because autoDeploy=false.
– Removed the ping to Hazelcast servers by default.

Graph

– Fixed regression introduced in 2.2.15 during vertex delete that caused stale pointers – Issue #7118.
– Fixed graph query of properties with kebab-case issue – Issue #7128.

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – January 19, 2017

The OrientDB Team has just released OrientDB v2.2.15.

 

If you are using 2.2.x series, please upgrade your production environments to v2.2.15. View our Change Log for a full list of new functionalities, bug fixes and other improvements.

Download The Latest OrientDB (v2.2.15) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements (view Changelog)

  1. The Schema panel within Studio has been improved: now there are two main class categories: “User” Class and “System” Class. The “User” Class now has additional separation between “Vertex“, “Edge” and “Generic” Classes.
  2. New forms to create Vertex, Edge and Generic Classes, along with their buttons, have been added in the Schema panel in Studio. It is now possible to specify the number of clusters during class creation.

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

London – January 16th, 2017

By OrientDB CEO, Luca Garulli

After ransomware groups recently wiped off about 34,000 MongoDB database and exposed about 35,000 Elastic Search databases on the Internet*(read the full article), we advise that OrientDB users double check their OrientDB server.

OrientDB’s average level of security is much stronger than both MongoDB and ElasticSearch. However, nothing can keep you totally safe, specially if you are exposing an OrientDB server directly to the Internet and/or you haven’t changed the default password in your database.

Follow this 5 minute action plan to keep your OrientDB database safe:

1. If you aren’t using the default users (admin, reader and writer), then delete them.

2. If you’re using them, be sure you changed the password for all 3 default users: admin, reader and writer.

3. When you installed OrientDB for the first time, the script asked for the root password. Make sure you didn’t set something obvious such as “root“, “orientdb“, “password“, or any other simple/obvious password.

Now a little advice to keep OrientDB even more secure:

1. If you can, don’t expose the OrientDB server to the Internet.security-box

2. Remember that starting from v2.2 you can configure stronger SALT cycles for hashed passwords. Take a look at the following page for more details: https://orientdb.com/docs/2.2/Database-Security.html#password-management.

3. If you’re working with very sensitive data, please consider using Encryption at REST with AES algorithm. For more details, take a look at the following page: http://orientdb.com/docs/2.2/Database-Encryption.html.

4. Don’t use a password at all. Since v2.2.14, OrientDB Enterprise Edition supports authentication via symmetric keys for the Java client. See https://orientdb.com/docs/2.2/Security-Symmetric-Key-Authentication.html.

5. Lastly, don’t forget OrientDB’s other advanced security features, such as Kerberos authentication, LDAP users, password validation, and auditing.

More Resources:

  1. Database Security
  2. Server Security

For any question, don’t hesitate to ask to the Community Group.

Thanks and keep your data safe!

Luca Garulli
Founder & CEO
OrientDB LTD

*http://www.pcworld.com/article/3157417/security/after-mongodb-ransomware-groups-hit-exposed-elasticsearch-clusters.html

London – December 23, 2016

The OrientDB Team has just released OrientDB v2.2.14, resolving 32 issues from v2.2.13.

 

If you are using 2.2.x series, please upgrade your production environments to v2.2.14. For more information, take a look at the Change Log.

Download The latest OrientDB (v2.2.14) version:

https://orientdb.com/download

If you are currently using a previous version of OrientDB, we recommend you upgrade using the link above. However, if you would like to download previous versions of OrientDB Community Edition, you may do so here: https://orientdb.com/download-previous/

Noteworthy Enhancements

  1. Symmetric Key Authentication:  As of OrientDB 2.2.14 Symmetric Key Authentication has been provided as an Enterprise only feature.
  2. Along with OrientDB 2.2.14 we have also released an new version of the Neo4j to OrientDB Importer. For those working in the Biometrics industry,  this latest version includes enhancements that allow for more efficient Reactome database migrations. The Reactome database is an open source curated pathway database that provides pathway and network analysis tools for life science researchers. Other enhancements include:

– Enhancements for Neo4j migrations in case original nodes have multiple Labels

– Improvements in migration speeds.

Team and Contributors

A big thank you goes out to the OrientDB team and all the contributors who worked hard on this release, providing pull requests, tests, issues and comments.

Best regards,

Luigi Dell’Aquila
Director of Consulting
OrientDB LTD

Take your enterprise to the next level with OrientDB