Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 need to implement data conversion code 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 transactions rolling back for long transactions, which overlap the change column type operation.

Tickets

Jira
serverASF JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyIGNITE-19413
// Links or report with relevant JIRA tickets.