mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-11-04 04:29:13 +00:00
e2578d6be3
* GitBook: [#177] Documentation Update - Airflow * GitBook: [#195] Removing Cron from databaseServices * GitBook: [#196] Added trino * GitBook: [#197] removed cron from config * GitBook: [#198] Added Redash Documentation * GitBook: [#199] Added Bigquery Usage Documentation * GitBook: [#200] Added page link for presto * GitBook: [#201] Added Local Docker documentation * GitBook: [#202] Added Documentation for Local Docker Setup * GitBook: [#203] Added Git Command to clone Openmetadata in docs * GitBook: [#207] links update * GitBook: [#208] Updating Airflow Documentation * GitBook: [#210] Adding Python installation package under Airflow Lineage config * GitBook: [#211] Change the links to 0.5..0 * GitBook: [#213] Move buried connectors page up * GitBook: [#214] Update to connectors page * GitBook: [#215] Removed sub-categories * GitBook: [#212] Adding Discovery tutorial * GitBook: [#220] Updated steps to H2s. * GitBook: [#230] Complex queries * GitBook: [#231] Add lineage to feature overview * GitBook: [#232] Make feature overview headers verbs instead of nouns * GitBook: [#233] Add data reliability to features overview * GitBook: [#234] Add complex data types to feature overview * GitBook: [#235] Simplify and further distinguish discovery feature headers * GitBook: [#236] Add data importance to feature overview * GitBook: [#237] Break Connectors into its own section * GitBook: [#238] Reorganize first section of docs. * GitBook: [#239] Add connectors to feature overview * GitBook: [#240] Organize layout of feature overview into feature categories as agreed with Harsha. * GitBook: [#242] Make overview paragraph more descriptive. * GitBook: [#243] Create a link to Connectors section from feature overview. * GitBook: [#244] Add "discover data through association" to feature overview. * GitBook: [#245] Update importance and owners gifs * GitBook: [#246] Include a little more descriptive documentation for key features. * GitBook: [#248] Small tweaks to intro paragraph. * GitBook: [#249] Clean up data profiler paragraph. * GitBook: [#250] Promote Complex Data Types to its own feature. * GitBook: [#251] Update to advanced search * GitBook: [#252] Update Roadmap * GitBook: [#254] Remove old features page (text and screenshot based). * GitBook: [#255] Remove references to removed page. * GitBook: [#256] Add Descriptions and Tags section to feature overview. * GitBook: [#257] Update title for "Know Your Data" Co-authored-by: Ayush Shah <ayush.shah@deuexsolutions.com> Co-authored-by: Suresh Srinivas <suresh@getcollate.io> Co-authored-by: Shannon Bradshaw <shannon.bradshaw@arrikto.com> Co-authored-by: OpenMetadata <github@harsha.io>
2.0 KiB
2.0 KiB
Feed
This schema defines the Thread entity. A Thread is a collection of posts made by the users. The first post that starts a thread is about a data asset from a user. Other users can respond to this post by creating new posts in the thread. Note that bot users can also interact with a thread. A post can contains links that mention Users or other Data Assets.
**$id: **https://open-metadata.org/schema/entity/feed/thread.json
Type: object
Properties
- id
required- Unique identifier that identifies an entity instance.
- $ref: ../../type/basic.json#/definitions/uuid
- href
- Link to the resource corresponding to this entity.
- $ref: ../../type/basic.json#/definitions/href
- threadTs
- Timestamp of the when the first post created the thread.
- $ref: ../../type/basic.json#/definitions/dateTime
- about
required- Data asset about which this thread is created for with format <#E/{enties}/{entityName}/{field}/{fieldValue}.
- $ref: ../../type/basic.json#/definitions/entityLink
- addressedTo
- User or team this thread is addressed to in format <#E/{enties}/{entityName}/{field}/{fieldValue}.
- $ref: ../../type/basic.json#/definitions/entityLink
- posts
required- Type:
array- Items
- $ref: #/definitions/post
- Type:
Type definitions in this schema
post
- Post within a feed.
- Type:
object - Properties
- message
required- Message in markdown format. See markdown support for more details.
- Type:
string
- postTs
- Timestamp of the post.
- Type:
string - String format must be a "date-time"
- from
required- ID of User (regular user or a bot) posting the message.
- $ref: ../../type/basic.json#/definitions/uuid
- message
This document was updated on: Monday, October 18, 2021