[
https://issues.apache.org/jira/browse/IGNITE-20966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Shergalis updated IGNITE-20966:
---------------------------------------
Description:
At least, 'Commit failed because schema %d is not forward-compatible with %d
for table %d' should be improved to make it useful for an end-user. We shoiuld
at least add table name to the message.
What was done:
Final error contains descriptions of all failed validations, i.e.
{quote}"Name of the table has been changed; Added nonnull columns without
default value: [NON_NULL_WITHOUT_DEFAULT_COL];
Columns were dropped; Columns change validation failed: [TYPE_CHANGED_COL: Type
changed;
ADD_DEFAULT_COL: Default value changed; CHANGE_DEFAULT_COL: Default value
changed; DROP_DEFAULT_COL: Default value changed]"
{quote}
. Where it was trivial, changed tableID to table name - for the case when table
was already dropped created a new issue.
was:At least, 'Commit failed because schema %d is not forward-compatible with
%d for table %d' should be improved to make it useful for an end-user. We
shoiuld at least add table name to the message.
> Improve error messages for schema change validation failures
> ------------------------------------------------------------
>
> Key: IGNITE-20966
> URL: https://issues.apache.org/jira/browse/IGNITE-20966
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Philipp Shergalis
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At least, 'Commit failed because schema %d is not forward-compatible with %d
> for table %d' should be improved to make it useful for an end-user. We
> shoiuld at least add table name to the message.
>
> What was done:
> Final error contains descriptions of all failed validations, i.e.
> {quote}"Name of the table has been changed; Added nonnull columns without
> default value: [NON_NULL_WITHOUT_DEFAULT_COL];
> Columns were dropped; Columns change validation failed: [TYPE_CHANGED_COL:
> Type changed;
> ADD_DEFAULT_COL: Default value changed; CHANGE_DEFAULT_COL: Default value
> changed; DROP_DEFAULT_COL: Default value changed]"
> {quote}
> . Where it was trivial, changed tableID to table name - for the case when
> table was already dropped created a new issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
