...
ALTER TABLE’ tbl’ ALTER COLUMN ‘mycolumn’ SET DATA TYPE LONG NOT NULL DEFAULT -1;
Risks and Assumptions
// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.
Discussion Links
// Links to discussions on the devlist, if applicable.
Reference Links
// Links to various reference documents, if applicable.
Tickets
- it is assumed, that BinaryTuple protocol will not changed. Otherwise, we will have to implement a solution to convert data explicitly, when row is upgraded.
- all storage engines are compatible this feature. Otherwise, we will need a workaround, e.g. to fallback to a slow blocking solution.
- user may experience unexpected transaction rolling back for long transactions, which overlap the change column type operation.
Tickets
Jira |
---|
server | ASF JIRA |
---|
columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
---|
columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
---|
serverId | 5aa69414-a9e9-3523-82ec-879b028fb15b |
---|
key | IGNITE-19413 |
---|
|
// Links or report with relevant JIRA tickets.