Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update databricks-labs-lsql requirement from <0.11,>=0.5 to >=0.5,<0.…
…12 (#2666) Updates the requirements on [databricks-labs-lsql](https://github.com/databrickslabs/lsql) to permit the latest version. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/databrickslabs/lsql/releases">databricks-labs-lsql's releases</a>.</em></p> <blockquote> <h2>v0.11.0</h2> <ul> <li>Added filter spec implementation (<a href="https://github.com/databrickslabs/lsql/issues/276">#276</a>). In this commit, a new <code>FilterHandler</code> class has been introduced to handle filter files with the suffix <code>.filter.json</code>, which can parse filter specifications in the header of the filter file and validate the filter columns and types. The commit also adds support for three types of filters: <code>DATE_RANGE_PICKER</code>, <code>MULTI_SELECT</code>, and <code>DROPDOWN</code>, which can be linked with multiple visualization widgets. Additionally, a <code>FilterTile</code> class has been added to the <code>Tile</code> class, which represents a filter tile in the dashboard and includes methods to validate the tile, create widgets, and generate filter encodings and queries. The <code>DashboardMetadata</code> class has been updated to include a new method <code>get_datasets()</code> to retrieve the datasets for the dashboard. These changes enhance the functionality of the dashboard by adding support for filtering data using various filter types and linking them with multiple visualization widgets, improving the customization and interactivity of the dashboard, and making it more user-friendly and efficient.</li> <li>Bugfix: <code>MockBackend</code> wasn't mocking <code>savetable</code> properly when the mode is <code>append</code> (<a href="https://github.com/databrickslabs/lsql/issues/289">#289</a>). This release includes a bugfix and enhancements for the <code>MockBackend</code> component, which is used to mock the <code>SQLBackend</code>. The <code>.savetable()</code> method failed to function as expected in <code>append</code> mode, writing all rows to the same table instead of accumulating them. This bug has been addressed, ensuring that rows accumulate correctly in <code>append</code> mode. Additionally, a new test function, <code>test_mock_backend_save_table_overwrite()</code>, has been added to demonstrate the corrected behavior of <code>overwrite</code> mode, showing that it now replaces only the existing rows for the given table while preserving other tables' contents. The type signature for <code>.save_table()</code> has been updated, restricting the <code>mode</code> parameter to accept only two string literals: <code>"append"</code> and <code>"overwrite"</code>. The <code>MockBackend</code> behavior has been updated accordingly, and rows are now filtered to exclude any <code>None</code> or <code>NULL</code> values prior to saving. These improvements to the <code>MockBackend</code> functionality and test suite increase reliability when using the <code>MockBackend</code> as a testing backend for the system.</li> <li>Changed filter spec to use YML instead of JSON (<a href="https://github.com/databrickslabs/lsql/issues/290">#290</a>). In this release, the filter specification files have been converted from JSON to YAML format, providing a more human-readable format for the filter specifications. The schema for the filter file includes flags for column, columns, type, title, description, order, and id, with the type flag taking on values of DROPDOWN, MULTI_SELECT, or DATE_RANGE_PICKER. This change impacts the FilterHandler, is_filter method, and _from_dashboard_folder method, as well as relevant parts of the documentation. Additionally, the parsing methods have been updated to use yaml.safe_load instead of json.loads, and the is_filter method now checks for .filter.yml suffix. A new file, '00_0_date.filter.yml', has been added to the 'tests/integration/dashboards/filter_spec_basic' directory, containing a sample date filter definition. Furthermore, various tests have been added to validate filter specifications, such as checking for invalid type and both <code>column</code> and <code>columns</code> keys being present. These updates aim to enhance readability, maintainability, and ease of use for filter configuration.</li> <li>Increase testing of generic types storage (<a href="https://github.com/databrickslabs/lsql/issues/282">#282</a>). A new commit enhances the testing of generic types storage by expanding the test suite to include a list of structs, ensuring more comprehensive testing of the system. The <code>Foo</code> struct has been renamed to <code>Nested</code> for clarity, and two new structs, <code>NestedWithDict</code> and <code>Nesting</code>, have been added. The <code>Nesting</code> struct contains a <code>Nested</code> object, while <code>NestedWithDict</code> includes a string and an optional dictionary of strings. A new test case demonstrates appending complex types to a table by creating and saving a table with two rows, each containing a <code>Nesting</code> struct. The test then fetches the data and asserts the expected number of rows are returned, ensuring the proper functioning of the storage system with complex data types.</li> <li>Minor Changes to avoid redundancy in code and follow code patterns (<a href="https://github.com/databrickslabs/lsql/issues/279">#279</a>). In this release, we have made significant improvements to the <code>dashboards.py</code> file to make the code more concise, maintainable, and in line with the standard library's recommended usage. The <code>export_to_zipped_csv</code> method has undergone major changes, including the removal of the <code>BytesIO</code> module import and the use of <code>StringIO</code> for handling strings as files. The method no longer creates a separate ZIP file for the CSV files, instead using the provided <code>export_path</code>. Additionally, the method skips tiles that don't contain queries. We have also introduced a new method, <code>dataclass_transform</code>, which transforms a given dataclass into a new one with specific attributes and behavior. This method creates a new dataclass with a custom metaclass and adds a new method, <code>to_dict()</code>, which converts the instances of the new dataclass to dictionaries. These changes promote code reusability and reduce redundancy in the codebase, making it easier for software engineers to work with.</li> <li>New example with bar chart in dashboards-as-code (<a href="https://github.com/databrickslabs/lsql/issues/281">#281</a>). A new example of a dashboard featuring a bar chart has been added to the <code>dashboards-as-code</code> feature using the existing metadata overrides feature to support the new widget type, without bloating the TileMetadata structure. An integration test was added to demonstrate the creation of a bar chart, and the resulting dashboard can be seen in the attached screenshot. Additionally, a new SQL file has been added for the <code>Product Sales</code> dashboard, showcasing sales data for different product categories. This approach can potentially be used to support other widget types such as Bar, Pivot, Area, etc. The team is encouraged to provide feedback on this proposed solution.</li> </ul> <p>Contributors: <a href="https://github.com/JCZuurmond"><code>@JCZuurmond</code></a>, <a href="https://github.com/bishwajit-db"><code>@bishwajit-db</code></a>, <a href="https://github.com/ericvergnaud"><code>@ericvergnaud</code></a>, <a href="https://github.com/jgarciaf106"><code>@jgarciaf106</code></a>, <a href="https://github.com/asnare"><code>@asnare</code></a></p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/databrickslabs/lsql/blob/main/CHANGELOG.md">databricks-labs-lsql's changelog</a>.</em></p> <blockquote> <h2>0.11.0</h2> <ul> <li>Added filter spec implementation (<a href="https://github.com/databrickslabs/lsql/issues/276">#276</a>). In this commit, a new <code>FilterHandler</code> class has been introduced to handle filter files with the suffix <code>.filter.json</code>, which can parse filter specifications in the header of the filter file and validate the filter columns and types. The commit also adds support for three types of filters: <code>DATE_RANGE_PICKER</code>, <code>MULTI_SELECT</code>, and <code>DROPDOWN</code>, which can be linked with multiple visualization widgets. Additionally, a <code>FilterTile</code> class has been added to the <code>Tile</code> class, which represents a filter tile in the dashboard and includes methods to validate the tile, create widgets, and generate filter encodings and queries. The <code>DashboardMetadata</code> class has been updated to include a new method <code>get_datasets()</code> to retrieve the datasets for the dashboard. These changes enhance the functionality of the dashboard by adding support for filtering data using various filter types and linking them with multiple visualization widgets, improving the customization and interactivity of the dashboard, and making it more user-friendly and efficient.</li> <li>Bugfix: <code>MockBackend</code> wasn't mocking <code>savetable</code> properly when the mode is <code>append</code> (<a href="https://github.com/databrickslabs/lsql/issues/289">#289</a>). This release includes a bugfix and enhancements for the <code>MockBackend</code> component, which is used to mock the <code>SQLBackend</code>. The <code>.savetable()</code> method failed to function as expected in <code>append</code> mode, writing all rows to the same table instead of accumulating them. This bug has been addressed, ensuring that rows accumulate correctly in <code>append</code> mode. Additionally, a new test function, <code>test_mock_backend_save_table_overwrite()</code>, has been added to demonstrate the corrected behavior of <code>overwrite</code> mode, showing that it now replaces only the existing rows for the given table while preserving other tables' contents. The type signature for <code>.save_table()</code> has been updated, restricting the <code>mode</code> parameter to accept only two string literals: <code>"append"</code> and <code>"overwrite"</code>. The <code>MockBackend</code> behavior has been updated accordingly, and rows are now filtered to exclude any <code>None</code> or <code>NULL</code> values prior to saving. These improvements to the <code>MockBackend</code> functionality and test suite increase reliability when using the <code>MockBackend</code> as a testing backend for the system.</li> <li>Changed filter spec to use YML instead of JSON (<a href="https://github.com/databrickslabs/lsql/issues/290">#290</a>). In this release, the filter specification files have been converted from JSON to YAML format, providing a more human-readable format for the filter specifications. The schema for the filter file includes flags for column, columns, type, title, description, order, and id, with the type flag taking on values of DROPDOWN, MULTI_SELECT, or DATE_RANGE_PICKER. This change impacts the FilterHandler, is_filter method, and _from_dashboard_folder method, as well as relevant parts of the documentation. Additionally, the parsing methods have been updated to use yaml.safe_load instead of json.loads, and the is_filter method now checks for .filter.yml suffix. A new file, '00_0_date.filter.yml', has been added to the 'tests/integration/dashboards/filter_spec_basic' directory, containing a sample date filter definition. Furthermore, various tests have been added to validate filter specifications, such as checking for invalid type and both <code>column</code> and <code>columns</code> keys being present. These updates aim to enhance readability, maintainability, and ease of use for filter configuration.</li> <li>Increase testing of generic types storage (<a href="https://github.com/databrickslabs/lsql/issues/282">#282</a>). A new commit enhances the testing of generic types storage by expanding the test suite to include a list of structs, ensuring more comprehensive testing of the system. The <code>Foo</code> struct has been renamed to <code>Nested</code> for clarity, and two new structs, <code>NestedWithDict</code> and <code>Nesting</code>, have been added. The <code>Nesting</code> struct contains a <code>Nested</code> object, while <code>NestedWithDict</code> includes a string and an optional dictionary of strings. A new test case demonstrates appending complex types to a table by creating and saving a table with two rows, each containing a <code>Nesting</code> struct. The test then fetches the data and asserts the expected number of rows are returned, ensuring the proper functioning of the storage system with complex data types.</li> <li>Minor Changes to avoid redundancy in code and follow code patterns (<a href="https://github.com/databrickslabs/lsql/issues/279">#279</a>). In this release, we have made significant improvements to the <code>dashboards.py</code> file to make the code more concise, maintainable, and in line with the standard library's recommended usage. The <code>export_to_zipped_csv</code> method has undergone major changes, including the removal of the <code>BytesIO</code> module import and the use of <code>StringIO</code> for handling strings as files. The method no longer creates a separate ZIP file for the CSV files, instead using the provided <code>export_path</code>. Additionally, the method skips tiles that don't contain queries. We have also introduced a new method, <code>dataclass_transform</code>, which transforms a given dataclass into a new one with specific attributes and behavior. This method creates a new dataclass with a custom metaclass and adds a new method, <code>to_dict()</code>, which converts the instances of the new dataclass to dictionaries. These changes promote code reusability and reduce redundancy in the codebase, making it easier for software engineers to work with.</li> <li>New example with bar chart in dashboards-as-code (<a href="https://github.com/databrickslabs/lsql/issues/281">#281</a>). A new example of a dashboard featuring a bar chart has been added to the <code>dashboards-as-code</code> feature using the existing metadata overrides feature to support the new widget type, without bloating the TileMetadata structure. An integration test was added to demonstrate the creation of a bar chart, and the resulting dashboard can be seen in the attached screenshot. Additionally, a new SQL file has been added for the <code>Product Sales</code> dashboard, showcasing sales data for different product categories. This approach can potentially be used to support other widget types such as Bar, Pivot, Area, etc. The team is encouraged to provide feedback on this proposed solution.</li> </ul> <h2>0.10.0</h2> <ul> <li>Added Functionality to export any dashboards-as-code into CSV (<a href="https://github.com/databrickslabs/lsql/issues/269">#269</a>). The <code>DashboardMetadata</code> class now includes a new method, <code>export_to_zipped_csv</code>, which enables exporting any dashboard as CSV files in a ZIP archive. This method accepts <code>sql_backend</code> and <code>export_path</code> as parameters and exports dashboard queries to CSV files in the specified ZIP archive by iterating through tiles and fetching dashboard queries if the tile is a query. To ensure the proper functioning of this feature, unit tests and manual testing have been conducted. A new test, <code>test_dashboards_export_to_zipped_csv</code>, has been added to verify the correct export of dashboard data to a CSV file.</li> <li>Added support for generic types in <code>SqlBackend</code> (<a href="https://github.com/databrickslabs/lsql/issues/272">#272</a>). In this release, we've added support for using rich dataclasses, including those with optional and generic types, in the <code>SqlBackend</code> of the <code>StatementExecutionBackend</code> class. The new functionality is demonstrated in the <code>test_supports_complex_types</code> unit test, which creates a <code>Nested</code> dataclass containing various complex data types, such as nested dataclasses, <code>datetime</code> objects, <code>dict</code>, <code>list</code>, and optional fields. This enhancement is achieved by updating the <code>save_table</code> method to handle the conversion of complex dataclasses to SQL statements. To facilitate type inference, we've introduced a new <code>StructInference</code> class that converts Python dataclasses and built-in types to their corresponding SQL Data Definition Language (DDL) representations. This addition simplifies data definition and manipulation operations while maintaining type safety and compatibility with various SQL data types.</li> </ul> <h2>0.9.3</h2> <ul> <li>Added documentation for exclude flag (<a href="https://github.com/databrickslabs/lsql/issues/265">#265</a>). A new <code>exclude</code> flag has been added to the configuration file for our lab tool, allowing users to specify a path to exclude from formatting during lab execution. This release also includes corrections to grammatical errors in the descriptions of existing flags related to catalog and database settings, such as updating <code>seperated</code> to "separate". Additionally, the flag descriptions for <code>publish</code> and <code>open-browser</code> have been updated for clarification: <code>publish</code> now clearly controls whether the dashboard is published after creation, while <code>open-browser</code> controls whether the dashboard is opened in a web browser. These changes are aimed at improving user experience and ease of use for our lab tool.</li> <li>Fixed dataclass field type in _row_to_sql (<a href="https://github.com/databrickslabs/lsql/issues/266">#266</a>). In this release, we have addressed an issue related to <a href="https://github.com/databrickslabs/lsql/issues/257">#257</a> by fixing the dataclass field type in the <code>_row_to_sql</code> method of the <code>backends.py</code> file. Additionally, we have made updates to the <code>_schema_for</code> method to use a new <code>_field_type</code> class method. This change resolves a rare problem where the <code>field.type</code> is a string instead of a type and ensures compatibility with a pull request from an external repository (<a href="https://github.com/databrickslabs/ucx/pull/2526">databrickslabs/ucx#2526</a>). The new <code>_field_type</code> method attempts to load the type from <code>__builtins__</code> if it's a string and logs a warning if it fails. The <code>_row_to_sql</code> method now consistently uses the <code>_field_type</code> method to get the field type. This ensures that the library functions seamlessly and consistently, avoiding any potential issues in the future.</li> </ul> <h2>0.9.2</h2> <ul> <li>Make hatch a prerequisite (<a href="https://github.com/databrickslabs/lsql/issues/259">#259</a>). In this commit, Eric Vergnaud has introduced a change to make the installation of <code>hatch</code> version 1.9.4 a prerequisite for the project to avoid errors related to <code>pip</code> command recognition. The Makefile has been updated to handle the installation of hatch automatically, and the <code>hatch env create</code> command is now used instead of <code>pip install hatch==1.7.0</code>. This change ensures that the development environment is consistent and reliable by maintaining the correct version of hatch and automatically handling its installation. Additionally, the <code>.venv/bin/python</code> and <code>dev</code> targets have been updated accordingly to reflect these changes. This commit also formats all files using the <code>make dev fmt</code> command, which helps maintain consistent code formatting throughout the project.</li> <li>add support for exclusions in <code>fmt</code> command (<a href="https://github.com/databrickslabs/lsql/issues/263">#263</a>). In this release, we have added support for exclusions to the <code>fmt</code> command in the 'databricks/labs/lsql/cli.py' module. This feature allows users to specify a list of directories or files to exclude while formatting SQL files, which is particularly useful when verifying SQL notebooks in ucx. The <code>fmt</code> command now accepts a new optional parameter 'exclude', which accepts an iterable of strings that specify the relative paths to exclude. Any <code>sql_file</code> that is a descendant of any <code>exclusion</code> is skipped during formatting. The exclusions are implemented by converting the relative paths into <code>Path</code> objects. This change addresses the issue where single line comments are converted into inlined comments, causing misinterpretation. The added unit test is manually verified, and this pull request fixes issue <a href="https://github.com/databrickslabs/lsql/issues/261">#261</a>. This feature was authored and co-authored by Eric Vergnaud.</li> </ul> <h2>0.9.1</h2> <ul> <li>Fixed dataclass field types (<a href="https://github.com/databrickslabs/lsql/issues/257">#257</a>). This PR introduces a workaround to a Python bug affecting the <code>dataclasses.fields()</code> function, which sometimes returns field types as string type names instead of types. This can cause the ORM to malfunction. The workaround involves checking if the returned <code>f.type</code> is a string, and if so, converting it to a type by looking it up in the <code>__builtins__</code> dictionary. This change is global and affects the <code>_schema_for</code> function in the <code>backends.py</code> file, which is responsible for creating a schema for a given dataclass, taking into account any necessary type conversions. This change ensures consistent and accurate type handling in the face of the Python bug, improving the reliability of our ORM.</li> <li>Fixed missing EOL when formatting SQL files (<a href="https://github.com/databrickslabs/lsql/issues/260">#260</a>). In this release, we have addressed an issue related to the inconsistent addition of end-of-line (EOL) characters in formatted SQL files. The <code>QueryTile.format()</code> method has been updated to ensure that an EOL character is always added, except when the input query already ends with a newline. This change enhances the reliability of the SQL formatting functionality, making the output format more predictable and improving the overall user experience. The new implementation is demonstrated in the <code>test_query_format_preserves_eol()</code> test case, and existing test cases have been updated to check for the presence of EOL characters, further ensuring consistent and correct formatting.</li> <li>Fixed normalize case input in cli (<a href="https://github.com/databrickslabs/lsql/issues/258">#258</a>). In this release, we have updated the <code>fmt</code> command in the <code>cli.py</code> file to allow users to specify whether they want to normalize the case of SQL files when formatting. The <code>normalize_case</code> parameter now defaults to the string <code>"true"</code> and checks if it is in the <code>STRING_AFFIRMATIVES</code> list to determine whether to normalize the case of SQL files. Additionally, we have introduced a new optional <code>normalize_case</code> parameter in the <code>format</code> method of the <code>dashboards.py</code> file in the Databricks CLI, which normalizes the identifiers in the query to lower case when set to <code>True</code>. We have also added support for a new <code>normalize_case</code> parameter in the <code>QueryTile.format()</code> method, which prevents the automatic normalization of string input to uppercase when set to <code>False</code>. This change allows for more flexibility in handling string input and ensures that the input string is preserved as-is. These updates improve the functionality and usability of the open-source library, providing more control to users over formatting and handling of string input.</li> </ul> <h2>0.9.0</h2> <ul> <li>Added design for filter file (<a href="https://github.com/databrickslabs/lsql/issues/251">#251</a>). A new feature has been added to enable the creation of filters for multiple widgets in a dashboard using a <code>.filter.json</code> file. This file allows users to specify columns to be filtered, the filter type, title, description, order, and a unique ID for each filter. Both the <code>column</code> and <code>columns</code> flags are supported, with the former taking a single string and the latter taking a list of strings. The filter type can be set to a drop-down menu or another type as desired. The <code>.filter.json</code> file schema also supports optional <code>title</code> and <code>description</code> strings, as well as <code>order</code> and <code>ID</code> flags. An example of a <code>.filter.json</code> file is provided in the commit message. Additionally, the <code>dashboard.yml</code> file documentation has been updated to include information on how to use the new <code>.filter.json</code> file.</li> <li>adding normalize-case option to databricks labs lsql fmt cmd (<a href="https://github.com/databrickslabs/lsql/issues/254">#254</a>). In this open-source library release, the <code>databricks labs lsql</code> tool's <code>fmt</code> command now supports a new flag, <code>normalize-case</code>. This flag allows users to control the normalization of query text to lowercase, providing more flexibility when formatting SQL queries. By default, query text is still normalized to lowercase, but users can now prevent this behavior by setting the <code>normalize-case</code> flag to <code>False</code>. This change addresses an issue where some queries are case sensitive, such as those using map field keys in UCX dashboards. Additionally, a new parameter <code>normalize_case</code> has been added to the <code>format</code> method in the <code>dashboards.py</code> file, with updated method documentation. A new test function, <code>test_query_formats_no_normalize()</code>, has also been included to ensure consistent formatter behavior.</li> </ul> <h2>0.8.0</h2> <ul> <li>Removed deploy_dashboard method (<a href="https://github.com/databrickslabs/lsql/issues/240">#240</a>). In this release, the <code>deploy_dashboard</code> method has been removed from the <code>dashboards.py</code> file and the legacy deployment method has been deprecated. The <code>deploy_dashboard</code> method was previously used to deploy a dashboard to a workspace, but it has been replaced with the <code>create</code> method of the <code>lakeview</code> attribute of the WorkspaceClient object. Additionally, the <code>test_dashboards_creates_dashboard_via_legacy_method</code> method has been removed. A new test has been added to ensure that the <code>deploy_dashboard</code> method is no longer being used, utilizing the <code>deprecated_call</code> function from pytest to verify that calling the method raises a deprecation warning. This change simplifies the code and improves the overall design of the system, resolving issue <a href="https://github.com/databrickslabs/lsql/issues/232">#232</a>. The <code>_with_better_names</code> method and <code>create_dashboard</code> method remain unchanged.</li> <li>Skip test that fails due to insufficient permission to create schema (<a href="https://github.com/databrickslabs/lsql/issues/248">#248</a>). A new test function, <code>test_dashboards_creates_dashboard_with_replace_database</code>, has been added to the open-source library, but it is currently marked to be skipped due to missing permissions to create a schema. This function creates an instance of the <code>Dashboards</code> class with the <code>ws</code> parameter, creates a dashboard using the <code>make_dashboard</code> function, and performs various actions using the created dashboard, as well as functions such as <code>tmp_path</code> and <code>sql_backend</code>. This test function aims to ensure that the <code>Dashboards</code> class functions as expected when creating a dashboard with a replaced database. Once the necessary permissions for creating a schema are acquired, this test function can be enabled for further testing and validation.</li> <li>Updates to use the Databricks Python sdk 0.30.0 (<a href="https://github.com/databrickslabs/lsql/issues/247">#247</a>). In this release, we have updated the project to use Databricks Python SDK version 0.30.0. This update includes changes to the <code>execute</code> and <code>fetch_value</code> functions, which now use the new <code>StatementResponse</code> type instead of <code>ExecuteStatementResponse</code>. A conditional import statement has been added to maintain compatibility with both Databricks SDK versions 0.30.0 and below. The <code>execute</code> function now raises <code>TimeoutError</code> when the specified timeout is greater than 50 seconds and the statement execution hasn't finished. Additionally, the <code>fetch_value</code> function has been updated to handle the case when the <code>execute</code> function returns <code>None</code>. The unit test file <code>test_backends.py</code> has also been updated to reflect these changes, with multiple test functions now using the <code>StatementResponse</code> class instead of <code>ExecuteStatementResponse</code>. These changes improve the system's compatibility with the latest version of the Databricks SDK, ensuring that the core functionality of the SDK continues to work as expected.</li> </ul> <h2>0.7.5</h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/databrickslabs/lsql/commit/02ed2c828fb134cfcfe8cc6cc4cbfb2e09a1477a"><code>02ed2c8</code></a> Release v0.11.0 (<a href="https://github.com/databrickslabs/lsql/issues/291">#291</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/95a656320333b44a900dae56195747f2a398431e"><code>95a6563</code></a> Change filter spec to use YML instead of JSON (<a href="https://github.com/databrickslabs/lsql/issues/290">#290</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/621647fc8c13b955456c080818e9042ac5dc9396"><code>621647f</code></a> Bugfix: <code>MockBackend</code> wasn't mocking <code>savetable</code> properly when the mode is `a...</li> <li><a href="https://github.com/databrickslabs/lsql/commit/d88bb65793451480e3c18d63355416cee5f5f18b"><code>d88bb65</code></a> Add filter spec implementation (<a href="https://github.com/databrickslabs/lsql/issues/276">#276</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/7a4dc1954fdb897c14e1eb62e2c852d47ffdc68c"><code>7a4dc19</code></a> Format code (<a href="https://github.com/databrickslabs/lsql/issues/288">#288</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/5fdac8f0ac43379cc3319119f00a9cd476b98ddd"><code>5fdac8f</code></a> Skip integration test <code>test_appends_complex_types</code> (<a href="https://github.com/databrickslabs/lsql/issues/286">#286</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/2ad66b6202cecdd86a9ec2d250b2af248dcca6d5"><code>2ad66b6</code></a> Retry deploy schema on <code>InternalError</code> (<a href="https://github.com/databrickslabs/lsql/issues/283">#283</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/2216a12a1787f1a161c18d07bb3daab499b18a8c"><code>2216a12</code></a> Format code (<a href="https://github.com/databrickslabs/lsql/issues/285">#285</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/0c91dcd75cfc75c23bb0b47314436576fcbad0ee"><code>0c91dcd</code></a> Fix unit test for export to zipped csv (<a href="https://github.com/databrickslabs/lsql/issues/284">#284</a>)</li> <li><a href="https://github.com/databrickslabs/lsql/commit/b60e4ab4e4e83c070524838bcaa6ce4e4211fcc6"><code>b60e4ab</code></a> Minor Changes to avoid redundancy in code and follow code patterns (<a href="https://github.com/databrickslabs/lsql/issues/279">#279</a>)</li> <li>Additional commits viewable in <a href="https://github.com/databrickslabs/lsql/compare/v0.5.0...v0.11.0">compare view</a></li> </ul> </details> <br /> Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
- Loading branch information
1 parent
10cdebe
commit c4e9f25