Sync repos for the release 170.3.0 #105
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds the ability to parse the CTAS statement which has the "Create Table TblName AS Select" format. So far we support "Create Table tableName With(Distribution) AS Select...) syntax only. This change fixes the syntax error at Select and allows the DW users to run the sql queries with the syntax. ---- #### AI description (iteration 1) #### PR Classification New feature: Adding support for CTAS (Create Table As Select) statements in the 160Parser. #### PR Summary This pull request introduces support for parsing CTAS statements in the TSql160Parser and includes corresponding unit tests. - Added `CreateCTASParser160Test` method in `Test/SqlDom/TSqlParserTest.cs` to validate CTAS statement parsing. - Updated `TSql160.g` to handle `As` keyword for CTAS statements. - Minor import addition in `Test/SqlDom/PhaseOneParserTest.cs`.
Adds release notes to 191.9142.1, adds the CTAS support to 160 Parser and SDK update ---- #### AI description (iteration 1) #### PR Classification Documentation #### PR Summary This pull request adds release notes for version 161.9142.1. - `release-notes/161.91/161.9142.1.md`: Introduces release notes detailing target platform support, updated dependencies, new features, fixed issues, and known issues.
Added tests for below vector functions: 1. VECTOR_DISTANCE 2. VECTOR_NORM 3. VECTOR_NORMALIZE
Updated vector function test script to include VECTORPROPERTY Metadata function
…Official Branches # Introducing Policy-as-Code, powered by 1ES’ Policy Aware Engineering System (PAES)! With [Policy-as-Code](https://aka.ms/1esPaaC), repository owners can configure Azure DevOps (ADO) branch policies directly in the source code, eliminating the need for manual per-branch configuration. Policy-as-Code is the easiest way to manage branch policies efficiently! This Pull Request (PR) contains policy configuration settings that will be applied to the entire repository. Learn more about this approver count policy [here](https://aka.ms/1esPaaCAC). --- ### Actions Required - **What is in this PR and why should I complete it?** - This PR contains a suggested initialization of peer review policy settings specific to your repository. - By adopting Policy-as-Code, you ensure that branch policies are version-controlled and consistently applied across your repository. This practice enhances collaboration, compliance, and reduces manual configuration efforts. - [OneBranch is rolling out pipeline-time validation on all its official pipelines](https://aka.ms/obprv). - **What do I need to do?** - Review the targeted leaf branches in the .yml file created for you. You may remove any branches where collaboration is not expected. [Most leaf branches shouldn't be using official pipelines](https://aka.ms/OBPRValidation). ### Best Practices on Policy-as-Code - **Is branch policy required? Do I need to complete this PR?** - Branch policies are required on default branches (like `main`, `master`, `default`, `release*`), but these are configured at the service level through a different mechanism ([learn more](https://aka.ms/1esPaaCCY22)). The policies in this PR are specific to your repository. - **What if we are already using branch policies? How do conflicts work?** - Policies can still be customized using the ADO UI. **Your existing branch policies will remain unchanged**. In case of conflicts, the **most restrictive** policy settings will take precedence, ensuring compliance is maintained. - **Who created this PR?** - This PR was generated by OneBranch to facilitate the adoption of Policy-as-Code. The Policy-as-Code tooling is a product of the 1ES team. - **Who do I contact for additional support?** - For more information, visit the [PAES Wiki](https://aka.ms/1esPaaC). To learn more about OneBranch compliance enforcement efforts, click [here](https://aka.ms/obprv). If you have questions or need assistance related to PAES and Policy-as-Code, please email [PolicyServiceHelp@microsoft.com](mailto:PolicyServiceHelp@microsoft.com). --- By reviewing and completing this PR, you'll be taking a significant step toward streamlined policy management and improved compliance within your development workflow. Thank you for your attention to this important initiative!
New feature This pull request adds support for the vector type in ScriptDOM and includes tests to verify the TSQL script for creating tables with vector column types. - Added `TSql170Parser.cs` to implement the T-SQL 17.0 parser. - Added `Sql170ScriptGeneratorVisitor.cs` to handle script generation for T-SQL 17.0. - Added `TSql170ParserBaseInternal.cs` to provide base internal parsing logic for T-SQL 17.0. - Added `Sql170ScriptGenerator.cs` to create a script generator for T-SQL 17.0. Related work items: #3355520
ssreerama
requested review from
dzsquared,
zijchen,
chlafreniere and
llali
as code owners
zijchen
approved these changes
Dec 11, 2024
| @@ -0,0 +1,19 @@ | |||
| name: approver_count | |||
There was a problem hiding this comment.
I don't think we need this file in public repo
There was a problem hiding this comment.
Done! I removed all other onebranch template file changes, unnoticed this one, thanks for noticing it.
llali
requested changes
Dec 11, 2024
| @@ -0,0 +1,19 @@ | |||
| name: approver_count | |||
llali
approved these changes
Dec 12, 2024
llali
approved these changes
Dec 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.