• OpenSearch SQL CLI
• Query Compatibility Testing
• SQL CLI
• Features
• Version
• Install
• Startup Commands
• Interactive Mode Commands
• Configuration
• Using the CLI
• Code of Conduct
• Security Issue Notifications
• Licensing
• Copyright

OpenSearch SQL CLI

Interactive command-line interface (CLI) for executing PPL (Piped Processing Language) and SQL queries against OpenSearch clusters. Supports secure and insecure endpoints, AWS SigV4 authentication, autocomplete, syntax highlighting, configurable output formats (Table, JSON, CSV), and saved query history. Easily toggle language modes, SQL plugin versions, and vertical display formatting - all from a single terminal session.

The SQL CLI component in OpenSearch is a stand-alone Python application and can be launched by a 'wake' word opensearchsql.

Users can run this CLI from Unix like OS or Windows, and connect to any valid OpenSearch end-point such as Amazon OpenSearch Service.

Query Compatibility Testing

Users can test their existing queries against newer OpenSearch SQL plug-in versions before upgrading their OpenSearch clusters.

For example, user is currently using version 2.19 may want to validate query compatibility with version 3.1 first.

By using this CLI tool, they can:

• Load and run SQL 3.1 logic locally, without upgrading their OpenSearch cluster.
• Verify that their current queries execute as expected under the new SQL engine.
• Avoid potential breaking changes and reduce the need for rollback in production.

Moreover, developers can use this to test their own SQL plug-in implementation.

This CLI acts as a safe testing environment, allowing smooth transitions between versions with confidence.

SQL CLI

Test and build

Features

• Multi-line input
• Autocomplete for SQL, PPL, index names
• Syntax highlighting
• Formatted output
  • Table
  • JSON
  • CSV
• Field names displayed with color
• Horizontal display for table format
  • Vertical display automatically used when output is too wide
  • Toggle vertical mode on/off with -v
• Connect to OpenSearch
  • Works with or without OpenSearch security enabled
  • Supports Amazon OpenSearch Service domains
• Query operations
  • Execute queries
  • Explain plans
  • Save and load queries
• SQL plugin version selection
  • Maven respository
  • Local directory
  • Git clone
• Command history
  • src/main/python/opensearchsql_cli/.cli_history
• Configuration file
  • src/main/python/opensearchsql_cli/config/config_file.yaml
• SQL plug-in connection log
  • src/main/java/sql_library.log
• Gradle log
  • sqlcli_build.log: SQL CLI jar
  • sql_build.log: SQL Plug-in jar

Version

Unlike plugins which use 4-digit version number. SQl-CLI uses x.x.x as version number same as other python packages in OpenSearch family. As a client for OpenSearch SQL, it has independent release. SQL-CLI should be compatible to all OpenSearch SQL versions. However since the codebase is in a monorepo, so we'll cut and name sql-cli release branch and tags differently. E.g.

release branch: sql-cli-1.0
release tag: sql-cli-v1.0.0 

Prerequisites

Essential Requirements:

• Git - Required for cloning the repository
• Python 3.12+ - Required runtime environment
• pip - Required for installing Python dependencies
• Java 21 - Required Java runtime (Java 21 recommended, Java 24 supported, Java 21 preferred for Amazon Linux)
• OpenSearch cluster with SQL plugin installed

Note for Windows Users: The SQL CLI does not work natively on Microsoft Windows. Windows users can use WSL (Windows Subsystem for Linux) to run the CLI.

📋 For detailed installation instructions for all prerequisites, see PREREQUISITES.md

⚠️Important: Before proceeding with the installation, ensure all prerequisites are installed. If you need help installing any of the required tools (Git, Python 3.12+, pip, Java 21), please follow the detailed instructions in PREREQUISITES.md.

Installation Steps

1. Clone the repository

   git clone https://github.com/opensearch-project/sql-cli
   cd sql-cli

2. Set up Python virtual environment

   python3 -m venv venv
   source ./venv/bin/activate

3. Install dependencies

   pip install -e .

