Kindly fill up the following to try out our sandbox experience. We will get back to you at the earliest.
Learn about Google BigQuery's new schema selection and enhanced asset details, plus insights on Langchain for language models.
Updated on
.png)
For Google Big Query connections, you can now specify which schemas are to be scanned and included to have greater control of which assets will be included into decube's Data Quality and Data Catalog.
Now, when you add a new connection to Google Big Query, you will need to test your connection first. If the connection is successful, you now have the choice to either scan and include all schemas within the connection or only scan a specific selection on schemas.
We've also added a new selection here for us to handle new schemas being added to your data source. You can either let us:
First time setting up your connection? Check our our docs here for more information.
We've updated the Asset Details to now have improved icons for your data sources, asset types and attributes. Enrich your asset details by adding Data Owners and Business Owners onto your critical data assets. Owners are responsible to maintain the data assets and act as the contact point for the status of the data asset.
We'll be adding the ability for users to tag columns within the data asset (eg. adding PII tags), and also add documentation to each asset for a complete data cataloging experience for your organization. Check out our plan on our roadmap here.
Didn't like the name you used when you first signed up? Just go ahead and change it in our new tab Update Profile in the My Account page!
We've also enhanced the following:
You can also view our Docs Changelog to see the nitty-gritty details of the fixes we've done since our v1.0.
First step to AI Readiness
Table of Contents
Sneak peek from the data world.
_For%20light%20backgrounds.svg)
.svg){kind=small}
