Exasol Virtual Schema (Lua)

Abstract read access from Exasol to Exasol via a Virtual Schema.

Features

• Access a local Exasol schema through a Virtual Schema

Table of Contents

Information for Users

• User Guide
• Changelog

Information for Contributors

Requirement, design documents and coverage tags are written in OpenFastTrace format.

• Developer Guide

Runtime Dependencies

Lua Dependencies

Running the Exasol Virtual Schema (Lua) requires an Exasol database with built-in Lua 5.4 or later.

Dependency	Purpose	License
Lua CJSON	JSON parsing and writing	MIT License
remotelog	Logging through a TCP socket	MIT License

remotelog has a transitive dependency to LuaSocket (MIT License). Note that Lua CSON and LuaSocket are pre-installed on an Exasol database.

For local unit testing you need to install them on the test machine though.

Test Dependencies

Unit Test Dependencies

Unit tests are written in Lua.

Dependency	Purpose	License
busted	Unit testing framework	BSD License
Mockagne	Mocking framework	MIT License

Integration Test Dependencies

The integration tests require exasol-testcontainers to provide an Exasol instance. They are written in Java and require version 11 or later.

See also: Java Dependencies.

Build Dependencies

This project has a complex build setup due to the mixture of Lua and Java. Apache Maven serves as the main build tool.

Lua build steps are also encapsulated by Maven.

Dependency	Purpose	License
Amalg	Bundling Lua modules (and scripts)	MIT License
LuaRocks	Package management	MIT License

See also: Java Dependencies.