4. Verify Java installation

   java --version

   Expected output (Java 21 or higher):

   openjdk 21.0.2 2024-01-16
   OpenJDK Runtime Environment Temurin-21.0.2+13 (build 21.0.2+13)
   OpenJDK 64-Bit Server VM Temurin-21.0.2+13 (build 21.0.2+13, mixed mode, sharing)
   

5. Set Java environment variables (adjust version number based on your installed Java version)

   macOS:

   export JAVA_HOME=$(/usr/libexec/java_home -v 21)# Use -v 24 for Java 24export PATH=$JAVA_HOME/bin:$PATH

   Linux:

   # Find Java installation
   sudo find /usr -name "java" -type f 2>/dev/null | grep bin
   # Set JAVA_HOME (replace with your Java installation path)export JAVA_HOME=/usr/lib/jvm/java-21-amazon-corretto.x86_64
   export PATH=$JAVA_HOME/bin:$PATH# Make permanentecho'export JAVA_HOME=/usr/lib/jvm/java-21-amazon-corretto.x86_64'>>~/.bashrc
   echo'export PATH=$JAVA_HOME/bin:$PATH'>>~/.bashrc
   source~/.bashrc
   # Switch Java versions (if multiple versions installed)
   sudo alternatives --config java

6. Launch the CLI

   Connection Note: By default, the CLI connects to http://localhost:9200. If you have OpenSearch running locally, you can launch directly. To connect to a remote cluster, use the -e flag with your cluster endpoint.

   # Connect to local OpenSearch cluster (default)
   opensearchsql
   # Connect to remote cluster
   opensearchsql -e https://your-cluster-endpoint

Startup Commands

Defaults: if no arguments provided

• Language: PPL
• Endpoint: http://localhost:9200
• Output Format: Table
• SQL Plugin Version: Latest version

If not specify protocol or port number

• The default protocol is HTTP with port number 9200.
• If using HTTPS without specifying a port, port 443 is used by default.

