LDWH 2.0.49 released: New JSON functions, job syncing, AdWords update
In 2.0.49 we added additional functions to generate JSON documents. The function JSONOBJECT can transform rows to JSON documents using column names as keys. The statement
SELECT JSONOBJECT(SalesOrderID, ProductID) FROM adventure.salesorderdetail
will transform each row of the queried table into a single JSON document, e.g {"SalesOrderID":5001.00,"ProductID":1218}. If you want to create a single JSON document with an array that includes all rows, you can wrap statement in a JSONARRAY_AGG call which will produce:
[{"SalesOrderID":5001.00,"ProductID":1218},{"SalesOrderID":5002.00,"ProductID":527}, ...]
You can even have multiple arrays in one JSON document in case you want to include different sets of data:
SELECT JSONOBJECT(
JSONARRAY_AGG(JSONOBJECT("SalesOrderID", "ProductID")) AS products,
JSONARRAY_AGG(JSONOBJECT("ProductID", "UnitPrice")) AS product_prices
)
This will generate a JSON document in the form of {"products": [...], "product_prices": [...]}.
Additionally, the synchronization tool for staging environments that we introduced recently now can also sync jobs and schedules, in addition to schemas, views and procedures.
The AdWords connector was updated to the latest API version v201806. If you are using AdWords, we will contact you in due time before your current API version is phased out to schedule an update.
Studio
- DVCORE-5037: DataVirtuality Studio: "Edit procedure" right-click menu item is disabled for failed procedure
Connectors
- DVCORE-5678 (Improvement): AdWords: migrate to v201806 AdWords API version
- DVCORE-5334: Disable concurrent requests per connection for Netezza
- DVCORE-5496: Joining a table or view from other source to a LEFT JOIN of two MySQL tables from the same data source results in error if streaming is enabled
Backend
- DVCORE-5532 (Improvement): Provide language objects to produce a JSON document
- DVCORE-5429 Improvement DataVirtuality Synchronization Tool: add syncing of jobs
- DVCORE-5702: DataVirtuality Exporter: "scheduleName" value is not quoted for CHAINED schedules in the export script
- DVCORE-5697: Duplicate schedule names are created
- DVCORE-5677: JSONTOXML fails on parsing too long numbers
- DVCORE-5651: DataVirtuality Exporter: exporting of job chained to another job freezes the exporter
- DVCORE-5588: UTILS.tryCast procedure does not allow null as value of originalValue parameter
- DVCORE-5565: Building the query plan takes too much time even if creation of recommended optimizations and indexes is disabled
- DVCORE-5187: Populate job description for non-SQL jobs in SYSLOG.JobLogs table
Please sign in to leave a comment.
Comments
0 comments