Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

COLUMN_NOT_FOUND at occasionally with trino|presto #9

Open
marun790 opened this issue Jan 20, 2022 · 6 comments
Open

COLUMN_NOT_FOUND at occasionally with trino|presto #9

marun790 opened this issue Jan 20, 2022 · 6 comments

Comments

@marun790
Copy link

Hi Team,
when executing a select query using appache superset + presto|trino getting column not found that too occasionally.
the same error is occurring in DBeaver also
but able to see the same column while executing aql > show bins.

Trino Error
trino error: {'message': "line 1:14: Column 'name' cannot be resolved", 'errorCode': 47, 'errorName': 'COLUMN_NOT_FOUND', 'errorType': 'USER_ERROR', 'errorLocation': {'lineNumber': 1, 'columnNumber': 14}, 'failureInfo': {'type': 'io.trino.spi.TrinoException', 'message': "line 1:14: Column 'name' cannot be resolved", 'suppressed': [], 'stack': ['io.trino.sql.analyzer.SemanticExceptions.semanticException(SemanticExceptions.java:48)', 'io.trino.sql.analyzer.SemanticExceptions.semanticException(SemanticExceptions.java:43)', 'io.trino.sql.analyzer.SemanticExceptions.missingAttributeException(SemanticExceptions.java:33)'

Please help us on this.

Thanks
Arun M

@reugn
Copy link
Member

reugn commented Jan 20, 2022

Hi @marun790. Do you have capital letters in the column/bin name?

@marun790
Copy link
Author

marun790 commented Jan 21, 2022

Hi @reugn thanks for the reply, yes we do have and we following camel case.
also we enabled 'aerospike.case-insensitive-identifiers' in aerospike trino connector.

@reugn
Copy link
Member

reugn commented Jan 21, 2022

Unfortunately, the data browser uses the old Trino (PrestoSQL) connector, which does not support capitalization. We will update here as soon as it is upgraded.

@marun790
Copy link
Author

Ohh!! thanks for the finding @reugn
but I am just wondering like we getting these issue irrespective of case sensitive, even we can see camel case bin ex:'bookName' in response and complete lower case bin ex:'name' is giving COLUMN_NOT_FOUND.
Is these also because of lower version of connector.
can you please help me to understand :)

@reugn
Copy link
Member

reugn commented Jan 21, 2022

The problem is that you can't query using the upper case in the bin (column) or set (table) name because that's not supported. Also, using the lowercase version of the name will not work due to Aerospike objects being case-sensitive. Yet the auto inferred column names will be displayed in lower case.

@marun790
Copy link
Author

ok @reugn , thanks for the explanation. we will wait for the upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants