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.

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

evalEngine: Implement ELT and FIELD #15249

Merged
merged 9 commits into from
Apr 1, 2024
Merged

Conversation

beingnoble03
Copy link
Member

@beingnoble03 beingnoble03 commented Feb 15, 2024

Description

This PR adds implementation of ELT and FIELD functions in evalengine.

Related Issue(s)

Fixes part of #9647

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

Deployment Notes

Signed-off-by: Noble Mittal <noblemittal@outlook.com>
Copy link
Contributor

vitess-bot bot commented Feb 15, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Feb 15, 2024
@github-actions github-actions bot added this to the v20.0.0 milestone Feb 15, 2024
Comment on lines +220 to +233
switch arg.Type {
case sqltypes.VarBinary, sqltypes.Binary, sqltypes.Blob:
if tc.Collation != collations.CollationBinaryID {
c.asm.Convert_xce(offset, arg.Type, tc.Collation)
}
case sqltypes.VarChar, sqltypes.Char, sqltypes.Text:
fromCharset := colldata.Lookup(arg.Col.Collation).Charset()
toCharset := colldata.Lookup(tc.Collation).Charset()
if fromCharset != toCharset && !toCharset.IsSuperset(fromCharset) {
c.asm.Convert_xce(offset, arg.Type, tc.Collation)
}
default:
c.asm.Convert_xce(offset, arg.Type, tc.Collation)
}
Copy link
Member Author

Choose a reason for hiding this comment

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

Should we create a common function for this? We are now using the same logic in 3 functions.

Copy link

codecov bot commented Feb 15, 2024

Codecov Report

Attention: Patch coverage is 92.85714% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 65.81%. Comparing base (14473b9) to head (baf6e3c).
Report is 167 commits behind head on main.

Files Patch % Lines
go/vt/vtgate/evalengine/compiler_asm.go 88.42% 11 Missing ⚠️
go/vt/vtgate/evalengine/fn_string.go 94.00% 9 Missing ⚠️
go/vt/vtgate/evalengine/translate_builtin.go 88.88% 1 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15249      +/-   ##
==========================================
- Coverage   67.34%   65.81%   -1.54%     
==========================================
  Files        1560     1561       +1     
  Lines      192571   195157    +2586     
==========================================
- Hits       129695   128435    -1260     
- Misses      62876    66722    +3846     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

}
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

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

One thing to look at with stuff like this, is how much test runtime we're adding. It might be too much with all these permutations? How long does it take to run these tests?

Copy link
Member Author

@beingnoble03 beingnoble03 Feb 15, 2024

Choose a reason for hiding this comment

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

about 24 sec, in the comparison test. total 567338 number of tests.
CONCAT_WS takes 12 sec, total 229438 number of tests

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we should reduce this then, that's a lot of time for a single subtest here.

Copy link
Member Author

Choose a reason for hiding this comment

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

Removed the test for 4 inputs. Total test time reduced to 6 sec, total 56234 number of tests.

@dbussink
Copy link
Contributor

This PR adds implementation of ELT func in evalengine.

Given, FIELD is the complement function of this one, should we add both in one go?

Signed-off-by: Noble Mittal <noblemittal@outlook.com>
Signed-off-by: Noble Mittal <noblemittal@outlook.com>
Signed-off-by: Noble Mittal <noblemittal@outlook.com>
@beingnoble03 beingnoble03 changed the title evalEngine: Implement ELT evalEngine: Implement ELT and FIELD Feb 29, 2024
return 1
}

if containsOnlyInt64 {
Copy link
Contributor

Choose a reason for hiding this comment

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

The idea behind the compiler is that we can emit efficient code once types are known. It looks like these are compile time known values, so we should split this up into separate Fn_FIELD functions. Like maybe Fn_FIELD_i, Fn_FIELD_s etc.

Signed-off-by: Noble Mittal <noblemittal@outlook.com>
go/vt/vtgate/evalengine/fn_string.go Outdated Show resolved Hide resolved
go/vt/vtgate/evalengine/compiler_asm.go Outdated Show resolved Hide resolved
@dbussink dbussink added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Evalengine changes to the evaluation engine and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Mar 18, 2024
Signed-off-by: Noble Mittal <noblemittal@outlook.com>
beingnoble03 and others added 3 commits March 23, 2024 02:19
Signed-off-by: Noble Mittal <noblemittal@outlook.com>
If there's a literal NULL with only numerical types, we also have to
convert to DOUBLE instead of ignoring the NULL.

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
Copy link
Contributor

@dbussink dbussink left a comment

Choose a reason for hiding this comment

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

This is looking good now I think!

@dbussink dbussink requested a review from vmg March 29, 2024 15:26
@vmg vmg merged commit fabd746 into vitessio:main Apr 1, 2024
102 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: Evalengine changes to the evaluation engine Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants