Giter Site home page Giter Site logo

amazon-archives / sql-odbc Goto Github PK

View Code? Open in Web Editor NEW
9.0 9.0 10.0 13.46 MB

Open Distro for Elasticsearch ODBC Driver

Home Page: https://opendistro.github.io/

License: Apache License 2.0

C 44.69% C++ 50.18% Batchfile 0.09% Shell 0.19% CMake 3.15% HTML 0.75% Python 0.60% PowerShell 0.19% JavaScript 0.16%

sql-odbc's People

Contributors

abbashus avatar alolita avatar anirudha avatar hyandell avatar jordanw-bq avatar joshuali925 avatar lyndonbauto avatar rupal-bq avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

sql-odbc's Issues

Can't connect to server

I cannot connect to server.

Server version: Opendistro 1.7.0
ODBC client version: 0.2.0

Error: Failed to Establish Connection to DB

Windows: Windows Server 2012R2

mac-installer 1.7 failure

Are there any known problems with mac-installer v1.7.0.0?

My installation attempt on MacOS Catalina v10.15.4 fails, and I'm seeing the following in logs:
installd[1725]: PackageKit: Executing script "./postinstall" in /private/tmp/PKInstallSandbox.u8xo7K/Scripts/com.Amazon.ODFE SQL ODBC Driver.Driver.7qOYqn
installd[1725]: ./postinstall: dyld: Library not loaded: @rpath/libodfesqlodbc.dylib
installd[1725]: ./postinstall: Referenced from: /usr/local/lib/odfe-sql-odbc/bin/dsn_installer
installd[1725]: ./postinstall: Reason: image not found
installd[1725]: ./postinstall: /tmp/PKInstallSandbox.u8xo7K/Scripts/com.Amazon.ODFE SQL ODBC Driver.Driver.7qOYqn/postinstall: line 14: 27143 Abort trap: 6 ${FINAL_INSTALL_DIR}/bin/dsn_installer ${FINAL_INSTALL_DIR}/bin/ > /tmp/dsn_installer.log

...
Install Failed: Error Domain=PKInstallErrorDomain Code=112 "An error occurred while running scripts from the package “ODFE SQL ODBC Driver-0.2.0-Darwin.pkg”

Update documentation

Update documentation with references to github and also add THIRD-PARTY document.

Mac installer fixes

Found a couple of issues during final testing of installers

  • No uninstall step
  • Cannot link to driver dependencies due to rpath configuration

Driver performance improvements

Work on driver performance improvements around query execution flow.

I have identified some areas that can be optimized to do some initial performance improvements.

Create Simple Windows Installer

Create a simple Windows installer that simply installs the binary dependencies (registry setup and proper versioning not required yet)

Connection string option tweaking

We should align our connection string options with ODBC default names for out outward options. This will allow tableau to properly populate the dialog boxes.

Furthermore, we should add a default drivername. I am not sure if it is considered a bug in Tableau, but if you default an empty string, Tableau will connect with the driver properly, then spin infinitely in the driver manager until forcefully killed, execution SQL calls in a loop, attempting to find a DSN with an empty string name. Regardless of whether it is a Tableau issue, let's add a default drivername.

Connection sting abbreviation support

The current connection string options match the sql-jdbc driver.

ODBC Drivers very often use 'server' instead of 'host', 'UID' instead of 'user', and 'PWD' instead of 'password' in connection strings.

Adding support for this would be beneficial for users who are used to ODBC style connection strings. We can still leave our registry writing and registry files using 'host', 'user', and 'password'.

Setup GitHub actions to build driver for Mac and Windows

Get GitHub actions up to build driver for Mac and Windows.

Tests will not run initially. They will be setup so that they can just be uncommented and will run and make result artifacts in the future. We need the ability to deploy a server to send our queries to before we get our testing setup.

Add Tableau connector

  • UI elements needed to collect user input for creating a connection to a data source
  • dialect and customizations needed for the connection

Update catalog tests to not require specific set of tables

Currently, the SQLTables catalog integration tests expect a specific set of data tables loaded into the ODFE server in order to pass. (if there are any missing, or any unexpected tables, some tests fail)

This check should be changed so it checks for a set of required tables on the server, but not failing for extra tables existing.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.