Apache Ignite 2.3 release adds powerful SQL features
Wednesday, November 1 2017 |
Putting aside the regular bug fixes and performance optimizations, the Apache Ignite 2.3 release brings new SQL capabilities and Ignite persistence improvements that are worth mentioning. (Download it here)
Let’s start with SQL first.
Apache Ignite users have consistently told us that despite all of Ignite’s SQL capabilities, it’s been at times challenging trying to figure out how to start using Ignite as an SQL database.
This was mostly caused by scattered documentation pages, lack of “getting started” guides and tutorials. We’ve remedied this oversight! Thanks to your feedback, all related SQL knowledge has been curated in a single documentation domain.
Are you curious about the SQL scope? Go to the new SQL Reference Overview section!
Cannot wait to learn how the Ignite SQL engine runs internally? We’ve prepared an Architectural Overview section for you.
Simply need to know how to connect to an Ignite cluster from an SQL tool? Here is a tooling section for you.
A closer look: SQL features released in Apache Ignite 2.3
First, we’re proud to deliver support of ALTER TABLE command. Presently, the command allows adding new columns to an SQL schema in runtime — avoiding any cluster restarts. Once a new column is added, it can be turned into an index. Again, in runtime. No restarts!
Another significant addition seen in Ignite 2.3 is the integration with the SQL Line tool that is bundled with every Apache Ignite release and can be used as a default command line tool for SQL-based interactions.
To prove that it’s fairly simple to work with Ignite as with an SQL database using the tool, we recorded a short screencast for you:
Apache Ignite Persistence
Apache Ignite native persistence keeps getting more attention and installs — which is why the community released a feature requested by at least a dozen users. The feature allows enabling the persistence for specific data sets. Before Ignite version 2.3, the persistence could be enabled globally.
Now, it’s up to you to decide which data to persist and which to store in RAM only. The persistence can be configured via data regions as shown below:
This data region will consume up to 500 MB of RAM and will store a superset of data on disk ensuring that no data loss happens in case of a crash or even if there is no more space left in RAM.
Flip through our release notes to see all the changes and improvements available in Apache Ignite 2.3 — and, for sure, download and use this version in production.
Questions, comments? Let me know! Also feel free to ask the Apache Ignite community on our user list.