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

   ### What happened?
   
   Find additional issue regarding to the snowflake getSchemaTable, it throw 
KeyNotFoundException  exception when calling ConvertArrowSchema.  You could 
reproduce this error by executing the query “SELECT * FROM 
PUBLIC.TEST_ALLTYPE_EMPTY” and `reader.GetSchemaTable()`.
   
   I also did some investigation. The exception is throwed from this line: 
[https://github.com/apache/arrow-adbc/blob/fa8498f39fa69e01cdf2c5557e15cd4e6dc0fac2/csharp/src/Client/SchemaConverter.cs#L69](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Farrow-adbc%2Fblob%2Ffa8498f39fa69e01cdf2c5557e15cd4e6dc0fac2%2Fcsharp%2Fsrc%2FClient%2FSchemaConverter.cs%23L69&data=05%7C02%7CDavid.Coe%40microsoft.com%7Ce3f39cabdc594b0a7a2d08dc341ab63e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638442536601022025%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=8QlJMJEnUnECCiH5ov2kmzP%2FRZ4Mwu2%2B0LbJMES2Seg%3D&reserved=0).
 
   When the type is float, actually the metadata doesn’t contain precision and 
scale property, leading to the exception.  
   
   Error call stack:
      at System.ThrowHelper.ThrowKeyNotFoundException()
      at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
      at Apache.Arrow.Adbc.Client.SchemaConverter.ConvertArrowSchema(Schema 
schema, AdbcStatement adbcStatement, DecimalBehavior decimalBehavior) in 
Apache.Arrow.Adbc.Client\SchemaConverter.cs:line 41
      at Microsoft.Connectors.Snowflake.SnowflakeV2DataReader.GetSchemaTable() 
in 
D:\Repos\HybridDataIS\Source\SideBySideConnectors\SnowflakeV2\1.0.0.0\Source\SnowflakeV2DataReader.cs:line
 152
   
   ### How can we reproduce the bug?
   
   _No response_
   
   ### 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