Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

useKernel = true, can not get real error

Open
#445 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
sql, typescript
Domain
api, backend

Research direction

Reproduce the query through DBSQLClient.connect, openSession, and session.executeStatement with useKernel set to true and false. Compare the resulting errors; done means the kernel path exposes the underlying Databricks SQL cast error instead of only reporting "kernel backend: unknown error".

Written by the indexing model from the issue text.

Description

hi owner
we found

  const connectOptions: DatabricksConnectOptions = {
    authType: 'databricks-oauth',
    host: dbConfig.host,
    path: dbConfig.httpPath,
    oauthClientId: dbConfig.clientId,
    oauthClientSecret: dbConfig.clientSecret,
    useKernel: true
  }
  const _client = new DBSQLClient()
  await _client.connect(connectOptions)
  const session = await _client.openSession()
  const sql = `SELECT try_cast('' as ARRAY<STRING>)`
  const op = await session.executeStatement(sql)
  await op.finished()


will throw 
DriverError: kernel backend: unknown error
    at decodeNapiKernelError (...) {stack: 'Error: kernel backend: unknown error
    )', message: 'kernel backend: unknown error'}

if useKernel: false , will get real error


    [DATATYPE_MISMATCH.CAST_WITHOUT_SUGGESTION] Cannot resolve "" due to data type mismatch: cannot cast "STRING" to "ARRAY<STRING>". SQLSTATE: 42K09; line 1 pos 7

Dominant language
TypeScript
Stars
36
Forks
50
Avg merge
13h 46m
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from databricks/databricks-sql-nodejs

All issues in databricks/databricks-sql-nodejs

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.