SCRIPT EXISTS - Upstash Documentation

Use SCRIPT EXISTS to check which of the given SHA1 digests are present in the script cache.

The reply holds one 1 or 0 per digest, in the order they were given. Client libraries use it to find out, in a single call, which of their scripts still need to be loaded before they can be invoked with EVALSHA, instead of discovering the gap through a NOSCRIPT error at call time.

Syntax#

SCRIPT EXISTS <sha1> [<sha1> ...]

Arguments#

Argument	Required	Repeatable	Description
`<sha1>`	Yes	Yes	SHA1 digest of a script cached with `SCRIPT LOAD`.

Response#

The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.

Protocol	Reply
RESP2	Array of integers, one per SHA1 digest
RESP3	Array of integers, one per SHA1 digest

Note

Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.

Examples#

TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.

Redis CLI

SCRIPT EXISTS fb67a0c03b48ddbf8b4c9b011e779563bdbc28cb

REST API

First, load the script. The response contains its SHA1 digest, 098e0f0d1448c0a81dafe820f66d460eb09263da.

curl -X POST "$UPSTASH_REDIS_REST_URL" \  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \  -H "Content-Type: application/json" \  -d '["SCRIPT", "LOAD", "return ARGV[1]"]'# Check whether the script is cached.curl -X POST "$UPSTASH_REDIS_REST_URL" \  -H "Authorization: Bearer $UPSTASH_REDIS_REST_TOKEN" \  -H "Content-Type: application/json" \  -d '["SCRIPT", "EXISTS", "098e0f0d1448c0a81dafe820f66d460eb09263da"]'

The second response is { "result": [1] } while the script is cached, or { "result": [0] } if it has been removed. See REST API for request and response conventions.

@upstash/redis

import { Redis } from "@upstash/redis";const redis = Redis.fromEnv();await redis.scriptExists("<sha1>", "<sha2>")// Returns 1// [1, 0]

upstash_redis

from upstash_redis import Redisredis = Redis.from_env()result = redis.script_exists("<sha1>")print(result)

ioredis

import Redis from "ioredis";const redis = new Redis(process.env.REDIS_URL!);const result = await redis.script("EXISTS", "<sha1>");console.log(result);

node-redis

import { createClient } from "redis";const client = await createClient({ url: process.env.REDIS_URL })  .on("error", console.error)  .connect();const result = await client.scriptExists("<sha1>");console.log(result);

redis-py

import osimport redisclient = redis.from_url(os.environ["REDIS_URL"])result = client.script_exists("<sha1>")print(result)

go-redis

package mainimport (    "context"    "fmt"    "os"    "github.com/redis/go-redis/v9")func main() {    opts, err := redis.ParseURL(os.Getenv("REDIS_URL"))    if err != nil {        panic(err)    }    client := redis.NewClient(opts)    result, err := client.ScriptExists(context.Background(), "<sha1>").Result()    if err != nil {        panic(err)    }    fmt.Println(result)}

jedis

import java.net.URI;import redis.clients.jedis.Jedis;try (Jedis jedis = new Jedis(new URI(System.getenv("REDIS_URL")))) {  Object result = jedis.scriptExists("<sha1>");  System.out.println(result);}

redis-rs

fn main() -> redis::RedisResult<()> {    let url = std::env::var("REDIS_URL").expect("REDIS_URL is not set");    let client = redis::Client::open(url)?;    let mut connection = client.get_connection()?;    let mut command = redis::cmd("SCRIPT");    command.arg("EXISTS");    command.arg("<sha1>");    let result: redis::Value = command.query(&mut connection)?;    println!("{result:?}");    Ok(())}