Releases: dekart-xyz/dekart
v0.14.0
Features
Rename queries and tabs
Now you can rename dataset tabs. Before they had automatic names assigned like Query 1, Query 2. Dataset layer in visualization panel will also pick up the new name.
OAuth Scopes Configuration for BigQuery
Added a mechanism to configure extra OAuth scopes for BigQuery. Extra OAuth scopes can be supplied via the DEKART_GCP_EXTRA_OAUTH_SCOPES environment variable as a comma-delimited list. (#122).
This allows querying a BigQuery table backed by a Google Sheet residing in Google Drive. In this case, it is necessary to set DEKART_GCP_EXTRA_OAUTH_SCOPES=https://www.googleapis.com/auth/drive.
This feature is the first contribution made by @hnicke 🚀
Fixes
- A security vulnerability was patched by fixing server security issues and resolving the problem with Golang dependencies (#129).
- Fixed the issue with Snowflake returning an empty result for better data fetching and representation (#123).
- Resolved an issue related to the concurrent map read causing backend to crash (#126).
- A bug that was causing issues with the popover positioning when clicking on geometry was fixed (#128).
Links
Upgrade from previous version
Documentation
Contribute 💜
Contributors
Assets 2
v0.13.0
Features
Export Dialogs
Added the ability for users to export their maps as HTML, images and data (#106). This can also be useful for printing maps or exporting to PDF. Thank you, @pooriaPoorsarvi, for the support and contribution!
AWS Athena Workgroup
Added the ability to specify an AWS Athena workgroup via an environment variable. This gives you the option to segment your query execution history for better governance, management, and isolation of queries (#102). Thank you, @seanlane, for the contribution.
Postgres Configuration
Added an option to configure Postgres using a connection string (#97). It allows specifying sslmode and use Dekart with wider range of managed Postgres services. Thank you, @christippett, for the contribution.
Fixes
- Fixed #93 causing rerunning query results in infinite load.
Links
Upgrade from previous version
Documentation
Contribute 💜
Contributors
Assets 2
v0.12.1
v0.12.0
Features
Snowflake connector ❄️
Snowflake connector is now available with Dekart!
Fetching 1M point from Snowflake ❄️ and rendering on the map
Fixes
- Fixing query cancellation
- #69 Retrieve results from BigQuery Scripts
- Fix missing download size
- Fix re-downloading queries when new query added
v0.11.0
Features
Support GeoJSON in file upload
Additionally to the existing CSV format, you can now also upload GeoJSON files to be used as datasets for your visualizations. As per the previous release, files are stored in the same storage as the SQL query cache. Both Amazon S3 and Google Cloud Storage are supported.
Share Reports
As a step towards better collaboration within an organization, we now introduce the feature allowing to make your own reports discoverable to other users. When sharing a report, you will allow other users of the same organization/website domain to see it in Shared Reports with only view access. Simply uncheck this setting and your report will not be visible anymore.
While this feature enhances discoverability, you can still see reports of other users from your organization if they share their link with you directly.
Resize SQL editor
You can now resize the query editor, allowing each user to define how big they want the map/editor for certain use cases. Simply drag the bar left and right to find your perfect configuration!
Copy geometry coordinates
With the upgrade to the latest version of kepler.gl, you can now leverage their Copy Geometry feature to extract the coordinates of vertices from a manually drawn polygon on the map. Simply paste in the query editor and there you go!
Control usage stats collection over configuration
As we all love data, Dekart appends some anonymized statistics to the referrer of external links related to the usage of the tool.
You have full control on if you allow this or not. Simply configure the variable DEKART_DISABLE_USAGE_STATS in your deployment environment.
See details in user experience configuration
Fixes
- #48 fix panic during error returning
- #28 fix the panic when no destination table exists
- Fix stale queries which cannot be cancelled
- Fix server crash/restart when cancelling query
Upgrade from previous version
v0.10.0
Features
#41 File upload
You can now upload enable file upload by setting DEKART_ALLOW_FILE_UPLOAD=1 in environment variables. Once enabled, you can upload .csv files to Dekart backend and add them to your report. Files are stored in the same storage as SQL query cache. Both Amazon S3 and Google Cloud Storage are supported.
#44 Introducing secure CORS headers
New environment configuration DEKART_CORS_ORIGIN= is strongly recommended to secure your deployment from CORS attacks. CORS attack allow 3rd party to delete, edit and run queries on behalf of the user visiting malicious web page.
Fixes
#37 Fix stale SQL query jobs
Upgrade from previous version
v0.9
Features
Support Authorization with Amazon OIDC headers #35
Now, you can configure user authorization in Dekart when using Amazon Load Balancer to host Dekart
You can configure Amazon Load Balancer to authenticate users via Amazon Cognito. Dekart parses x-amzn-oidc-data header, validates the JWT token and extracts claims containing user email. When you configure DEKART_REQUIRE_AMAZON_OIDC option, users will be authorized user to:
- list and edit only their own reports
- have read-only access to other users reports
Links:
v0.8.1
Features
Support AWS Athena as datasource.
Before Dekart was supporting only BigQuery. Now you can configure Dekart to query Athena or BigQuery with DEKART_DATASOURCE environment variable.
AWS Athena is a serverless query engine based on Presto. Athena/Presto includes support of Geospatial Functions and enables querying datasets like OpenStreetMap from AWS Public Dataset.
Make sure to configure Data Limits before using Athena.
See configuration details in https://dekart.xyz/docs/configuration/environment-variables/#main-configuration
Support AWS S3 as backend for storing queries and query results.
Now you can configure Dekart to use AWS S3 or Google Cloud Storage (GCS) to store queries and query results with DEKART_STORAGE environment variable. S3 storage will work with both: Athena and BigQuery datasources. You can deploy Dekart to AWS regardless if you query Athena or BigQuery.
Dekart still requires Postgres to store query meta information.
Acknowledgements
Thank you @tochka and @Tsovak for hacking together Athena and S3 support PoC.
Contributors
Assets 2
v0.7.2
v0.7.1
Fixes kepler.gl dependency to include performance improvements listed in v0.7.0 release notes
See v0.7.0 release notes for details