[
https://issues.apache.org/jira/browse/BEAM-4425?focusedWorklogId=106814&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-106814
]
ASF GitHub Bot logged work on BEAM-4425:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/May/18 20:30
Start Date: 29/May/18 20:30
Worklog Time Spent: 10m
Work Description: kennknowles opened a new pull request #5503:
[BEAM-4425] Force load JDBC drivers
URL: https://github.com/apache/beam/pull/5503
In some environments (known to be OSX) the JDBC drivers are not loaded by
the time they are used. This is a cherry-pick from #5490 to make it easy for
anyone to review just these commits.
------------------------
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [x] 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.
- [x] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
It will help us expedite review of your Pull Request if you tag someone
(e.g. `@username`) to look at it.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 106814)
Time Spent: 10m
Remaining Estimate: 0h
> JDBC driver load errors :jdbc:calcite and :jdbc:beam
> ----------------------------------------------------
>
> Key: BEAM-4425
> URL: https://issues.apache.org/jira/browse/BEAM-4425
> Project: Beam
> Issue Type: Bug
> Components: dsl-sql
> Reporter: Kenneth Knowles
> Assignee: Kenneth Knowles
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> These have different causes but the same fix - force load the JDBC driver
> before it is used or otherwise factor code so it is not possible to hit this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
