Schema issueshttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues2024-01-08T13:43:28Zhttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/144Schema Bootstrap failure issue2024-01-08T13:43:28ZIsha KumariSchema Bootstrap failure issueThe system schema has experienced substantial growth, expanding from an initial range of 200-300 to approximately 900. Consequently, I've been facing failures in the schema during script execution. Notably, the script is designed to rei...The system schema has experienced substantial growth, expanding from an initial range of 200-300 to approximately 900. Consequently, I've been facing failures in the schema during script execution. Notably, the script is designed to reinitiate the schema upon encountering failures
Additionally, the Bootstrap process is showing failures randomly due to the schema variations. To address this, I have implemented error-catching mechanisms and introduced a retry strategy to mitigate the impact of these intermittent failures.M22 - Release 0.25Isha KumariIsha Kumarihttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/139Add /liveness_check2023-11-21T19:08:35ZRiabokon Stanislav(EPAM)[GCP]Add /liveness_checkNeed to add the endpoint '/liveness_check' in order to verify the operational status of the Schema Service.Need to add the endpoint '/liveness_check' in order to verify the operational status of the Schema Service.M22 - Release 0.25Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/49Job Failed #3846292023-08-07T09:56:06ZAbhishek Kumar (SLB)Job Failed #384629The changes were done to the Azure module only though IBM bootstrapping is failing.
Could you please take a look and fix the bootstrapping issue.
Job [#384629](https://community.opengroup.org/osdu/platform/system/schema-service/-/jobs/3...The changes were done to the Azure module only though IBM bootstrapping is failing.
Could you please take a look and fix the bootstrapping issue.
Job [#384629](https://community.opengroup.org/osdu/platform/system/schema-service/-/jobs/384629) failed for 5342e3fc0accfe6fbeec0cb13c5fad533b42abfc:Anuj GuptaAnuj Guptahttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/6[Schema Service] IBM SPI Implementation2022-08-23T10:47:24Zethiraj krishnamanaidu[Schema Service] IBM SPI ImplementationAlan BrazAlan Braz2020-09-04https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/57Upgrade Core IBM Dependency2022-02-11T21:59:05ZDavid Diederichd.diederich@opengroup.orgUpgrade Core IBM Dependencyhttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/77Job Failed #6925242021-12-14T12:29:03ZAbhishek Kumar (SLB)Job Failed #692524IBM Deployment is failing kindly unblock us.
Job [#692524](https://community.opengroup.org/osdu/platform/system/schema-service/-/jobs/692524) failed for 7ba9e83323cea20e8e5c2017e667677e40372016:IBM Deployment is failing kindly unblock us.
Job [#692524](https://community.opengroup.org/osdu/platform/system/schema-service/-/jobs/692524) failed for 7ba9e83323cea20e8e5c2017e667677e40372016:Anuj GuptaShrikant GargAnuj Guptahttps://community.opengroup.org/osdu/platform/system/schema-service/-/issues/9[System/Core] Schema Service2020-11-09T20:06:02ZStephen Whitley (Invited Expert)[System/Core] Schema ServiceThe schema service is both an implementation of the schema standard defined below and a service to help create, manage and share schemas between different users. It aims to both raise awareness of the different models used by teams to he...The schema service is both an implementation of the schema standard defined below and a service to help create, manage and share schemas between different users. It aims to both raise awareness of the different models used by teams to help reuse both of the data sources but also of the schemas themselves. This will hopefully help reduce the friction obtaining data from multiple sources.
**Schema service goals**:
- To enable easier creation of new schemas
- To discover popular schemas in use today
- To make reuse of existing schemas easier to achieve
**Schema Definition**:
A schema is the model definition for a particular entity. At its core it defines the property names, their types and relationships to other models. It also includes certain qualities to expect about the actual entities and the data its hold.
An entity is a specific instance of a schema. A schema is assigned an entityType which categorizes the data the schema defines. For example 'well' is an example of an entityType.
An entityType is assigned an 'authority'. An authority is a namespace to help differentiate types defined by different groups e.g. it allows for both an slb:well and a chevron:well type to exist.
With schema definitions we aim to define the standards for data models used by a DDMS. This will reduce the friction with different systems data sharing needs helping with our vision to enable data discovery and sharing.
**Principles**:
- Low threshold for Schema Registration
: We should make it as easy as possible to create a new schema and register it, Whether this be through examples, tooling to help auto-generate a schema or validators to give early feedback when invalid markup is used. Also it must be easy to reuse existing schema definitions - DE-schemas and external schemas - using composition.
- Easy to consume
: JSON schema allows for JSON pointers to other schema parts and fragments, which need to be chased to obtain a full schema. A registered DE schema is self-contained, i.e. it contains only internal references "$ref": "#/definitions/../target". This is particularly important for schemas, which originally refer to external URLs. All internal "$ref" are resolvable. Consumers find all the answers inside the single schema document. The schema has a predictable structure.
- Robust
: All Schemas are read-only and versioned. The major version is controlled by the schema producer, the minor version is controlled by the schema service. When a schema is assigned version 1.0.0 or higher no breaking changes can be applied on new schema versions. Breaking changes will be allowed on any schema version with major version 0.X.X.
- Breaking changes are:
- removed properties
- changes to existing properties e.g.changed types, changed required properties
: This gives consumers confidence that they can use data without fear of breaks in the future. However schemas can be deprecated meaning that no new data will be assigned to it.
**Schema attributes**
Schema definitions are based on in the [JSON schema standard](https://json-schema.org/latest/json-schema-core.html) and [OpenAPI 3](https://swagger.io/docs/specification/data-models/). There are subtle differences in the keyword support, which are explained in conjunction with OAS3 [here](https://swagger.io/docs/specification/data-models/keywords/).
- [x] AWS
- [x] Azure
- [x] IBM
- [ ] GCPM1 - Release 0.1Hrvoje MarkovicFerris ArgyleDania Kodeih (Microsoft)Wladmir FrazaoChris ZhangMichael CleminsonHrvoje Markovic2020-10-30https://community.opengroup.org/osdu/platform/system/schema-service/-/issues/13Schema Service - Integration test issue2020-08-25T11:56:47ZShaonSchema Service - Integration test issue1. Schema Id is already present - In the failing test cases currentMajorVersion & currentMinorVersion are retrieved from the context(ScenarioScoped class) and those versions are inceremented by 1 respectively and that generates the schem...1. Schema Id is already present - In the failing test cases currentMajorVersion & currentMinorVersion are retrieved from the context(ScenarioScoped class) and those versions are inceremented by 1 respectively and that generates the schemaId which is already present in tenant/DB
2. Pre-integration and post-integration data setup and cleanup is missing that results in test data to be stored in DB foreverethiraj krishnamanaiduSubham Agarwalethiraj krishnamanaidu