Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Request to enable providing space, version information in the @edge directivee.g. type Relationship @edge(space: “A”, version: “1”) { relationName: String!, relationType: RelationType}
The change in the requiredness of one of the field is not consistently validated across all the inherited types.Below works and the data model is published.Data Model Version - 1interface Person @view(version: "1"){name: String}type Actor implements Person @view(version: "1") { name: String didWinOscar: Boolean}Next stepBelow doesn't work and I get an error "Can not change the nullability of the property\n We do not support modifying a field's 'required'ness at the moment."interface Person @view(version: "2"){name: String!}type Actor implements Person @view(version: "2") { name: String! didWinOscar: Boolean}Next stepBelow worksinterface Person @view(version: "2"){name: String}type Actor implements Person @view(version: "2") { name: String! didWinOscar: Boolean}
type Employee {name: String!department: Department!}type Department {name: String!}I can't model a use case where an employee must belong to a department.
One or more employees must belong to a department and each employee instance is non nullable. Below type is accepted through UI in CDF. type Department {name: String!,employees: [Employee!]!}2. Zero or more employees can belong to a department and it can be a null object or an employee instance. Below type is accepted through UI in CDF.type Department {name: String!,employees: [Employee]}3. Zero or more employees can belong to a department and it has to be a non null employee instance. Below type isn't accepted through UI in CDF.type Department {name: String!,employees: [Employee!]}I am trying to enforce field nullability use case as suggested here - https://www.apollographql.com/docs/apollo-server/schema/schema/#field-nullabilityBelow example may make my above question more meaningful in the CDF FDM context.type Department {name: String!,employees: [String!]} How can I ensure that the list of strings are non-nulls? Also, Would Strings be stored in a separate node and connected thro
Below works and the data model is published.Data Model Version - 1type Employee @view(version: "1"){name: String}Next stepBelow doesn't work and I get an error "Can not change the nullability of the property\n We do not support modifying a field's 'required'ness at the moment."Data Model Version - 2type Employee @view(version: "2"){name: String!}
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
