BigQuery connection string helper functions

Open
#171 9 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
google-cloud, r
Domain
cloud, database

Research direction

Start with the createConnectionDetails entry point and review the linked R/bqAuthHelper.R utility for the proposed BigQuery connection-string behavior. Done means BigQuery connection details can produce a connection string through extraSettings when connectionString is absent.

Written by the indexing model from the issue text.

Description

enhancement

Creating BigQuery connection strings appears to be an important issue for users, ideally this should be completed using createConnectionDetails where possible, utilizing the extraSettings parameter.

@jdposada has created this custom package that includes a connection string building utility function.

Perhaps this could be included in the createConnectionDetails function by adding an additional call along these lines:

createConnectionDetails <- function(function(dbms,
                                    user = NULL,
                                    password = NULL,
                                    server = NULL,
                                    port = NULL,
                                    extraSettings = NULL,
                                    oracleDriver = "thin",
                                    connectionString = NULL,
                                    pathToDriver = Sys.getenv("DATABASECONNECTOR_JAR_FOLDER"), 
                                    ...) {) {

    ...

    if (is.null(connectionString) & dbms == "bigquery") {
         result$connectionString <- createBigQueryConnectionString(...)
    }
}

createBigQueryConnectionString <- function (**requiredAndOptionalBqParams**) {
    #return connection string
}
Dominant language
R
Stars
57
Forks
93
Avg merge
10d 12h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OHDSI/DatabaseConnector

All issues in OHDSI/DatabaseConnector

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.