Hi @marun790. I've added support for the aerospike.case-insensitive-identifiers configuration property and updated default Trino and the connector versions. Please pull the changes and let us know if that fixed the issue.

from trino-aerospike.docker.

hi @reugn , thanks for the update, we will check on this.

from trino-aerospike.docker.

Hi @reugn we have tried the fix but didn’t helped, can you please help us on this.

from trino-aerospike.docker.

@marun790, could you please provide the table structure and steps to reproduce?

from trino-aerospike.docker.

@reugn the table structure is 48 column with all are string data type, and 2 million records. and those all are created by java application with micronaut framework.
tried to recreate the same using insert script with 67 column but that is not helping, will try on the same and will let you know if I can recreate the scenario in any other way as-well.

from trino-aerospike.docker.

Hi, I am using Trino CLI for Aerospike and facing the same issue when trying to query a column in Aerospike DB. I have created a secondary index on AerospikeDB but the issue is still persisting.

ERROR:

2024-02-28T13:11:24.592+0530 INFO dispatcher-query-346 io.trino.event.QueryMonitor TIMELINE: Query 20240228_074124_00024_wtnbu :: FAILED (COLUMN_NOT_FOUND) :: elapsed 2ms :: planning 2ms :: waiting 0ms :: scheduling 0ms :: running 0ms :: finishing 0ms :: begin 2024-02-28T13:11:24.589+05:30 :: end 2024-02-28T13:11:24.591+05:30

SQL:

select isDeceased from customers where isDeceased is not null;

isDeceased is a varchar in this case, the set has huge amount of data (more than 5 Million).

from trino-aerospike.docker.

@NikhilPrasad0497, have you enabled the aerospike.case-insensitive-identifiers configuration property?

from trino-aerospike.docker.

Hi @reugn yes we have this option aerospike.case-insensitive-identifiers set

from trino-aerospike.docker.

Ensure the configuration value is set in the logs when the Trino server initializes. Additionally, run describe on your table to check if the column exists and is of the correct type.

from trino-aerospike.docker.

Sure, we have done this. The Column does not appear while running the describe table.

from trino-aerospike.docker.