> create a new column with the new type (followed by UPSERT SELECT)the problem is we can't use the same name as it would throw "duplicate column name" exception, so will need to copy the values twice (first into temp column and then to the new column with the original name and new type)is it possible to rename columns in Phoenix?thanksAlexOn Tue, Oct 20, 2015 at 12:41 PM, James Heather <firstname.lastname@example.org> wrote:
This would be of huge benefit to us.
One of the problems we have with MySQL is the locking that's done for many schema changes. Any support in Phoenix for online schema changes will be a major plus point.
JamesOn 20 Oct 2015 5:38 p.m., "James Taylor" <email@example.com> wrote:We don't support altering the data type of a column directly. The way I've seen this done is:- create a new column with the new type- copy the old value over, coercing it to the new type (either using UPSERT SELECT or MR)- start using the new column instead of the old column- drop the old columnWe have a JIRA for it (PHOENIX-152). In theory, we could automate the above process, doing it asynchronously where the data type change wouldn't take effect until the entire process is complete.Thanks,JamesOn Mon, Oct 19, 2015 at 10:29 AM, ALEX K <firstname.lastname@example.org> wrote:Is it possible to change data type of column in Apache Phoenix without losing HBase data?