Now you can generate POST REST calls for your scenarios where you can run a pre-configured scenario for a different query or a table or a profile by changing the details in the API payload.
When this API is executed, it will also return another API as output which can be used for monitoring execution progress of the scenario and the result.
Data retention policy for scenario/query chains/jobs.
You can configure the data retention policy for every query chain, scenario, and job. Data that doesn't fall under the given policy is purged from the DB automatically.
Date pattern check rule.
There is a new business rule added in the validation scenario where you can check a String column's conformity to a specific date format.
Manually delete the data of a session.
Now you have a provision in execution history in the designer page of a query chain, scenario, and job to delete the data of a session if it isn't already deleted.
Manually stop the execution of a session.
A new provision is given in execution history in the designer page of a query chain, scenario and job to stop a running session.
Perform profiling directly on a data source without having to ingest the data into the RightData DB.
Use this feature when you don't need a snapshot of the actual data and you're only interested in the data profiling stats.
Currently, only MSSQL, Impala, and Spark data sources are covered. We will be expanding to other data sources in the coming days.
Improvements in downloading the scenario exceptions data from the summary page.
Introducing an internal packeting process during data ingestion where packet data would be ingested at a rate of a maximum of 1 million records at a time.
Reduces the load on the RightData DB.
Data ingestion process will be faster when a single packet has some millions of records to ingest.