[
https://issues.apache.org/jira/browse/HBASE-13147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14517061#comment-14517061
]
Anoop Sam John commented on HBASE-13147:
----------------------------------------
While creating the HTDs and TableDescriptors from reading from FS, we will call
HTD#convert(final TableSchema ts)
HTableDescriptor(final TableName name, HColumnDescriptor[] families)
setName(name);
setMetaFlags(this.name);
This contains code
{code}
byte[] version = getValue(META_VERSION_KEY);
if (version == null) {
setMetaVersion(HConstants.META_VERSION);
}
{code}
So for old descriptor with no meta version in it, we consider as new version
Will the below code in MetaMigration will get used then?
{code}
else if (current.getMetaVersion() < HConstants.META_VERSION) {
LOG.info("Meta has different version, running migration "
+ current.getMetaVersion() + " -> " + HConstants.META_VERSION);
MetaMigration.doMigration(fsd, current, compiledMetaDescriptor);
}
{code}
> Load actual META table descriptor, don't use statically defined one.
> --------------------------------------------------------------------
>
> Key: HBASE-13147
> URL: https://issues.apache.org/jira/browse/HBASE-13147
> Project: HBase
> Issue Type: Bug
> Components: master, regionserver
> Affects Versions: 2.0.0
> Reporter: Andrey Stepachev
> Assignee: Andrey Stepachev
> Attachments: HBASE-13147-branch-1.patch,
> HBASE-13147-branch-1.v2.patch, HBASE-13147.patch, HBASE-13147.v2.patch,
> HBASE-13147.v3.patch, HBASE-13147.v4.patch, HBASE-13147.v4.patch,
> HBASE-13147.v5.patch, HBASE-13147.v6.patch, HBASE-13147.v7.patch
>
>
> In HBASE-13087 stumbled on the fact, that region servers don't see actual
> meta descriptor, they use their own, statically compiled.
> Need to fix that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
