You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduces ResultSummary.gqlStatusObjects as preview feature.
GqlStatusObject is a GQL compliant Notification object and status of query execution, this new object includes gqlStatus and statusDescription.
ResultSummary.gqlStatusObjects always contains at least 1 status representing the Success, No Data or Omitted Result. When discarding records in a RxSession while connected to a non-GQL-aware server, the driver might not be able to tell apart Success and No Data.
The GqlStatusObjects will be presented in the following order:
A “no data” (02xxx) has precedence over a warning;
A warning (01xxx) has precedence over a success.
A success (00xxx) has precedence over anything informational (03xxx)
Migrating from Notification
Most of the properties present in the Notification are present in the new object, except code and title.
The GqlStatusObject.gqlStatus is equivalent of code in the Notification, but with values compliant with GQL.
The properties GqlStatusObject.classification and GqlStatusObject.rawClassification are equivalent to Notification.category and Notification.rawCategory. The name change is needed because category has a different meaning in GQL.
Configuration
Filtering gqlStatusObjects can be done using in the same way as filtering notifications. However, non-notification status can not be filtered (such as Success or No Data).
The property disabledClassifications was added to NotificationFilter for being named consistently with GQL. This property is equivalent to disabledCategories and it be can used interchangeably. However, they can not be used at the same time. An exception will be raised in this scenario.
The bolt protocol 5.5 should support a slightly different way of
configuring notifications filtering.
This new configuration change the name of categories to classification
to be aligned with the definitions on Gql standard.
This changes doesn't includes add the protocol to handshake and the
proper configuration on the driver side.
bigmontz
changed the title
Introduces ´GqlStatusObject support as notifications to ResultSummary`
Introduce ´GqlStatusObject support as notifications to ResultSummary`
May 16, 2024
bigmontz
changed the title
Introduce ´GqlStatusObject support as notifications to ResultSummary`
Introduce GqlStatusObject support as notifications to ResultSummaryMay 17, 2024
ResultSummary.gqlStatusObjects always contains at least 1 status representing the Success, No Data or Omitted Result. This status will be always the first one.
I thought this isn't the case.
When discarding records while connected to a non-GQL aware server, the driver might not be able to tell apart Success and No Data.
This only applies to the reactive driver, doesn't it? Might be worth being explicit here.
All following status are notifications like warnings about problematic queries or other valuable information that can be presented in a client.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Introduces
ResultSummary.gqlStatusObjects
as preview feature.GqlStatusObject
is a GQL compliantNotification
object and status of query execution, this new object includesgqlStatus
andstatusDescription
.ResultSummary.gqlStatusObjects
always contains at least 1 status representing theSuccess
,No Data
orOmitted Result
. When discarding records in a RxSession while connected to a non-GQL-aware server, the driver might not be able to tell apartSuccess
andNo Data
.The GqlStatusObjects will be presented in the following order:
02xxx
) has precedence over a warning;01xxx
) has precedence over a success.00xxx
) has precedence over anything informational (03xxx
)Migrating from Notification
Most of the properties present in the
Notification
are present in the new object, exceptcode
andtitle
.The
GqlStatusObject.gqlStatus
is equivalent ofcode
in theNotification
, but with values compliant with GQL.The properties
GqlStatusObject.classification
andGqlStatusObject.rawClassification
are equivalent toNotification.category
andNotification.rawCategory
. The name change is needed becausecategory
has a different meaning in GQL.Configuration
Filtering
gqlStatusObjects
can be done using in the same way as filteringnotifications
. However, non-notification status can not be filtered (such asSuccess
orNo Data
).The property
disabledClassifications
was added toNotificationFilter
for being named consistently with GQL. This property is equivalent todisabledCategories
and it be can used interchangeably. However, they can not be used at the same time. An exception will be raised in this scenario.