regadas / trino-js-client Goto Github PK

View Code? Open in Web Editor NEW

20.0 2.0 5.0 47.51 MB

A TypeScript client library for Trino

Home Page: https://regadas.dev/trino-js-client

License: MIT License

TypeScript 96.03% Emacs Lisp 0.38% JavaScript 3.58%

javascript trino trinodb typescript client library

trino-js-client's People

Contributors

Stargazers

Watchers

Forkers

tmdc-io elferherrera jordanfowler groupesperlos

trino-js-client's Issues

Handle headers properly

Request/Response headers are not being set properly.

push a new version

hi brother , I find the mian branch have new code to support https 。
could you push a new version npm ?
@regadas @elferherrera

Support other `AuthTypes` in addition to `BasicAuth`

Such as all of the authentication types listed here. Filing this as sort of a feature request 😄 but would be happy to possibly contribute here. The Auth interface looks clean enough to extend pretty easily.

Primary Introductory Example wouldn't compile or run

In the introductory documentation the following snippet is offered...

trino-js-client/README.md

Lines 42 to 44 in 97e599a

    
           const iter: Iterator<QueryResult> = await trino.query( 
        
             'select * from customer limit 100' 
        
           );

A followup snippet explains how you consume the result...

trino-js-client/README.md

Lines 50 to 52 in 97e599a

    
           for await (const queryResult of iter) { 
        
             console.log(queryResult.data); 
        
           }

I don't know how the example offered would ever compile and run, since the for await...of signature requires an AsyncIterator. See the following typescript playground.

QueryResult and QueryInfo is missing error/failure info

Improve authentication support

Basic
Kerberos

Add trino deployment for IT testing

Support multiple queries

Look into how would this look like.

Need to implement exponential backoff for polling nextUri

In the library exponential needs to implemented for checking the nextUri
Is there going be a performance impact if we directly check the nextUri without polling or doing exponential backoff?

Extra headers during initialization

Possibility to provide extra / additional request headers will help to solve some issues with connection to Trino inside cluster.
When some service setup inside one k8 cluster with Trino, you have a possibility to call it via http, but you have to pass X-Forwarded-Proto: "https" as axios request header.
So, would be great to extend ConnectionOptions interface (f.e. with extraHeaders property) and pass them to query method for headers.

Axios 1.2.0 update

When using axios 1.2.0 we are affected by axios/axios#5296

Change with failed IT tests cafe6d2

Is there a way to pass some properties to the Driver?

From DBeaver I use the JDBC driver for Trino and I needed to manually add three driver parameters:

SSL
SSLKeyStorePassword
SSLKeyStorePath

Is it possible to pass those parameters and their values to this tool?

Converting the Output to JSON

Hello! I just started using this package and has been the easiest to connect and faster responses among the others I have tried. I have a requirement to return the Trino results in JSON format. Is there a way to add the columns to each of the results in data?

Go from this
[ [ "data1" ] ]

To this
[ { 'column1': "data1" } ]

	const iter: Iterator<QueryResult> = await trino.query(
	'select * from customer limit 100'
	);

	for await (const queryResult of iter) {
	console.log(queryResult.data);
	}