[
https://issues.apache.org/jira/browse/HBASE-22955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Busbey resolved HBASE-22955.
-
Fix Version/s: 2.2.2
2.1.7
1.4.11
1.3.6
+1
Checked sigs and hashes.
Built src. Ran a few commands against a cluster. Seemed to work fine.
S
On Mon, Sep 16, 2019 at 11:31 AM Peter Somogyi wrote:
> Please vote on this Apache HBase Operator Tools Release Candidate (RC),
> 1.0.0.
>
> The VOTE will remain open for at least 72 hours.
>
>
Guanghao Zhang created HBASE-23035:
--
Summary: Retain region to the last RegionServer make the failover
slower
Key: HBASE-23035
URL: https://issues.apache.org/jira/browse/HBASE-23035
Project: HBase
stack created HBASE-23034:
-
Summary: List all of our repos in one place (download page? Home
page?)
Key: HBASE-23034
URL: https://issues.apache.org/jira/browse/HBASE-23034
Project: HBase
Issue
[
https://issues.apache.org/jira/browse/HBASE-22804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xu Cang resolved HBASE-22804.
-
Fix Version/s: 1.4.12
2.2.2
2.1.7
1.3.6
Please vote on this Apache HBase Operator Tools Release Candidate (RC),
1.0.0.
The VOTE will remain open for at least 72 hours.
[ ] +1 Release this package as Apache HBase Operator Tools 1.0.0
[ ] -1 Do not release this package because ...
The tag to be voted on is 1.0.0RC0:
[
https://issues.apache.org/jira/browse/HBASE-22699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-22699.
---
Fix Version/s: (was: 3.0.0)
Resolution: Fixed
Resolving. Pushed PR to branch-2.1 => branch-2 but
[
https://issues.apache.org/jira/browse/HBASE-23033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-23033.
---
Resolution: Fixed
> Do not run git-commit-id-plugin when .git is missing
>
Peter Somogyi created HBASE-23033:
-
Summary: Do not run git-commit-id-plugin when .git is missing
Key: HBASE-23033
URL: https://issues.apache.org/jira/browse/HBASE-23033
Project: HBase
Issue
[
https://issues.apache.org/jira/browse/HBASE-23029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-23029.
---
Resolution: Fixed
Merged #35 to master.
> Handle hbase-operator-tools releasenotes in
[
https://issues.apache.org/jira/browse/HBASE-23026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-23026.
---
Resolution: Fixed
Merged #34 to master.
> docker run command should not quote JAVA_VOL
>
Tamas Penzes created HBASE-23032:
Summary: Upgrade to Curator 4.2.0
Key: HBASE-23032
URL: https://issues.apache.org/jira/browse/HBASE-23032
Project: HBase
Issue Type: Improvement
Peter Somogyi created HBASE-23031:
-
Summary: Upgrade Yetus version in RM scripts
Key: HBASE-23031
URL: https://issues.apache.org/jira/browse/HBASE-23031
Project: HBase
Issue Type:
> I think we can do it in https://issues.apache.org/jira/browse/HBASE-22986.
Sounds good!
> To avoid this, I think we need to remove the images from the history of
the
source repository maybe by using filter-branch?
We should not rewrite history. It will remain there but when you do shallow
[
https://issues.apache.org/jira/browse/HBASE-22804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi reopened HBASE-22804:
---
This was only committed to branch-1.
> Provide an API to get list of successful regions and
Jiayi Liu created HBASE-23030:
-
Summary: Update completebulkload hadoop jar usage in related doc
Key: HBASE-23030
URL: https://issues.apache.org/jira/browse/HBASE-23030
Project: HBase
Issue
[
https://issues.apache.org/jira/browse/HBASE-23027?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guanghao Zhang resolved HBASE-23027.
Fix Version/s: 2.2.2
Resolution: Fixed
Pushed to branch-2.2. Thanks [~meiyi] for
[
https://issues.apache.org/jira/browse/HBASE-22890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Reid Chan reopened HBASE-22890:
---
> Verify the files when RegionServer is starting and BucketCache is in file mode
>
Sounds good to me.
So, should we move the images to the hbase-site repository (
https://github.com/apache/hbase-site)
and move the README itself to the HBase Book?
I think we can do it in https://issues.apache.org/jira/browse/HBASE-22986.
> every time we pull the repository for the builds it
Peter Somogyi created HBASE-23029:
-
Summary: Handle hbase-operator-tools releasenotes in release
making script
Key: HBASE-23029
URL: https://issues.apache.org/jira/browse/HBASE-23029
Project: HBase
Guanghao Zhang created HBASE-23028:
--
Summary: Add 2.2.1 to download page
Key: HBASE-23028
URL: https://issues.apache.org/jira/browse/HBASE-23028
Project: HBase
Issue Type: Sub-task
Guanghao Zhang created HBASE-23027:
--
Summary: Set version to 2.2.2-SNAPSHOT in branch-2.2
Key: HBASE-23027
URL: https://issues.apache.org/jira/browse/HBASE-23027
Project: HBase
Issue Type:
[
https://issues.apache.org/jira/browse/HBASE-23004?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Somogyi resolved HBASE-23004.
---
Resolution: Fixed
Pushed to hbase-site repo.
> Update 2.0 Javadoc on website
>
With 4 binding +1s, the vote passes.
Let me push out the release and send a notice.
Thanks all for verifying the release candidate.
Stack 于2019年9月14日周六 上午6:46写道:
> +1
> IMO, CHANGES and RELEASENOTES should accumulate all changes, not just show
> what is in current release.
> Compat report
24 matches
Mail list logo