Options	Description
-e, --endpoint<host:port>	Set the OpenSearch endpoint (e.g., protocol://domain:port)
-u, --user<username:password>	Provide credentials for secure clusters
-k, --insecure	Ignore SSL certificate verification (use with https protocol)
-l, --language<language>	Choose query language: ppl or sql
-f, --format<format>	Set output format: table, json, or csv
-q, --query<query>	Single query execution
--version<version>	Set OpenSearch SQL plugin version (e.g., 3.1, 2.19)
--local<directory>	Use a local directory containing the SQL plugin JAR
--remote<git_url>	Clone from a git repository URL
-b, --branch<branch_name>	Branch name to clone (default is main)
-o, --output<directory>	Custom output directory for cloned repository (used with --remote)
--rebuild	Rebuild or update the corresponding JAR file
-c, --config	Show current configuration values
--help	Show help message and usage examples

Example Usages

# Start with all defaults
opensearchsql
# Use secure endpoint with credentials
opensearchsql -e https://localhost:9200 -u admin:password -k
# Use AWS SigV4 connection
opensearchsql --aws-auth amazon.com
# Use SQL and JSON output
opensearchsql -l sql -f json
# Single query execution
opensearchsql -q "source=index_name"# Load specific plugin version
opensearchsql --version 2.19
# Use a local SQL plugin directory
opensearchsql --local /path/to/sql/plugin/directory
# Use a remote git repository with main branch
opensearchsql --remote "https://github.com/opensearch-project/sql.git"# Use a remote git repository with a specific branch
opensearchsql --remote "https://github.com/opensearch-project/sql.git" -b "feature-branch"# Clone a repository to a custom directory
opensearchsql --remote "https://github.com/opensearch-project/sql.git" -o /path/to/custom/directory

Interactive Mode Commands

Options	Description
<query>	Execute a query
-l <type>	Change language: ppl, sql
-f <type>	Change output format: table, json, or csv
-v	Toggle vertical table display mode
-s --save <name>	Save the latest query with a given name
-s --load <name>	Load and execute a saved query
-s --remove <name>	Remove a saved query by name
-s --list	List all saved query names
help	Show this help message
exit, quit, q	Exit the interactive mode

Version Switching

To use a different OpenSearch SQL plug-in version, you must restart the CLI

Configuration

When you first launch the SQL CLI, a configuration file is automatically loaded.

You can also configure the following connection properties:

Main

Key	Description	Options	Default
multi_line	allows breaking up the statements into multiple lines	true, false	false

Connection Settings

Key	Description	Example	Default
endpoint	OpenSearch URL (http://localhost:9200, https://localhost:9200, or AWS SigV4 endpoint)	localhost:9200	localhost:9200
username	Username for HTTPS authentication (use "" if not set)	"admin"	""
password	Password for HTTPS authentication (use "" if not set)	"admin"	""
insecure	Skip certificate validation (-k flag)	true / false	false
aws_auth	Use AWS SigV4 authentication	true / false	false

⚠️Security Warning: Passwords stored in this file are not encrypted. Consider using -u username:password instead for sensitive environments.

Query Settings

Key	Description	Options	Default
language	Query language	ppl, sql	ppl
format	Output format	table, json, csv	table
vertical	Use vertical table display mode	true / false	false

SQL Version Settings

Key	Description	Example	Default
version	Use Maven repository version (as a string)	"3.1"	""
local	Use local JAR files with absolute path	"/path/to/sql/plugin/directory"	""
remote	Git repository URL to clone	"https://github.com/opensearch-project/sql.git"	""
branch_name	Branch name to clone from the repository	"feature-branch"	""
remote_output	Custom directory for cloned repository	"/path/to/custom/directory"	""

SQL Plugin Settings

Key	Description	Default
QUERY_SIZE_LIMIT	Maximum number of rows returned per query	200
FIELD_TYPE_TOLERANCE	Tolerate field type mismatches	true
CALCITE_ENGINE_ENABLED	Enable the Calcite SQL engine	true
CALCITE_FALLBACK_ALLOWED	Fallback to legacy engine if Calcite fails	true
CALCITE_PUSHDOWN_ENABLED	Enable pushdown optimization in Calcite	true
CALCITE_PUSHDOWN_ROWCOUNT_ESTIMATION_FACTOR	Row count estimation factor for pushdown	1.0
SQL_CURSOR_KEEP_ALIVE	Cursor keep-alive time in minutes	1

Note: PPL Calcite result is limited by QUERY_SIZE_LIMIT number

File Paths

Key	Description	Default Path
sql_log	SQL library log	src/main/java/sql_library.log
history_file	CLI command history	src/main/python/opensearchsql_cli/.cli_history
saved_query	Saved query	src/main/python/opensearchsql_cli/query/save_query/saved.txt

Custom Colors

The CLI supports customizing the colors of various UI elements through the config file. You can modify these settings to match your terminal theme or personal preferences.

Color format: "bg:<background_color> <text_color> [style]" where colors are hex values and style can be bold, italic, etc.

For a list of all available configurations, see config.yaml.

Using the CLI

1. Save the sample accounts test data file.

2. Index the sample data.

   curl -H "Content-Type: application/x-ndjson" -POST https://localhost:9200/data/_bulk -u admin:< Admin password > --insecure --data-binary "@accounts.json"
   

3. Run a simple SQL/PPL command in OpenSearch SQL CLI:

   # PPL
   source=accounts
   # SQLSELECT*FROM accounts

The CLI supports all types of query that OpenSearch PPL/SQL supports. Refer to OpenSearch SQL basic usage documentation.

Development and Contributing

If you're interested in contributing to this project or running tests:

Running Tests

The project includes an automated build and test system:

# Run all tests with automated cluster setup
./gradlew build

This command will:

• Build the Java and Python components
• Automatically clone/update the OpenSearch SQL repository to ./remote/sql
• Start a test OpenSearch cluster in the background
• Load test data from test_data/accounts.json
• Run all Java and Python tests
• Clean up the test cluster automatically

For detailed development instructions, see:

• Development Guide - Complete developer documentation
• Contributing Guide - How to contribute to the project
• Test Suite Documentation - Testing details

Code of Conduct

This project has adopted an Open Source Code of Conduct.

Security issue notifications

If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our vulnerability reporting page. Please do not create a public GitHub issue for security bugs you report.

Licensing

See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.

Copyright

Copyright OpenSearch Contributors. See NOTICE for details.