TIME (time64[ns]) type unhandled

Abierto
  • ¿Algo no está bien?
#505 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
67/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
go
Área
backend-api-design, database

Línea de trabajo

Start by locating the Arrow row scanner's type switch, where the issue says time32 and time64 are unhandled and DATE and TIMESTAMP already have arms. Reproduce with SELECT TIME '09:15:00.123456' against a SQL warehouse and trace how the Arrow batch value reaches rows.Scan. Done when TIME scans as a time of day without a date or location, and an unsupported column does not prevent rows from being returned.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug engineer-bot

QueryContext + rows.Next fails for a TIME column. The server returns the value as an Arrow time64 (nanoseconds, including when the SQL type is TIME with microsecond precision). The Arrow row scanner has no arm for time32 or time64, so the whole result fails with:

databricks: arrow row scanner unhandled type time64[ns]

The value is present in the Arrow batch. The failure is the scanner's type switch.

Reproducer, against a SQL warehouse:

SELECT TIME '09:15:00.123456'

rows, err := db.QueryContext(ctx, "SELECT TIME '09:15:00.123456'")
// err == nil
var dest any
ok := rows.Next()
err = rows.Scan(&dest)
// databricks: arrow row scanner unhandled type time64[ns]

Expected: a TIME value scans as a time-of-day (wall clock, no date and no location), and one unsupported column does not have to fail the result before any row is returned. DATE and TIMESTAMP already have arms in that switch https://docs.databricks.com/aws/en/sql/language-manual/data-types/time-type.

Lenguaje dominante
Go
Estrellas
53
Forks
70
Merge medio
2 d 12 h
PR fusionados (30 d)
16

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de databricks/databricks-sql-go

Todos los issues de databricks/databricks-sql-go

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.