[jira] [Created] (HBASE-21841) Allow inserting null values throw DataSource API

Balazs Meszaros created HBASE-21841: --- Summary: Allow inserting null values throw DataSource API Key: HBASE-21841 URL: https://issues.apache.org/jira/browse/HBASE-21841 Project: HBase Issue

[jira] [Created] (HBASE-21842) Remove ${revision} from parent POMs

Balazs Meszaros created HBASE-21842: --- Summary: Remove ${revision} from parent POMs Key: HBASE-21842 URL: https://issues.apache.org/jira/browse/HBASE-21842 Project: HBase Issue Type: Improve

[jira] [Reopened] (HBASE-21819) Generate CHANGES.md and RELEASENOTES.md for 2.1.3

[ https://issues.apache.org/jira/browse/HBASE-21819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-21819: --- > Generate CHANGES.md and RELEASENOTES.md for 2.1.3 > -

[jira] [Created] (HBASE-21843) AM misses region assignment in catastrophic scenarios where RS assigned to the region in Meta does not have a WAL dir.

Wellington Chevreuil created HBASE-21843: Summary: AM misses region assignment in catastrophic scenarios where RS assigned to the region in Meta does not have a WAL dir. Key: HBASE-21843 URL: https://issue

Re: HBase Website Cleanup task

Does anyone have any concern with removing 0.94 documentation completely from hbase.apache.org? Currently it is hosted at https://hbase.apache.org/0.94/ to which we don't have any direct link but with a few hops a user can reach this area. This release is almost 4 years old! I had a chat with Sean

Re: The first HBase 1.5.0 release candidate (RC0) is available

Based on my own testing I was going to vote +1.I built 1.5.0 from source, and ran it with the tip of the Phoenix 4.x. I regularly load a lot of data, execute Phoenix queries, etc. Nothing undue, nothing undue in the logs either. I'll try to reproduce the test failures. Since Andy can't reproduce

Re: HBase Website Cleanup task

Sounds good by me. S On Mon, Feb 4, 2019 at 7:40 AM Peter Somogyi wrote: > Does anyone have any concern with removing 0.94 documentation completely > from hbase.apache.org? Currently it is hosted at > https://hbase.apache.org/0.94/ to which we don't have any direct link but > with a few hops a u

Branch-2.0: EOL and a 2.0.5RC

I was going to put up a 2.0.5 RC to address https://issues.apache.org/jira/browse/HBASE-21791.Its been about a month since 2.0.4. There are 50 odd fixes in 2.0.5 currently [1] mostly perfunctory backports. Stepping back though, I'd like to entertain our letting the branch-2.0.x releases go. After

Re: Branch-2.0: EOL and a 2.0.5RC

big +1 from me. On Mon, Feb 4, 2019 at 12:29 PM Stack wrote: > > I was going to put up a 2.0.5 RC to address > https://issues.apache.org/jira/browse/HBASE-21791.Its been about a month > since 2.0.4. There are 50 odd fixes in 2.0.5 currently [1] mostly > perfunctory backports. > > Stepping back th

Re: Branch-2.0: EOL and a 2.0.5RC

+1 On Mon, Feb 4, 2019 at 10:29 AM Stack wrote: > I was going to put up a 2.0.5 RC to address > https://issues.apache.org/jira/browse/HBASE-21791.Its been about a month > since 2.0.4. There are 50 odd fixes in 2.0.5 currently [1] mostly > perfunctory backports. > > Stepping back though, I'd lik

Re: HBase Website Cleanup task

+1 On Mon, Feb 4, 2019 at 10:04 AM Stack wrote: > Sounds good by me. > S > > On Mon, Feb 4, 2019 at 7:40 AM Peter Somogyi wrote: > > > Does anyone have any concern with removing 0.94 documentation completely > > from hbase.apache.org? Currently it is hosted at > > https://hbase.apache.org/0.94/

[jira] [Created] (HBASE-21844) Master could get stuck in initializing state while waiting for meta

Bahram Chehrazy created HBASE-21844: --- Summary: Master could get stuck in initializing state while waiting for meta Key: HBASE-21844 URL: https://issues.apache.org/jira/browse/HBASE-21844 Project: HB

Re: HBase Website Cleanup task

My only concern is that all my searches targeting our user guide land in 0.94 docs. I don't know why the SEO lands us thusly, but I fear that suddenly it'll look to user searches like the project is dead. On Mon, Feb 4, 2019 at 11:46 AM Misty Linville wrote: > +1 > > On Mon, Feb 4, 2019 at 10:04

Re: HBase Website Cleanup task

If we are concerned about SEO, we should try to set up 301 Redirect to the latest doc when we remove 0.94. That should alleviate some of the problems with users landing on dead links. Over time the result should adjust, or we could set up Google Search Console for HBase site, and trigger a reindex.

Re: HBase Website Cleanup task

We should add rel=canonical info to all the headers and always point to the latest as canonical. On Mon, Feb 4, 2019 at 2:56 PM William Shen wrote: > If we are concerned about SEO, we should try to set up 301 Redirect to the > latest doc when we remove 0.94. That should alleviate some of the pro

Re: Branch-2.0: EOL and a 2.0.5RC

+1 Andrew Purtell 于2019年2月5日周二 上午3:24写道： > +1 > > > On Mon, Feb 4, 2019 at 10:29 AM Stack wrote: > > > I was going to put up a 2.0.5 RC to address > > https://issues.apache.org/jira/browse/HBASE-21791.Its been about a month > > since 2.0.4. There are 50 odd fixes in 2.0.5 currently [1] mostly >

[jira] [Created] (HBASE-21845) Make a 2.0.5 release

stack created HBASE-21845: - Summary: Make a 2.0.5 release Key: HBASE-21845 URL: https://issues.apache.org/jira/browse/HBASE-21845 Project: HBase Issue Type: Bug Components: release Affe

[jira] [Reopened] (HBASE-21727) Simplify documentation around client timeout

[ https://issues.apache.org/jira/browse/HBASE-21727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-21727: --- HBaseConfiguration is IA.Public and we removed a public method in it, I think this can only be done for

Re: The first HBase 1.5.0 release candidate (RC0) is available

I think HBASE-21727 should be partially reverted since it removed a public method in HBaseConfiguration which is marked as IA.Public? la...@apache.org 于2019年2月5日周二 上午1:54写道： > Based on my own testing I was going to vote +1.I built 1.5.0 from source, > and ran it with the tip of the Phoenix 4.x.