Open a Support Ticket

[None123]

Anyone know how to submit a support ticket? I keep getting into a loop that takes me back to the community page, but I need to submit an urgent ticket. I'm told our company pays a ridiculous sum for this feature yet it is impossible to find.

Thanks very much in advance!!

[None123]

Agreed. The question is how do I open one with a representative of Databricks

[None123]

Thanks, Kaniz. Unfortunately that reroutes me to the community page. I can send you a screen recording if that helps. (It includes private information about my company because of the login interstitial, so I cannot post it here.)

[vickytscv]

Hi Team,

     We are working with Adobe tool for campaign metrics. which needs to pull data from AEP using explode option, when we pass query it is taking long time and performance is also very. Is there any better way to pull data from AEP, Please let let me know if there is best way to pull data from adobe tool.

#Adobe #query #ldatabricks

Thanks in advance. 

Vignesh Kumar

[vermyas]

Hello Databricks Support Team,

We are currently using:

• databricks-sql-connector==4.3.0
• thrift==0.22.0

Our organization's security scanning tool (Prisma) is flagging Thrift 0.22.0 and requires us to upgrade to a newer version (0.23.0 or later).

As part of our analysis, we upgraded Thrift to 0.23.0; however, the application was no longer able to establish a connection using the Databricks SQL Connector. Reverting to Thrift 0.22.0 restored connectivity.

We have also noticed that Apache Thrift 0.24.0 has been released. Since our security requirements mandate the use of a newer Thrift version, the current dependency constraint is creating a compliance challenge.

Could you please advise on the following:

1. Are there plans to update the Databricks SQL Connector to support Thrift 0.24.0?
2. Is there a newer Databricks SQL Connector version that already supports Thrift 0.24.0 (or later)?
3. Is there an estimated timeline for support of newer Thrift versions?
4. Do you recommend any workaround that would allow us to remain compliant with security requirements while maintaining Databricks SQL connectivity?

Any guidance or official recommendation would be greatly appreciated, as we need to determine the appropriate remediation path for our security findings.