Re: [VOTE] First release candidate for HBase 1.3.1 (RC0) is available
Hmm. Looks like this change has already went out in 1.2.5 though, looking at https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12338339&projectId=12310753 Those the compat report posted there on the RC is no longer available (we can re-run it). Should we revert it in 1.2.6 back then, or leave as is? On Wed, Apr 5, 2017 at 11:32 PM, Mikhail Antonov wrote: > Thanks Yu Li! > > You picture doesn't load for me, could you repost? I'll run compatibility > checker too. > > -Mikhail > > On Wed, Apr 5, 2017 at 11:22 PM, Yu Li wrote: > >> -1 (non-binding) >> >> Checked sums and signatures: ok >> Built from source: ok (7u79) >> RAT check passed: ok (7u79) >> Compatibility check: Failed >> >> >> >> Checked the commit history and the above issue is introduced by >> HBASE-17716, and have opened HBASE-17886 to fix it. >> >> Best Regards, >> Yu >> >> On 6 April 2017 at 07:38, Mikhail Antonov wrote: >> >>> Hello everyone, >>> >>> I'm pleased to announce the first release candidate for Apache HBase >>> 1.3.1 is >>> available to download and testing. >>> >>> Artifacts are available here: >>> >>> https://dist.apache.org/repos/dist/dev/hbase/1.3.1RC0/ >>> >>> Maven artifacts are available in the staging repository: >>> >>> https://repository.apache.org/content/repositories/orgapachehbase-1165 >>> >>> All artifacts are signed with my code signing key 35A4ABE2, which is also >>> in the project KEYS file at >>> >>> http://www.apache.org/dist/hbase/KEYS >>> >>> these artifacts correspond to commit hash >>> >>> 2a425fc420a3de98eedd2ee7b703bb2873127f0e tagged as 1.3.1RC0. >>> >>> HBase 1.3.1 is the first maintenance release in the HBase 1.3.z release >>> line, >>> continuing on the theme of bringing a stable, reliable database to the >>> Hadoop and NoSQL communities. This release includes 67 resolved issues >>> since the initial 1.3.0 release that was 3 month ago. >>> >>> The full list of issues addressed is available at >>> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje >>> ctId=12310753&version=12335746 >>> >>> and also in the CHANGES.txt file in the root directory of the source >>> tarball. >>> >>> Please take a few minutes to verify the release and vote on >>> releasing it: >>> >>> [ ] +1 Release this package as Apache HBase 1.3.1 >>> [ ] +0 no opinion >>> [ ] -1 Do not release this package because... >>> >>> This Vote will run for one week and close Wed Apr 12, 2017 22:00 PST. >>> >>> Thanks ! (also separate thanks to Andrew Purtell for the help to get the >>> RC >>> out) >>> >>> -Mikhail Antonov >>> >> >> > > > -- > Thanks, > Michael Antonov > -- Thanks, Michael Antonov
Re: [VOTE] First release candidate for HBase 1.3.1 (RC0) is available
Thanks Yu Li! You picture doesn't load for me, could you repost? I'll run compatibility checker too. -Mikhail On Wed, Apr 5, 2017 at 11:22 PM, Yu Li wrote: > -1 (non-binding) > > Checked sums and signatures: ok > Built from source: ok (7u79) > RAT check passed: ok (7u79) > Compatibility check: Failed > > > > Checked the commit history and the above issue is introduced by > HBASE-17716, and have opened HBASE-17886 to fix it. > > Best Regards, > Yu > > On 6 April 2017 at 07:38, Mikhail Antonov wrote: > >> Hello everyone, >> >> I'm pleased to announce the first release candidate for Apache HBase >> 1.3.1 is >> available to download and testing. >> >> Artifacts are available here: >> >> https://dist.apache.org/repos/dist/dev/hbase/1.3.1RC0/ >> >> Maven artifacts are available in the staging repository: >> >> https://repository.apache.org/content/repositories/orgapachehbase-1165 >> >> All artifacts are signed with my code signing key 35A4ABE2, which is also >> in the project KEYS file at >> >> http://www.apache.org/dist/hbase/KEYS >> >> these artifacts correspond to commit hash >> >> 2a425fc420a3de98eedd2ee7b703bb2873127f0e tagged as 1.3.1RC0. >> >> HBase 1.3.1 is the first maintenance release in the HBase 1.3.z release >> line, >> continuing on the theme of bringing a stable, reliable database to the >> Hadoop and NoSQL communities. This release includes 67 resolved issues >> since the initial 1.3.0 release that was 3 month ago. >> >> The full list of issues addressed is available at >> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje >> ctId=12310753&version=12335746 >> >> and also in the CHANGES.txt file in the root directory of the source >> tarball. >> >> Please take a few minutes to verify the release and vote on >> releasing it: >> >> [ ] +1 Release this package as Apache HBase 1.3.1 >> [ ] +0 no opinion >> [ ] -1 Do not release this package because... >> >> This Vote will run for one week and close Wed Apr 12, 2017 22:00 PST. >> >> Thanks ! (also separate thanks to Andrew Purtell for the help to get the >> RC >> out) >> >> -Mikhail Antonov >> > > -- Thanks, Michael Antonov
Re: [VOTE] First release candidate for HBase 1.3.1 (RC0) is available
-1 (non-binding) Checked sums and signatures: ok Built from source: ok (7u79) RAT check passed: ok (7u79) Compatibility check: Failed Checked the commit history and the above issue is introduced by HBASE-17716, and have opened HBASE-17886 to fix it. Best Regards, Yu On 6 April 2017 at 07:38, Mikhail Antonov wrote: > Hello everyone, > > I'm pleased to announce the first release candidate for Apache HBase 1.3.1 > is > available to download and testing. > > Artifacts are available here: > > https://dist.apache.org/repos/dist/dev/hbase/1.3.1RC0/ > > Maven artifacts are available in the staging repository: > > https://repository.apache.org/content/repositories/orgapachehbase-1165 > > All artifacts are signed with my code signing key 35A4ABE2, which is also > in the project KEYS file at > > http://www.apache.org/dist/hbase/KEYS > > these artifacts correspond to commit hash > > 2a425fc420a3de98eedd2ee7b703bb2873127f0e tagged as 1.3.1RC0. > > HBase 1.3.1 is the first maintenance release in the HBase 1.3.z release > line, > continuing on the theme of bringing a stable, reliable database to the > Hadoop and NoSQL communities. This release includes 67 resolved issues > since the initial 1.3.0 release that was 3 month ago. > > The full list of issues addressed is available at > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > projectId=12310753&version=12335746 > > and also in the CHANGES.txt file in the root directory of the source > tarball. > > Please take a few minutes to verify the release and vote on > releasing it: > > [ ] +1 Release this package as Apache HBase 1.3.1 > [ ] +0 no opinion > [ ] -1 Do not release this package because... > > This Vote will run for one week and close Wed Apr 12, 2017 22:00 PST. > > Thanks ! (also separate thanks to Andrew Purtell for the help to get the RC > out) > > -Mikhail Antonov >
[jira] [Created] (HBASE-17886) HBASE-17716 breaks compatibility of ServerSideScanMetrics
Yu Li created HBASE-17886: - Summary: HBASE-17716 breaks compatibility of ServerSideScanMetrics Key: HBASE-17886 URL: https://issues.apache.org/jira/browse/HBASE-17886 Project: HBase Issue Type: Bug Reporter: Yu Li Assignee: Yu Li In HBASE-17716 we have changed the public field name in {{ServerSideScanMetrics}} which is IA.Public, which causes source compatibility issue, and we propose to fix it in this JIRA. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17885) Backport HBASE-15871 to branch-1
ramkrishna.s.vasudevan created HBASE-17885: -- Summary: Backport HBASE-15871 to branch-1 Key: HBASE-17885 URL: https://issues.apache.org/jira/browse/HBASE-17885 Project: HBase Issue Type: Bug Components: Scanners Affects Versions: 1.1.8, 1.2.5, 1.3.1 Reporter: ramkrishna.s.vasudevan Assignee: ramkrishna.s.vasudevan Fix For: 1.1.9, 1.2.6, 1.3.2 Will try to rebase the branch-1 patch at the earliest. Hope the fix versions are correct. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: release of HBase 1.3.1?
Thanks, Mikhail, Andrew and the rest of the team! Really appreciate it. James On Wed, Apr 5, 2017 at 4:39 PM, Mikhail Antonov wrote: > All right, I cherry picked HBASE-17227 and the first RC is out. > > Thanks Andrew for the help pushing it! > > -Mikhail > > On Wed, Apr 5, 2017 at 12:47 PM, Mikhail Antonov > wrote: > > > Thanks Andrew! > > > > So after open jiras has been re-targeted for 1.3.2 and looking at the > > filter > > `affectedVersion in (1.3.0) AND fixVersion = 1.3.2 AND status in (Open, > > "Patch Available", Reopened, "In Progress")` > > > > there are only few issues that warrant discussion before RC0, I think. > > > > - HBASE-17513, where Thrift-1 security settings are easy to > misconfigure. > >Currently marked critical, I don't think it's release blocker. > Opinions? > > - HBASE-17227, a backport of HBASE-17206, a stability fix for FSHLog. > > This one I think we should pull in. > > > > Everything else isn't important enough for an RC. > > > > Any opinions? Otherwise I'd cherry pick the latter one. > > > > -Mikhail > > > > > > On Wed, Apr 5, 2017 at 11:20 AM, Andrew Purtell > > wrote: > > > >> Branch 1.3 updated and tagged for RC0. > >> > >> remote: hbase git commit: Update POMs and CHANGES.txt for 1.3.1 RC0 > >> To https://git-wip-us.apache.org/repos/asf/hbase.git > >>fd297e2..3a2f3aa branch-1.3 -> branch-1.3 > >> * [new tag] 1.3.1RC0 -> 1.3.1RC0 > >> > >> > >> On Mon, Apr 3, 2017 at 10:35 PM, Mikhail Antonov > >> wrote: > >> > >> > Hi, > >> > > >> > I've been planning to cut an RC for 1.3.1 for some time, apologize for > >> the > >> > delay here. I'm going to go over outstanding jiras tomorrow, > >> > I think there are still few issues waiting for backports. > >> > > >> > Andrew - appreciate your offer! I have started preparations for 1.3.1 > >> > release, but any help with triaging changes, API compatibility tests > >> > and general release testing would definitely be helpful. > >> > > >> > Thanks! > >> > -Mikhail > >> > > >> > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell < > >> andrew.purt...@gmail.com> > >> > wrote: > >> > > >> > > I'd be happy to RM 1.3.1 unless someone already has it waiting in > the > >> > > wings. > >> > > > >> > > > >> > > > On Apr 3, 2017, at 5:43 PM, James Taylor > >> > wrote: > >> > > > > >> > > > Hello, > >> > > > We'd like to start supporting releases of Phoenix that work with > the > >> > > HBase > >> > > > 1.3 branch, but there's a committed fix on which we rely > >> (HBASE-17587) > >> > > for > >> > > > Phoenix to function correctly. Is there a time frame for an HBase > >> 1.3.1 > >> > > > release? > >> > > > Thanks, > >> > > > James > >> > > > >> > > >> > > >> > > >> > -- > >> > Thanks, > >> > Michael Antonov > >> > > >> > >> > >> > >> -- > >> Best regards, > >> > >>- Andy > >> > >> If you are given a choice, you believe you have acted freely. - Raymond > >> Teller (via Peter Watts) > >> > > > > > > > > -- > > Thanks, > > Michael Antonov > > > > > > -- > Thanks, > Michael Antonov >
Re: release of HBase 1.3.1?
All right, I cherry picked HBASE-17227 and the first RC is out. Thanks Andrew for the help pushing it! -Mikhail On Wed, Apr 5, 2017 at 12:47 PM, Mikhail Antonov wrote: > Thanks Andrew! > > So after open jiras has been re-targeted for 1.3.2 and looking at the > filter > `affectedVersion in (1.3.0) AND fixVersion = 1.3.2 AND status in (Open, > "Patch Available", Reopened, "In Progress")` > > there are only few issues that warrant discussion before RC0, I think. > > - HBASE-17513, where Thrift-1 security settings are easy to misconfigure. >Currently marked critical, I don't think it's release blocker. Opinions? > - HBASE-17227, a backport of HBASE-17206, a stability fix for FSHLog. > This one I think we should pull in. > > Everything else isn't important enough for an RC. > > Any opinions? Otherwise I'd cherry pick the latter one. > > -Mikhail > > > On Wed, Apr 5, 2017 at 11:20 AM, Andrew Purtell > wrote: > >> Branch 1.3 updated and tagged for RC0. >> >> remote: hbase git commit: Update POMs and CHANGES.txt for 1.3.1 RC0 >> To https://git-wip-us.apache.org/repos/asf/hbase.git >>fd297e2..3a2f3aa branch-1.3 -> branch-1.3 >> * [new tag] 1.3.1RC0 -> 1.3.1RC0 >> >> >> On Mon, Apr 3, 2017 at 10:35 PM, Mikhail Antonov >> wrote: >> >> > Hi, >> > >> > I've been planning to cut an RC for 1.3.1 for some time, apologize for >> the >> > delay here. I'm going to go over outstanding jiras tomorrow, >> > I think there are still few issues waiting for backports. >> > >> > Andrew - appreciate your offer! I have started preparations for 1.3.1 >> > release, but any help with triaging changes, API compatibility tests >> > and general release testing would definitely be helpful. >> > >> > Thanks! >> > -Mikhail >> > >> > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell < >> andrew.purt...@gmail.com> >> > wrote: >> > >> > > I'd be happy to RM 1.3.1 unless someone already has it waiting in the >> > > wings. >> > > >> > > >> > > > On Apr 3, 2017, at 5:43 PM, James Taylor >> > wrote: >> > > > >> > > > Hello, >> > > > We'd like to start supporting releases of Phoenix that work with the >> > > HBase >> > > > 1.3 branch, but there's a committed fix on which we rely >> (HBASE-17587) >> > > for >> > > > Phoenix to function correctly. Is there a time frame for an HBase >> 1.3.1 >> > > > release? >> > > > Thanks, >> > > > James >> > > >> > >> > >> > >> > -- >> > Thanks, >> > Michael Antonov >> > >> >> >> >> -- >> Best regards, >> >>- Andy >> >> If you are given a choice, you believe you have acted freely. - Raymond >> Teller (via Peter Watts) >> > > > > -- > Thanks, > Michael Antonov > -- Thanks, Michael Antonov
[jira] [Created] (HBASE-17884) Backport HBASE-16217 to branch-1
Gary Helmling created HBASE-17884: - Summary: Backport HBASE-16217 to branch-1 Key: HBASE-17884 URL: https://issues.apache.org/jira/browse/HBASE-17884 Project: HBase Issue Type: Sub-task Reporter: Gary Helmling The change to add calling user to ObserverContext in HBASE-16217 should also be applied to branch-1 to avoid use of UserGroupInformation.doAs() for access control checks. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[VOTE] First release candidate for HBase 1.3.1 (RC0) is available
Hello everyone, I'm pleased to announce the first release candidate for Apache HBase 1.3.1 is available to download and testing. Artifacts are available here: https://dist.apache.org/repos/dist/dev/hbase/1.3.1RC0/ Maven artifacts are available in the staging repository: https://repository.apache.org/content/repositories/orgapachehbase-1165 All artifacts are signed with my code signing key 35A4ABE2, which is also in the project KEYS file at http://www.apache.org/dist/hbase/KEYS these artifacts correspond to commit hash 2a425fc420a3de98eedd2ee7b703bb2873127f0e tagged as 1.3.1RC0. HBase 1.3.1 is the first maintenance release in the HBase 1.3.z release line, continuing on the theme of bringing a stable, reliable database to the Hadoop and NoSQL communities. This release includes 67 resolved issues since the initial 1.3.0 release that was 3 month ago. The full list of issues addressed is available at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310753&version=12335746 and also in the CHANGES.txt file in the root directory of the source tarball. Please take a few minutes to verify the release and vote on releasing it: [ ] +1 Release this package as Apache HBase 1.3.1 [ ] +0 no opinion [ ] -1 Do not release this package because... This Vote will run for one week and close Wed Apr 12, 2017 22:00 PST. Thanks ! (also separate thanks to Andrew Purtell for the help to get the RC out) -Mikhail Antonov
Re: release of HBase 1.3.1?
Thanks Andrew! So after open jiras has been re-targeted for 1.3.2 and looking at the filter `affectedVersion in (1.3.0) AND fixVersion = 1.3.2 AND status in (Open, "Patch Available", Reopened, "In Progress")` there are only few issues that warrant discussion before RC0, I think. - HBASE-17513, where Thrift-1 security settings are easy to misconfigure. Currently marked critical, I don't think it's release blocker. Opinions? - HBASE-17227, a backport of HBASE-17206, a stability fix for FSHLog. This one I think we should pull in. Everything else isn't important enough for an RC. Any opinions? Otherwise I'd cherry pick the latter one. -Mikhail On Wed, Apr 5, 2017 at 11:20 AM, Andrew Purtell wrote: > Branch 1.3 updated and tagged for RC0. > > remote: hbase git commit: Update POMs and CHANGES.txt for 1.3.1 RC0 > To https://git-wip-us.apache.org/repos/asf/hbase.git >fd297e2..3a2f3aa branch-1.3 -> branch-1.3 > * [new tag] 1.3.1RC0 -> 1.3.1RC0 > > > On Mon, Apr 3, 2017 at 10:35 PM, Mikhail Antonov > wrote: > > > Hi, > > > > I've been planning to cut an RC for 1.3.1 for some time, apologize for > the > > delay here. I'm going to go over outstanding jiras tomorrow, > > I think there are still few issues waiting for backports. > > > > Andrew - appreciate your offer! I have started preparations for 1.3.1 > > release, but any help with triaging changes, API compatibility tests > > and general release testing would definitely be helpful. > > > > Thanks! > > -Mikhail > > > > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell > > > wrote: > > > > > I'd be happy to RM 1.3.1 unless someone already has it waiting in the > > > wings. > > > > > > > > > > On Apr 3, 2017, at 5:43 PM, James Taylor > > wrote: > > > > > > > > Hello, > > > > We'd like to start supporting releases of Phoenix that work with the > > > HBase > > > > 1.3 branch, but there's a committed fix on which we rely > (HBASE-17587) > > > for > > > > Phoenix to function correctly. Is there a time frame for an HBase > 1.3.1 > > > > release? > > > > Thanks, > > > > James > > > > > > > > > > > -- > > Thanks, > > Michael Antonov > > > > > > -- > Best regards, > >- Andy > > If you are given a choice, you believe you have acted freely. - Raymond > Teller (via Peter Watts) > -- Thanks, Michael Antonov
[jira] [Resolved] (HBASE-17641) Provide shaded hbase-testing-util
[ https://issues.apache.org/jira/browse/HBASE-17641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey resolved HBASE-17641. - Resolution: Duplicate Fix Version/s: (was: 1.4.0) (was: 2.0.0) > Provide shaded hbase-testing-util > -- > > Key: HBASE-17641 > URL: https://issues.apache.org/jira/browse/HBASE-17641 > Project: HBase > Issue Type: New Feature > Components: Client, test >Reporter: Attila Sasvari >Priority: Critical > > Besides shaded hbase client, server, protocol, it would be great to have a > shaded hbase-testing-util too. For example, that could be used in integration > tests of other Hadoop components. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
Re: release of HBase 1.3.1?
Branch 1.3 updated and tagged for RC0. remote: hbase git commit: Update POMs and CHANGES.txt for 1.3.1 RC0 To https://git-wip-us.apache.org/repos/asf/hbase.git fd297e2..3a2f3aa branch-1.3 -> branch-1.3 * [new tag] 1.3.1RC0 -> 1.3.1RC0 On Mon, Apr 3, 2017 at 10:35 PM, Mikhail Antonov wrote: > Hi, > > I've been planning to cut an RC for 1.3.1 for some time, apologize for the > delay here. I'm going to go over outstanding jiras tomorrow, > I think there are still few issues waiting for backports. > > Andrew - appreciate your offer! I have started preparations for 1.3.1 > release, but any help with triaging changes, API compatibility tests > and general release testing would definitely be helpful. > > Thanks! > -Mikhail > > On Mon, Apr 3, 2017 at 9:52 PM, Andrew Purtell > wrote: > > > I'd be happy to RM 1.3.1 unless someone already has it waiting in the > > wings. > > > > > > > On Apr 3, 2017, at 5:43 PM, James Taylor > wrote: > > > > > > Hello, > > > We'd like to start supporting releases of Phoenix that work with the > > HBase > > > 1.3 branch, but there's a committed fix on which we rely (HBASE-17587) > > for > > > Phoenix to function correctly. Is there a time frame for an HBase 1.3.1 > > > release? > > > Thanks, > > > James > > > > > > -- > Thanks, > Michael Antonov > -- Best regards, - Andy If you are given a choice, you believe you have acted freely. - Raymond Teller (via Peter Watts)
[jira] [Created] (HBASE-17883) release 1.4.0
Sean Busbey created HBASE-17883: --- Summary: release 1.4.0 Key: HBASE-17883 URL: https://issues.apache.org/jira/browse/HBASE-17883 Project: HBase Issue Type: Task Components: community Affects Versions: 1.4.0 Reporter: Sean Busbey Priority: Critical Fix For: 1.4.0 Let's start working through doing the needful; it's been almost 3 months sine 1.3.0. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17882) Why do the WalEdit implement the Writable interface
Chia-Ping Tsai created HBASE-17882: -- Summary: Why do the WalEdit implement the Writable interface Key: HBASE-17882 URL: https://issues.apache.org/jira/browse/HBASE-17882 Project: HBase Issue Type: Brainstorming Reporter: Chia-Ping Tsai Priority: Minor Do we have any use cases? (serialize/deserialize the WalEdit between mapper and reducer?) If not, we should make WalEdit not implement the Writable interface. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17881) Remove the ByteBufferCellImpl
Chia-Ping Tsai created HBASE-17881: -- Summary: Remove the ByteBufferCellImpl Key: HBASE-17881 URL: https://issues.apache.org/jira/browse/HBASE-17881 Project: HBase Issue Type: Sub-task Components: test Affects Versions: 2.0.0 Reporter: Chia-Ping Tsai Assignee: Chia-Ping Tsai Priority: Minor Fix For: 2.0.0 We should substitute ByteBufferKeyValue for ByteBufferCellImpl -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (HBASE-17880) Avoid NPE in snapshot.jsp when accessing without any request parameter
[ https://issues.apache.org/jira/browse/HBASE-17880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Abhishek Kumar resolved HBASE-17880. Resolution: Duplicate Closing it as duplicate of HBASE-17879, raised it twice mistakenly. > Avoid NPE in snapshot.jsp when accessing without any request parameter > -- > > Key: HBASE-17880 > URL: https://issues.apache.org/jira/browse/HBASE-17880 > Project: HBase > Issue Type: Bug > Components: UI >Reporter: Abhishek Kumar >Priority: Trivial > > When accessing snapshot jsp with below url inadvertently NPE comes in UI: > Requested URL: > http://:/snapshot.jsp? > Response: > java.lang.NullPointerException > at > org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) > at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) > at > org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17880) Avoid NPE in snapshot.jsp when accessing without any request parameter
Abhishek Kumar created HBASE-17880: -- Summary: Avoid NPE in snapshot.jsp when accessing without any request parameter Key: HBASE-17880 URL: https://issues.apache.org/jira/browse/HBASE-17880 Project: HBase Issue Type: Bug Components: UI Reporter: Abhishek Kumar Priority: Trivial When accessing snapshot jsp with below url inadvertently NPE comes in UI: Requested URL: http://:/snapshot.jsp? Response: java.lang.NullPointerException at org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (HBASE-17879) Avoid NPE in snapshot.jsp when accessing without any request parameter
Abhishek Kumar created HBASE-17879: -- Summary: Avoid NPE in snapshot.jsp when accessing without any request parameter Key: HBASE-17879 URL: https://issues.apache.org/jira/browse/HBASE-17879 Project: HBase Issue Type: Bug Components: UI Reporter: Abhishek Kumar Priority: Trivial When accessing snapshot jsp with below url inadvertently NPE comes in UI: Requested URL: http://:/snapshot.jsp? Response: java.lang.NullPointerException at org.apache.hadoop.hbase.generated.master.snapshot_jsp._jspService(snapshot_jsp.java:66) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:98) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (HBASE-15179) Cell/DBB end-to-end on the write-path
[ https://issues.apache.org/jira/browse/HBASE-15179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anoop Sam John resolved HBASE-15179. Resolution: Fixed Hadoop Flags: Reviewed > Cell/DBB end-to-end on the write-path > - > > Key: HBASE-15179 > URL: https://issues.apache.org/jira/browse/HBASE-15179 > Project: HBase > Issue Type: Umbrella > Components: regionserver >Reporter: Anoop Sam John >Assignee: Anoop Sam John > Fix For: 2.0.0 > > > Umbrella jira to make the HBase write path off heap E2E. We have to make sure > we have Cells flowing in entire write path. Starting from request received in > RPC layer, till the Cells get flushed out as HFiles, we have to keep the Cell > data off heap. > https://docs.google.com/document/d/1fj5P8JeutQ-Uadb29ChDscMuMaJqaMNRI86C4k5S1rQ/edit -- This message was sent by Atlassian JIRA (v6.3.15#6346)