# Aerospike connect Trino - Error listing schemas for catalog

**URL:** <https://discuss.aerospike.com/t/aerospike-connect-trino-error-listing-schemas-for-catalog/11827>\
**Category:** Feature Discussion\
**Created:** [November 25, 2024, 3:10pm UTC](https://discuss.aerospike.com/t/aerospike-connect-trino-error-listing-schemas-for-catalog/11827 "2024-11-25T15:10:08Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![zeckem](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/zeckem/32/2502_2.png) [@zeckem](https://discuss.aerospike.com/u/zeckem)\
**Post date:** [November 25, 2024, 3:10pm UTC](https://discuss.aerospike.com/t/aerospike-connect-trino-error-listing-schemas-for-catalog/11827/1 "2024-11-25T15:10:09Z")

</div>

Followed the docs here [Configuration Properties for Aerospike Connect for Trino | Aerospike Documentation](https://aerospike.com/docs/connect/trino/configuration-properties) supplied clientpolicy params

```auto
      aerospike.clientpolicy.user: xxx
        aerospike.clientpolicy.password: xxx
        aerospike.clientpolicy.authMode: INTERNAL
        aerospike.hostlist: xxx.com:3000

```

However I am getting this error while querying with trino cli (using trino 464)

```auto
trino> show schemas from aerospike;

Query 20241108_230450_00022_w4vj2 failed: Error listing schemas for catalog aerospike: Aerospike feature key validation

```

The same credentials work for connection with other tools but only occur with trino. We are also using a full Aerospike enterprise version. What am I doing wrongly?

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [November 25, 2025, 3:10pm UTC](https://discuss.aerospike.com/t/aerospike-connect-trino-error-listing-schemas-for-catalog/11827/2 "2025-11-25T15:10:48Z")

</div>

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.