Metatron Discovery 3.0.7 is released.

Created with Sketch.

Metatron Discovery 3.0.7 is released.


Notice: Undefined offset: 1 in /data/httpd/www/html/wp-includes/media.php on line 764

Notice: Undefined offset: 1 in /data/httpd/www/html/wp-includes/media.php on line 766

Notice: Undefined offset: 1 in /data/httpd/www/html/wp-includes/media.php on line 769

Notice: Undefined offset: 1 in /data/httpd/www/html/wp-includes/media.php on line 70
0
(0)

Metatron Discovery 3.0.7 is released. Now we are heading to 3.1.0 version, which is the first stable release of Metatron Discovery 3.0. Currently we have a QA period and will fix all the bugs found this time. We will release 3.1.0 version after all these QA steps are done and we supposed it will be completed on Dec. 7 and release date is scheduled on Dec. 10.

Main Improvements

Improve the Save data table action for useful download functions(#240)

Preview any data on the dashboard before downloading it. Downloading data in Excel format also supported now.

Add GEO type column when loading datasource(#728)

You can now add a Geo Type when creating a Datasource. Creating additional columns using the expression type is possible as well.

Full feature enhancements and bug fixes for 3.0.7 release are listed below.

Enhancement

#240 Improve the Save data table action for useful download functions.
#351 Rule list in snapshot detail should be short and concise
#410 CSV input enhancement (Apache Commons CSV)
#465 Relocating information in the query history
#538 Improve query editor window usability
#570 Supports txt file upload to dataset
#589 When a new subscription is made, the identity of the user in the denied request can be duplicated.
#620 Set limitation on chart view
#728 Add GEO type column when loading datasource
#738 Add custom properties in DataConnection
#747 Add clean menu in context menu
#753 display partition totalSize in partition validation result view.
#768 autocompletion of the rule edit for window function name
#811 Support multi-lined CSV snapshot

Bug Fix

#395 An error occurs when creating a data source with a query statement containing duplicate column names.
#398 No vertical scroll on detail view screen of Column Dictionary
#458 Empty header in Text Table
#495 Secondary indicators receive empty result
#501 Problem with the Today search option in the data source list
#578 The sorting feature of the results window in the workbench does not work sometimes
#627 number of data is not correct when previewing the data
#628 total number of data is invisible
#629 In the case of series by dimension, the tooltip representation is incorrect.
#664 Swap the upsteam dataset of a wrangled dataset
#665 When the workbench screen has been accessed for a long time, a “The current query is running.” message appears and the query is not executed.
#701 Dataset preview is not displayed
#710 Error in querying a specific column statistics in data source
#726 error when getting sample data from postgresql in schema browser.
#732 When api to find filter entry call fails, the dashboard stops load
#733 When api to search data for widget call fails, edit button in widget not worked.
#749 Show rule in colour red when rule is broken (dataflow panel)
#750 Show snapshot type in list and detail page
#755 empty message in ingestion details
#763 The results area is not visible in the workbench
#774 fix auto complete in command
#777 Deleting a data column to ingest does not work
#798 Fail to edit split rule
#818 Fix misaligned grid
#820 error occured when datasource search with date range.
#825 Error deleting column dictionary and code table
#828 Fix wrong Korean label
#845 Bug when 2 expressions are used in the window rule.
#848 Error notification when query cancelled.
#872 Suppress exceptions from broken rules
#885 invisible imported dataset after dataset swapping

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

As you found this post useful...

Share this post on your social media!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Leave a Reply

Your email address will not be published. Required fields are marked *