frbvianna opened a new issue, #2544:
URL: https://github.com/apache/arrow-adbc/issues/2544

   ### What happened?
   
   When a table contains a column of VECTOR data type, the driver panics:
   `panic: runtime error: invalid memory address or nil pointer dereference`
   
   To my understanding, this is not a [supported 
type](https://arrow.apache.org/adbc/current/driver/snowflake.html#type-support) 
by this driver or Go clients in general.
   
   However, the driver could return a clearer error message.
    
   
   ### Stack Trace
   
   ```
   panic: runtime error: invalid memory address or nil pointer dereference
   [signal SIGSEGV: segmentation violation code=0x2 addr=0x20 pc=0x103f614c0]
   
   goroutine 74 [running]:
   
github.com/apache/arrow-adbc/go/adbc/driver/internal/driverbase.ToXdbcDataType({0x0,
 0x0})
           
/Users/<redacted>/go/pkg/mod/github.com/apache/arrow-adbc/go/[email protected]/driver/internal/driverbase/connection.go:703
 +0x20
   
github.com/apache/arrow-adbc/go/adbc/driver/snowflake.(*connectionImpl).GetObjects.func4()
           
/Users/<redacted>/go/pkg/mod/github.com/apache/arrow-adbc/go/[email protected]/driver/snowflake/connection.go:368
 +0x280
   created by 
github.com/apache/arrow-adbc/go/adbc/driver/snowflake.(*connectionImpl).GetObjects
 in goroutine 1
           
/Users/<redacted>/go/pkg/mod/github.com/apache/arrow-adbc/go/[email protected]/driver/snowflake/connection.go:354
 +0x164c
   exit status 2
   ```
   
   ### How can we reproduce the bug?
   
   - Create the table described in this doc: 
https://docs.snowflake.com/en/sql-reference/data-types-vector#loading-and-unloading-vector-data
   - Send a `GetObjects` at `ObjectDepthColumns` targetting that table
   
   ### Environment/Setup
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to