Forum Discussion
Creating a connector that uses a native component / ADBC
Hi SQLGuy,
I hope the information provided above assists you in resolving the issue. If you have any additional questions or concerns, please do not hesitate to contact us. We are here to support you and will be happy to help with any further assistance you may need.
Regards,
Harshitha.
Hi SQLGuy,
I hope the above details help you fix the issue. If you still have any questions or need more help, feel free to reach out. We are always here to support you.
Regards,
Harshitha.
- v-hjannapu1 year agoCommunity Support
Hi SQLGuy,
I wanted to follow up and see if you have had a chance to review the information that was shared. If you have any additional questions or need further clarification, please don’t hesitate to reach out. I am here to assist with any concerns you might have.
Regards,
Harshitha.- SQLGuy21 year agoNew Member
I have reviewed it, but I still do not see any ODBC/ADBC bridge actually existing. I have submitted an inquiry to the MS Fabric team to see what else I can find about the Connector creation process for new drivers.
- v-hjannapu1 year agoCommunity Support
Hi SQLGuy2,
Thank you for the update, and great that you have contacted the MS Fabric team directly. Since there isn't much documentation on using native ADBC drivers like libadbc_driver_flightsql.dll in custom connectors, reaching out to them is good move.
As you mentioned, there doesn’t appear to be an ADBC-to-ODBC bridge available yet, and Microsoft hasn’t provided much public information about native connector development. Hopefully, with more interest from users, they will consider offering official guidance or more details soon.
If you receive any updates from the Fabric team, please share them here, as it could be helpful for others exploring similar connector setups.
Best Regards,
Harshitha.