not really, just that if the app is not in the list of apps that is started, the config is pruned. so it needs to be a name of an app that is started, not a random atom that you pass in the use Snowflex macro.
cevado
0
pdgonzalez872
Hi! I’m afraid this won’t be too helpful, but let’s see:
I have looked extensively, but did not find any similar error
Yes, the errors are difficult to read/reason about (we had some connection errors that would not allow re-connecting, so eventually the machine would just die). We were only able to prove that it happened by attaching a connection listener to the connection and cross referencing the logs in the odbc driver. Once a connection died it would not come back up.
As far as your issue:
Unixodbc 2.3.12 (installed through Homebrew following the Snowflex readme).
I’d check the snowflake docs (not the library’s) to make sure you have the correct ODBC driver installed: ODBC Driver | Snowflake Documentation
This is the best hunch I have at the moment 
I say this because a lot has changed with the M1 and maybe that’s the issue? Maybe the version is not the right one? I’d check that first.
I’d open an issue on the Snowflex repo as well, as I bet the folks using it maybe have seen this issue before and know exactly how to handle it. The M1 has been around for a while now, I’m sure some folks that are using this have seen it before.
General thoughts on odbc
The ODBC route was difficult to use after a while. I’m not a fan of “here is a suggestion that changes all of your current workflow”. BUT, I was part of a project that dealt with this problem before and the result was moving away from odbc (last code commit in the erlang file was in 2010) and started using Snowflake’s api.
We have GitHub - HGInsights/avalanche: Avalanche is an Elixir Snowflake Connector built on top of the Snowflake SQL API v2. · GitHub and even telemetry for it: GitHub - HGInsights/opentelemetry_avalanche: Telemetry handler that creates OpenTelemetry spans from Avalanche (Snowflake) query events. · GitHub. Ever since the switch, it became a non-issue, we don’t talk about this anymore 
1
killerkiara
Hey @pdgonzalez872,
thanks a lot for your reply, I think it is helping more than you could imagine.
There is a lot of insights, especially your thoughts and considerations on ODBC.
As this is not a requirement, I will gladly follow your suggestion and try out a setup using Avalanche.
I had planned to open an issue on the Snowflex repo, it might still be useful for others who cannot choose the non-ODBC route.
Thanks a lot!
0