[
https://issues.apache.org/jira/browse/HBASE-26264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17512900#comment-17512900
]
Hudson commented on HBASE-26264:
--------------------------------
Results for branch branch-2.5
[build #78 on
builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(x) {color:red}-1 general checks{color}
-- For more information [see general
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78/General_20Nightly_20Build_20Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(x) {color:red}-1 source release artifact{color}
-- See build output for details.
(x) {color:red}-1 client integration test{color}
-- Something went wrong with this stage, [check relevant console
output|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.5/78//console].
> Add more checks to prevent misconfiguration on store file tracker
> -----------------------------------------------------------------
>
> Key: HBASE-26264
> URL: https://issues.apache.org/jira/browse/HBASE-26264
> Project: HBase
> Issue Type: Sub-task
> Components: conf, HFile
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Priority: Major
> Fix For: 2.6.0, 3.0.0-alpha-3
>
>
> For example, when creating new tables, if the store file tracker is
> configured to MigrationStoreFileTracker, we should fail the creation and tell
> users you should not use this store file tracker for a new table.
> And when switching the implementation for store file tracker, we should let
> end users first switch to MigrationStoreFileTracker, and then to the final
> target store file tracker. If end users configure wrong store file tracker,
> we should fail the alter table operation.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)