Google Git
Sign in
apache / ignite-3 / refs/heads/cache_poc
commit118b37cc8ddff558c887e33dd33e1076634fc49d[log] [tgz]
authorAlexey Scherbakov <alexey.scherbakoff@gmail.com>Mon Jan 15 17:07:51 2024 +0300
committerAlexey Scherbakov <alexey.scherbakoff@gmail.com>Mon Jan 15 17:07:51 2024 +0300
tree0389764c4ffededb69e5532464cfbda30cbeca1f
parent5c82065bac4a429ec314a9e5ef985e4fe50b4c22 [diff]
Cache transactions recovery
26 files changed
tree: 0389764c4ffededb69e5532464cfbda30cbeca1f
  1. .github/
  2. .idea/
  3. .run/
  4. assembly/
  5. buildscripts/
  6. check-rules/
  7. dev-utilities/
  8. docs/
  9. examples/
  10. gradle/
  11. modules/
  12. packaging/
  13. .asf.yaml
  14. .gitattributes
  15. .gitignore
  16. build.gradle
  17. CONTRIBUTING.md
  18. DEVNOTES.md
  19. gradle.properties
  20. gradlew
  21. gradlew.bat
  22. LICENSE
  23. NOTICE
  24. README.md
  25. RELEASE.md
  26. settings.gradle
README.md

Apache Ignite 3

Apache Ignite 3 is a distributed database for high-performance computing.

  • ACID TRANSACTIONS: Ignite can operate in a strongly consistent mode that provides full support for distributed ACID transactions executed at the Serializable isolation level.
  • DISTRIBUTED SQL: Use Ignite as a traditional SQL database by leveraging JDBC drivers, ODBC drivers, or the native SQL APIs that are available for Java, C#, C++, and other programming languages.
  • COMPUTE API: With traditional databases, for in-place calculations, you use stored procedures that are written in a language such as PL/SQL. With Ignite, you use modern JVM languages to develop and execute custom tasks across your distributed database.
  • SCHEMA-DRIVEN ARCHITECTURE: Ignite built around schema-driven model ensuring consistency between DDL, internal models and data.
  • PLUGABLE STORAGE ENGINES: Ignite's modular architecture enables the customization of underlying data and metadata storage, offering in-memory storage and RocksDB as default options.
  • UNIFIED CLI TOOL AND REST API: Management tools now include built-in CLI and REST API allowing simple access and configuration of Ignite cluster.

Documentation

The latest documentation is generated together with the releases and hosted on the apache site.

Please check the documentation page for more information.

Contact

Ignite is a top level project under the Apache Software Foundation

Download

Latest release artifacts (source release and binary packages) are available from the Ignite web page.

Quick start

Run Ignite from released artifact

To start Ignite you need to download latest zip archive from the Ignite web page. After unpacking it, go to the ignite3-db-3.0.0-beta1 folder and run the following command:

bin/ignite3db start

After that you need to connect to your node with Ignite CLI:

ignite3-cli-3.0.0-beta1/bin/ignite3

In CLI you need to initialize simple cluster via the following command:

cluster init -n=sampleCluster -m=defaultNode

Now CLI can be switched into SQL interactive mode with command:

sql

In SQL interactive mode user can simply type SQL commands in CLI:

CREATE TABLE IF NOT EXISTS Person (id int primary key,  city varchar,  name varchar,  age int,  company varchar);
INSERT INTO Person (id, city, name, age, company) VALUES (1, 'London', 'John Doe', 42, 'Apache');
INSERT INTO Person (id, city, name, age, company) VALUES (2, 'New York', 'Jane Doe', 36, 'Apache');
SELECT * FROM Person;

Build from source

Ignite distributive zip archive can be built with Gradle:

./gradlew clean distZip

Build artifacts can be found in packaging/db and packaging/cli directories.

Run from source using Docker

Ignite can be started with the help of Docker:

./gradlew docker
cd packaging/docker
docker compose up -d

For more information, you can check the Developer notes

Contribute

All contributions are welcome.

  1. Please open a Jira issue
  2. And create a pull request

For more information, you can check the Contribution guideline

License

The Apache Ignite project is licensed under the Apache 2.0 License. See the LICENSE file for details.