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

[BEAM-13609] Not all variable length types works properly for Oracle DB #16451

Conversation

vitaly-ivanov
Copy link
Contributor

@vitaly-ivanov vitaly-ivanov commented Jan 7, 2022

For example RAW(16) fails while comparing field length because the Oracle JDBC driver returns precision = 0 but columnDisplaySize = 16.

Looks like we can take into account columnDisplaySize when precision is zero or negative


Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

  • Choose reviewer(s) and mention them in a comment (R: @username).
  • Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
  • Update CHANGES.md with noteworthy changes.
  • If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

ValidatesRunner compliance status (on master branch)

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- Build Status Build Status Build Status Build Status ---
Java Build Status Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Build Status
Python --- Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status ---
XLang Build Status Build Status Build Status Build Status Build Status ---

Examples testing status on various runners

Lang ULR Dataflow Flink Samza Spark Twister2
Go --- --- --- --- --- --- ---
Java --- Build Status
Build Status
Build Status
--- --- --- --- ---
Python --- --- --- --- --- --- ---
XLang --- --- --- --- --- --- ---

Post-Commit SDK/Transform Integration Tests Status (on master branch)

Go Java Python
Build Status Build Status Build Status
Build Status
Build Status

Pre-Commit Tests Status (on master branch)

--- Java Python Go Website Whitespace Typescript
Non-portable Build Status
Build Status
Build Status
Build Status
Build Status
Build Status Build Status Build Status Build Status
Portable --- Build Status Build Status --- --- ---

See .test-infra/jenkins/README for trigger phrase, status and link of all Jenkins jobs.

GitHub Actions Tests Status (on master branch)

Build python source distribution and wheels
Python tests
Java tests

See CI.md for more information about GitHub Actions CI.

Take into account columnDisplaySize when precision is zero or negative
@vitaly-ivanov
Copy link
Contributor Author

R: @timrobertson100 @pabloem

@vitaly-ivanov
Copy link
Contributor Author

retest this please

@robertwb robertwb requested a review from pabloem January 14, 2022 23:01
@aaltay
Copy link
Member

aaltay commented Jan 27, 2022

@pabloem - Could you review this or find another reviewer?

@aaltay
Copy link
Member

aaltay commented Feb 5, 2022

@pabloem - friendly ping? Perhaps @kerrydc could help with finding another reviewer?

@pabloem
Copy link
Member

pabloem commented Feb 7, 2022

sorry about the delay - and thanks so much for the fix @vitaly-ivanov !

I don't see a lot of information regarding this issue, which is interesting. I think your current fix may work for RAW, but may not work for e.g. COUNT(*), which would return a BigInt (and what does that return as the columnDisplaySize?)

I see this: https://stackoverflow.com/questions/1410267/oracle-resultsetmetadata-getprecision-getscale

@pabloem
Copy link
Member

pabloem commented Feb 7, 2022

I suppose that your fix improves the functionality, even if it doesn't address all possible cases. I wonder if we could also throw a more informative error message that would directusers to use CAST

@pabloem
Copy link
Member

pabloem commented Feb 7, 2022

@vitaly-ivanov what are your thoughts on the above comments? Do you think there could be a way of handling also the COUNT(*) case?

@github-actions
Copy link
Contributor

github-actions bot commented Apr 9, 2022

This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the PR at any time and @mention a reviewer or discuss it on the dev@beam.apache.org list. Thank you for your contributions.

@github-actions github-actions bot added the stale label Apr 9, 2022
@github-actions
Copy link
Contributor

This pull request has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.

@github-actions github-actions bot closed this Apr 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants