[
https://issues.apache.org/jira/browse/KUDU-3176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17177155#comment-17177155
]
Attila Bukor commented on KUDU-3176:
------------------------------------
I've been trying to reproduce this in the past couple of hours, but couldn't.
Every single combination I could think of, except for one, works fine. I tried
on different cluster versions with different kudu-backup2 versions. The only
failure I could get was when I tried to restore a backup that didn't have table
owner on a cluster that did. This failed due to trying to set the owner to an
empty string, but this is a different issue and it's solved by 4bed27234, you
just need to add {{--restoreOwner false}}. Whatever it was, I likely messed up
the backup somehow, or it was some other environmental issue. I think it is
safe to say this bug doesn't exist.
> Backup & restore incompatibility
> --------------------------------
>
> Key: KUDU-3176
> URL: https://issues.apache.org/jira/browse/KUDU-3176
> Project: Kudu
> Issue Type: Bug
> Reporter: Attila Bukor
> Assignee: Attila Bukor
> Priority: Blocker
>
> The ownership in the backup metadata introduced in KUDU-3090 seems to have
> backward/forward compatibility issues as restoring a backup with
> post-ownership backup tool that was created on a pre-ownership cluster with
> the matching backup tool fails. Other combinations might also fail but I
> haven't reproduced them so far.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
