# OpenMetadata 0.13.2 Release Feb 15, 2023 ![](data:image/svg+xml,%3csvg%20xmlns=%27http://www.w3.org/2000/svg%27%20version=%271.1%27%20width=%2748%27%20height=%2748%27/%3e)![](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1699594258729/81993512-5eef-4eb8-a0c3-28c8fe0f2c4b.png) Sriharsha Chintalapani ![OpenMetadata 0.13.2 Release](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7) ![OpenMetadata 0.13.2 Release](https://cdn.hashnode.com/res/hashnode/image/upload/v1699598009888/6015d829-a0ca-4992-a885-6e1bc0115ca5.png) ## Improved SQL Lineage, Glossary Bulk Upload, Unified Tag Category API, Mutually Exclusive Tags, Chrome Extension, and lots more. We are glad to announce OpenMetadata’s **Release — 0.13.2**, which showcases some exciting features and improvements like Glossary bulk upload, improved SQL lineage, mutually exclusive tags, and a beta release of the **OpenMetadata Chrome extension**. The OpenMetadata community recently hosted a [**Mini-Webinar on Custom Connectors**](https://www.youtube.com/watch?v=fDUj30Ub9VE&t=9s), which discussed the core aspects of OpenMetadata, the ingestion process, and building your own **custom connectors**. Most organizations have their own in-house systems and other third-party services crucial to their business. OpenMetadata supports 60+ connectors, and by building a custom connector, you can have a holistic view of everything that happens in your Data Platform. We plan to add additional features to the [SaaS](https://www.getcollate.io/) version in future releases, so stay tuned for more updates 🚀. [![](https://cdn.hashnode.com/res/hashnode/image/upload/v1699598000800/ed920bba-e46b-4084-b802-71b73048d451.png)](https://www.getcollate.io/?pk_campaign=14_day_trial&pk_source=medium&pk_medium=small_rectangle) ## Community Update Thanks to OpenMetadata’s amazing community. We’ve been receiving productive feedback and active code contributions over the past one and a half years. And, we deeply appreciate your support and feedback. * Crossed 1800+ GitHub stars * The Slack community reached 2200+ members * 141 Open source GitHub developers * 312 Commits were merged into the 0.13.2 release ## OpenMetadata 0.13.2 Release Highlights ### Glossary Import and Export ![](https://cdn-images-1.medium.com/max/1024/1*9cBtzHcH-URSL8hVdcwzRg.gif) Glossary import and export When the Glossary was introduced in the 0.9 release, we supported a manual approach to add the glossary terms one at a time. This can become time-consuming for organizations already maintaining a business glossary in a spreadsheet or similar tools. Based on community feedback, we’ve introduced the functionality to **bulk upload glossary terms**. Users can save time and effort by uploading a CSV with thousands of terms in one go. The import utility will validate the file and show you a **preview** of the elements that will be imported to OpenMetadata. Just as you can import the glossary terms, you can **export the glossary data** as a CSV file. We take your feedback really seriously, and we are always excited to see community requests come to life! ### Improved SQL Lineage Open source thrives when communities grow together. We have been heavy users of [sqllineage](https://github.com/reata/sqllineage) for our query parsing processes, and it’s been a great tool. Still, the growing number of connectors and community needs required us to improve our existing parsing capabilities. We have worked together with [Reata](https://github.com/reata), the developer behind _sqllineage_, to migrate the library’s core to [sqlfluff](https://www.sqlfluff.com/). We’d like to take this opportunity to thank both communities for merging our contributions and helping bring our lineage parsing to the next level. If you are interested in learning more about how we handle Data Lineage in OpenMetadata, you can look at our [webinar](https://www.youtube.com/watch?v=jEbN1tt89H0&t=1s&ab_channel=OpenMetadata)! ### New Glossary UI ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1699598003510/c9a05d77-eea9-4bd8-8f64-29bc2a770fc5.png) Previously, the Glossary and the Glossary terms were displayed together in a tree UI. Now, we’ve separated the Glossary and Glossary Terms within the UI, such that the Glossaries are displayed in the left navigation pane, while the glossary details are displayed on the right. The list of terms has been sorted alphabetically for better navigation. The improved UI changes will help you easily access the details with tags and descriptions in the cards. ### From Tag Category to Classification We have renamed **Tag Categories** to **Classification** as a more widely used term for expressing groups of tags. The team also took this chance to unify the Tags API to conform to the other APIs we have been building. This change will make it easier for developers familiar with the existing APIs, and it simplified different internal flows. You can find more information about the exact modifications [here](https://github.com/open-metadata/OpenMetadata/issues/9259). ### Mutually Exclusive Tags from the UI There are situations where mixing multiple tags from the same classification does not make sense. Imagine an asset being tagged both with PII Sensitive and PII Non-Sensitive! When creating a Classification or a Glossary term, their elements can be **mutually exclusive**. If this configuration is enabled, you won’t be able to assign multiple tags from the same category or glossary to the same data asset. ### Chrome Extension ![](https://cdn-images-1.medium.com/max/1024/1*XBNCJuh-SXV1WtkVLKd0QQ.gif) OpenMetadata Chrome Extension We are elated to announce the launch of the BETA version of the [OpenMetadata Chrome extension](https://chrome.google.com/webstore/detail/openmetadata-chrome-exten/pakbbdhbbiclnceabdmnghamabjloofc?hl=en&authuser=0). Feel free to explore it and share your feedback. We are focused on meeting the needs of the Data Community, by simplifying processes and making all the metadata ubiquitously accessible by providing the necessary context in all your tools. ### Connectors * **Databricks Pipeline Connector** has been added as a community contribution! * Some important fixes have been made for the **AWS QuickSight** connector. * Improvements have been made to **DB2** constraints and profiler. * The **Oracle** connector now ships with the Thick mode enabled. * Added support for **Postgres** Foreign Tables * Connectors like Redshift or Snowflake are way **faster** now, as we get the descriptions in batches. * Added support for **Data Lake profiler** row-based sampling. ### Entity Names The team introduced an enforcement of the Entity Names’ format using regex patterns. The intention is to better manage and harmonize Entity Names values and to allow users to form better expectations around them. You can find more information about this change in the [docs](https://docs.open-metadata.org/deployment/upgrade). ## Planned for Next Release Our next release will be the long-awaited 1.0 Release ✨ The team has already started developing amazing new features, such as: * **Storage Service revamp** to better represent your Datalakes (based on your [feedback](https://github.com/open-metadata/OpenMetadata/discussions/8124)) with awesome community members! * NoSQL stores API definitions to prepare the ingestion for sources like Elasticsearch, * Automatic PII tagging during the profiler workflow, * Continuous improvement for the brand-new sqllineage package And more! Stay tuned for any news, and let us know which features you’d like to see next! ## Thanks to our Contributors It’s been great to associate with the open-source community members for the last one and a half years. We’ve been receiving encouraging feedback, and great code contributions; all this has been a huge motivation to keep scaling new heights. Thanks to [Aashish1221](https://github.com/Aashish1221), [Alina Valea Forter](https://github.com/Alina-Valea-Forter), [Bigdata-spec](https://github.com/bigdata-spec), [Frederico Cotrim](https://github.com/fredericocotrim), [geoHeil](https://github.com/geoHeil), [Gnomolio](https://github.com/gnomolio), [Itai Sevitt](https://github.com/itaise), [Laila Patel](https://github.com/lailapatel), [Martin Trillhaas](https://github.com/trillhaa), [Nithin Kumara N T](https://github.com/NithinKumaraNT), [Paulo Ventura](https://github.com/pauloventurab), [Sérgio Passos](https://github.com/sergiopassoscb) for raising GitHub issues that made it to the 0.13.2 release. Please contact us on [Slack](https://openmetadata.slack.com/) if you have questions about [code](https://github.com/open-metadata/OpenMetadata), [installation](https://docs.open-metadata.org/install/run-openmetadata), and [docs](https://docs.open-metadata.org/v/main/). For feature requests, you can file a [GitHub issue](https://github.com/open-metadata/OpenMetadata/issues) or reach out to us on [Slack](https://openmetadata.slack.com/). Interested in contributing code? Here are some [good first issues](https://github.com/open-metadata/OpenMetadata/issues?q=is%3Aopen+is%3Aissue+label%3Agood-first-issue) to get you going. Please give us a **GitHub star** if you like what we are doing. That’ll greatly help OpenMetadata in reaching a wider audience. [![](https://cdn.hashnode.com/res/hashnode/image/upload/v1699598007195/fec3540a-7bd6-49bd-8bc2-85a3340781ee.png)](https://www.getcollate.io/?pk_campaign=14_day_trial&pk_source=medium&pk_medium=large_rectangle) ![](https://cdn.hashnode.com/res/hashnode/image/upload/v1699598008630/4d1af5c8-4b2d-4ede-bde8-6fbd7d98036f.gif) * * * [OpenMetadata 0.13.2 Release](https://blog.open-metadata.org/openmetadata-0-13-2-release-e32c0de93361) was originally published in [OpenMetadata](https://blog.open-metadata.org) on Medium, where people are continuing the conversation by highlighting and responding to this story. [#data](/blog/tag/data)[#metadata](/blog/tag/metadata)[#open-source](/blog/tag/open-source) Ready for trusted intelligence? See how Collate helps teams work smarter with trusted data [Get Started](/welcome)[Contact Us](/contact-sales) ## Keep Reading [View All](/blog)