[BUG]: Use sqlglot.expression.SplitPart instead of local_expression.SplitPart in the custom dialects

[bishwajit-db]

Is there an existing issue for this?

• I have searched the existing issues

Category of Bug / Issue

ReconcileError

Current Behavior

Currently, local_expression.SplitPart is being used to parse and generate SQL for the custom dialects (Snow and Databricks, etc.). We should use the built-in sqlglot.expression.SplitPart instead, as it is available now. Using local_expression.SplitPart is creating some issues in reconciliation with user-provided transformation for the target. Also, in Databricks custom dialect, we don't need to override splitpart_sql method.

Expected Behavior

Use sqlglot.expression.SplitPart

Steps To Reproduce

No response

Relevant log output or Exception details

No response

Sample Query

No response

Operating System

macOS

Version

latest via Databricks CLI