Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Fix] Handle edge case for effective_properties in databricks_sql_table #4153

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Fix] Handle edge case for effective_properties in databricks_sql_table #4153

wants to merge 1 commit into from

Commits on Oct 25, 2024

  1. [Fix] Handle edge case for effective_properties in `databricks_sql_… 

    …table`

It was reported in #4098 that some of the specified options, like, `multiLine`,
`recursiveFileLookup` and potentially more, aren't returned as `option.multiLine`, etc.,
but instead are expanded into full names, like, `spark.sql.dataSourceOptions.multiLine`.

This PR changes lookup logic a bit, and if we can't find `option.something`, then we're
looking for all options ending with `.something` (only if there are no `.` in the name).

Resolves #4098
    @alexott
    alexott committed Oct 25, 2024
    Configuration menu
    Copy the full SHA
    2e0bdfa View commit details
    Browse the repository at this point in the history