Skip to content

Merges main branch into v1 #1420

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.

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

Merged
merged 47 commits into from
Apr 11, 2024
Merged

Merges main branch into v1 #1420

merged 47 commits into from
Apr 11, 2024

Conversation

rchowell
Copy link
Contributor

@rchowell rchowell commented Apr 10, 2024

Relevant Issues

N/A

Description

This PR merges the main branch into v1. We've made several changes to our typer and model. We will show some regression as operators such as COALESCE and NULLIF are not included in this PR.

Other Information

  • Updated Unreleased Section in CHANGELOG: [YES/NO]
    Yes

  • Any backward-incompatible changes? [YES/NO]
    N/A

  • Any new external dependencies? [YES/NO]
    N/A

  • Do your changes comply with the Contributing Guidelines
    and Code Style Guidelines? [YES/NO]
    Yes

License Information

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

rchowell and others added 30 commits December 20, 2023 11:13
Re-adds removed builder APIs and adds deprecation notice
Updates planner builder deprecation message
Adds a unit-test for excluding a column that is as a result of a new projection from a subquery.

More details:
```
PartiQL> SELECT tbl2.* EXCLUDE tbl2.dervidedColumn FROM (SELECT tbl1.*, tbl1.a.b + 2 AS dervidedColumn FROM <<{'a': {'b': 2}, 'foo': 'bar', 'foo2': 'bar2'}>> AS tbl1) AS tbl2;
==='
<<
  {
    'a': {
      'b': 2
    },
    'foo': 'bar',
    'foo2': 'bar2'
  }
>>
---
OK!
PartiQL> SELECT tbl2.* FROM (SELECT tbl1.*, tbl1.a.b + 2 AS dervidedColumn FROM <<{'a': {'b': 2}, 'foo': 'bar', 'foo2': 'bar2'}>> AS tbl1) AS tbl2;
==='
<<
  {
    'a': {
      'b': 2
    },
    'foo': 'bar',
    'foo2': 'bar2',
    'dervidedColumn': 4
  }
>>
---
OK!
```
@rchowell rchowell requested a review from johnedquinn April 10, 2024 21:52
)
}
),
// TestCase.ErrorTestCase(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you mean to comment out all of these? I've gone through the post-merge commits, and there are only two things that immediately stand out to me. These commented out tests are one. The other has to do with the undefined variable returning ANY instead of MISSING.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I did not, just need to isolate the failing tests. I will fix this ASAP

@@ -1,68 +0,0 @@
// package org.partiql.planner.internal
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this file be commented out?

@alancai98
Copy link
Member

Not too sure why but some of the GitHub actions steps aren't running.

Also looks like there are a few conflicts w/ the v1 branch.

@johnedquinn
Copy link
Member

Not too sure why but some of the GitHub actions steps aren't running.

Yeah, that is odd. I've been seeing that from my fork recently, and I'm not sure what it's from. It'd be nice to see the passing build and the change in conformance, if any.

@alancai98
Copy link
Member

Issue w/ the GH Actions gradle build/test step not running for v1 target branch should be fixed in #1423.

Copy link

Conformance comparison report-Cross Engine

Base (legacy) eval +/-
% Passing 92.51% 82.12% -10.38%
✅ Passing 5382 4778 -604
❌ Failing 436 1040 604
🔶 Ignored 0 0 0
Total Tests 5818 5818 0
Number passing in both: 4606

Number failing in both: 264

Number passing in legacy engine but fail in eval engine: 776

Number failing in legacy engine but pass in eval engine: 172
⁉️ CONFORMANCE REPORT REGRESSION DETECTED ⁉️
The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.
172 test(s) were failing in legacy but now pass in eval. Before merging, confirm they are intended to pass.
The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.

Conformance comparison report-Cross Commit-LEGACY

Base (5f16e67) 4ff50ed +/-
% Passing 92.52% 92.51% -0.02%
✅ Passing 5383 5382 -1
❌ Failing 435 436 1
🔶 Ignored 0 0 0
Total Tests 5818 5818 0
Number passing in both: 5382

Number failing in both: 435

Number passing in Base (5f16e67) but now fail: 1

Number failing in Base (5f16e67) but now pass: 0
⁉️ CONFORMANCE REPORT REGRESSION DETECTED ⁉️. The following test(s) were previously passing but now fail:

Click here to see
  • MYSQL_SELECT_29, compileOption: LEGACY

Conformance comparison report-Cross Commit-EVAL

Base (5f16e67) 4ff50ed +/-
% Passing 82.43% 82.12% -0.31%
✅ Passing 4796 4778 -18
❌ Failing 1022 1040 18
🔶 Ignored 0 0 0
Total Tests 5818 5818 0
Number passing in both: 4764

Number failing in both: 1008

Number passing in Base (5f16e67) but now fail: 32

Number failing in Base (5f16e67) but now pass: 14
⁉️ CONFORMANCE REPORT REGRESSION DETECTED ⁉️
The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.
14 test(s) were previously failing but now pass. Before merging, confirm they are intended to pass
The complete list can be found in GitHub CI summary, either from Step Summary or in the Artifact.

Copy link
Member

@alancai98 alancai98 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice work getting the branches merged!

@rchowell rchowell merged commit 04e33a8 into v1 Apr 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants