[jira] [Resolved] (HBASE-24278) The Java doc for minFilesToCompact is wrong
[ https://issues.apache.org/jira/browse/HBASE-24278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Stack resolved HBASE-24278. --- Fix Version/s: 3.0.0 Hadoop Flags: Reviewed Resolution: Fixed Merged to master. Thank you for the fix [~Joseph295] > The Java doc for minFilesToCompact is wrong > --- > > Key: HBASE-24278 > URL: https://issues.apache.org/jira/browse/HBASE-24278 > Project: HBase > Issue Type: Improvement >Reporter: Junhong Xu >Assignee: Junhong Xu >Priority: Trivial > Fix For: 3.0.0 > > > It is the lower bound, not the upper bound on number of files to be included > in minor compactions, its name reveals that clearly. I think it is a slip of > the pen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-23933) Separate a hbase-balancer or hbase-assignment module
[ https://issues.apache.org/jira/browse/HBASE-23933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-23933. --- Resolution: Fixed Remove the hadoop-2.0 profile in hbase-balancer/pom.xml. Pushed to master. > Separate a hbase-balancer or hbase-assignment module > > > Key: HBASE-23933 > URL: https://issues.apache.org/jira/browse/HBASE-23933 > Project: HBase > Issue Type: Bug > Components: Balancer, build, Region Assignment >Reporter: Duo Zhang >Assignee: niuyulin >Priority: Major > Fix For: 3.0.0 > > > Open an issue here. After we merge hbase-rsgroup back to hbase-server, the > hbase-server even makes findbugs OOM... > So I think we should try to move out classes to make the module smaller... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (HBASE-23933) Separate a hbase-balancer or hbase-assignment module
[ https://issues.apache.org/jira/browse/HBASE-23933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang reopened HBASE-23933: --- For cleanup pom. > Separate a hbase-balancer or hbase-assignment module > > > Key: HBASE-23933 > URL: https://issues.apache.org/jira/browse/HBASE-23933 > Project: HBase > Issue Type: Bug > Components: Balancer, build, Region Assignment >Reporter: Duo Zhang >Assignee: niuyulin >Priority: Major > Fix For: 3.0.0 > > > Open an issue here. After we merge hbase-rsgroup back to hbase-server, the > hbase-server even makes findbugs OOM... > So I think we should try to move out classes to make the module smaller... -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24249) Move code in FSHDFSUtils to FSUtils and mark related classes as final
[ https://issues.apache.org/jira/browse/HBASE-24249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24249. --- Fix Version/s: 2.3.0 3.0.0 Hadoop Flags: Reviewed Resolution: Fixed Pushed to branch-2.3+. Thanks [~stack] for reviewing. > Move code in FSHDFSUtils to FSUtils and mark related classes as final > - > > Key: HBASE-24249 > URL: https://issues.apache.org/jira/browse/HBASE-24249 > Project: HBase > Issue Type: Task > Components: Filesystem Integration >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0, 2.3.0 > > > It is a bit strange that a 'util' class can be instantiated. > I think the motivation is to provide multiple recoverFileLease implementation > based on different filesystem implementation. But until now, there is still > only one implementation for HDFS in HBase, and all the related classes are > marked as IA.Private so we do not expect user to extend the class. > Let's just move the code in FSHDFSUtils to FSUtils directly and make FSUtils > a true 'util' class. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24169) Drop hadoop 2 support for hbase 3.x
[ https://issues.apache.org/jira/browse/HBASE-24169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24169. --- Resolution: Fixed > Drop hadoop 2 support for hbase 3.x > --- > > Key: HBASE-24169 > URL: https://issues.apache.org/jira/browse/HBASE-24169 > Project: HBase > Issue Type: Umbrella > Components: hadoop2, hadoop3, pom >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Blocker > Fix For: 3.0.0 > > > As discussed several times on mailing list, I think it is time to do this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24228) Merge the code in hbase-hadoop2-compat module to hbase-hadoop-compat
[ https://issues.apache.org/jira/browse/HBASE-24228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Duo Zhang resolved HBASE-24228. --- Hadoop Flags: Reviewed Resolution: Fixed Pushed to master. Thanks [~stack] for reviewing. > Merge the code in hbase-hadoop2-compat module to hbase-hadoop-compat > > > Key: HBASE-24228 > URL: https://issues.apache.org/jira/browse/HBASE-24228 > Project: HBase > Issue Type: Sub-task > Components: hadoop2, hadoop3, pom >Reporter: Duo Zhang >Assignee: Duo Zhang >Priority: Major > Fix For: 3.0.0 > > > As now we only depend on hadoop3 and the compatible issues are mostly > resolved by reflection, no need to maintain a hadoop2-compat module any more. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24280) TestSecureRESTServer started failing in nightlies for Hadoop3
Josh Elser created HBASE-24280:
--
Summary: TestSecureRESTServer started failing in nightlies for
Hadoop3
Key: HBASE-24280
URL: https://issues.apache.org/jira/browse/HBASE-24280
Project: HBase
Issue Type: Sub-task
Reporter: Josh Elser
Assignee: Josh Elser
Fix For: 2.3.0
[~ndimiduk] pointed out that, after this change went in, TestSecureRESTServer
started failing with Hadoop3 on branch-2.3
https://builds.apache.org/job/HBase%20Nightly/job/branch-2.3/56/
Of course, I ran this with 1.8.0_241 and Maven 3.6.33 and it passed :) {{mvn
clean package -Dtest=TestSecureRESTServer -Dhadoop.profile=3.0
-DfailIfNoTests=false}}
FYI [~stoty] in case you can repro a failure and want to dig in. Feel free to
re-assign.
It looks like we didn't have a nightly run of branch-2.2 due to docker
container build issues. Will be interesting to see if it fails there. It did
not fail the master nightly.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (HBASE-24247) Failed multi-merge because two regions not adjacent (legitimately).
[
https://issues.apache.org/jira/browse/HBASE-24247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Stack resolved HBASE-24247.
---
Hadoop Flags: Reviewed
Assignee: Michael Stack
Resolution: Fixed
Pushed to branch-2.3+. Thanks for review [~janh]
> Failed multi-merge because two regions not adjacent (legitimately).
> ---
>
> Key: HBASE-24247
> URL: https://issues.apache.org/jira/browse/HBASE-24247
> Project: HBase
> Issue Type: Bug
>Reporter: Michael Stack
>Assignee: Michael Stack
>Priority: Major
> Fix For: 3.0.0, 2.3.0
>
>
> Below is a multi-merge created by FixMeta provoked by 'hbck2 fixMeta'. The
> merge is legitimate in that indeed all Regions overlap. The merge is cutoff
> off at the current max of 10 Regions-at-a-time (which is another issue). The
> merge fails though because two Regions in the Set of Regions to merge are not
> adjacent when we do our pre-flight check. We could 'force' the merge but
> better if the 'check' is improved.
> {code}
> 2020-04-22 22:04:57,048 WARN
> org.apache.hadoop.hbase.master.assignment.MergeTableRegionsProcedure: Unable
> to merge non-adjacent or non-overlapping regions
> 50b9f911320f64d0ab54a7606a6cdb77, 15877a8df3987176b12a2e2c4712c95f when
> force=false
> 2020-04-22 22:04:57,048 WARN org.apache.hadoop.hbase.master.MetaFixer: Failed
> overlap fix of [{ENCODED => 6f880442573f4ca0c2536ce2352e4883, NAME =>
> 'X,,1567882650838.6f880442573f4ca0c2536ce2352e4883.', STARTKEY => '', ENDKEY
> =>
> '\x01\x02\x05\x01\x03\x02\x01\x01\x01\x01\x02201908310200\x00\x00\x048.1-11B117\x00\x00\x00\x00\x00\x00iPad4,1\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'},
> {ENCODED => 98af7f02916e014c07ac099724c7ffaf, NAME =>
> 'X,\x01\x01\x05\x01\x01,1558718898305.98af7f02916e014c07ac099724c7ffaf.',
> STARTKEY => '\x01\x01\x05\x01\x01', ENDKEY => '\x01\x01\x05\x01\x02'},
> {ENCODED => d1a0b8772432c1148cdf7a8fad8e770c, NAME =>
> 'X,\x01\x01\x05\x01\x02,1558718898305.d1a0b8772432c1148cdf7a8fad8e770c.',
> STARTKEY => '\x01\x01\x05\x01\x02', ENDKEY => '\x01\x01\x05\x01\x03'},
> {ENCODED => 99738e58d057dafb861116a3efcb0285, NAME =>
> 'X,\x01\x01\x05\x01\x03,1558718898305.99738e58d057dafb861116a3efcb0285.',
> STARTKEY => '\x01\x01\x05\x01\x03', ENDKEY => '\x01\x01\x05\x02\x01'},
> {ENCODED => 50b9f911320f64d0ab54a7606a6cdb77, NAME =>
> 'X,\x01\x01\x05\x02\x01,1558718898305.50b9f911320f64d0ab54a7606a6cdb77.',
> STARTKEY => '\x01\x01\x05\x02\x01', ENDKEY => '\x01\x01\x05\x02\x02'},
> {ENCODED => 15877a8df3987176b12a2e2c4712c95f, NAME =>
> 'X,\x01\x01\x05\x02\x03,1558718898305.15877a8df3987176b12a2e2c4712c95f.',
> STARTKEY => '\x01\x01\x05\x02\x03', ENDKEY => '\x01\x01\x06\x01\x01'},
> {ENCODED => d5f0929fffbaec29ca99d4d0cd90c491, NAME =>
> 'X,\x01\x01\x06\x01\x01,1558718898305.d5f0929fffbaec29ca99d4d0cd90c491.',
> STARTKEY => '\x01\x01\x06\x01\x01', ENDKEY => '\x01\x01\x06\x01\x02'},
> {ENCODED => 8d72ed0d1d635511a323abef7026ec4f, NAME =>
> 'X,\x01\x01\x06\x01\x03,1558718898305.8d72ed0d1d635511a323abef7026ec4f.',
> STARTKEY => '\x01\x01\x06\x01\x03', ENDKEY => '\x01\x01\x06\x02\x01'},
> {ENCODED => 977f5a0e2f77a91531000d358f9a8eba, NAME =>
> 'X,\x01\x01\x06\x02\x01,1558718898305.977f5a0e2f77a91531000d358f9a8eba.',
> STARTKEY => '\x01\x01\x06\x02\x01', ENDKEY => '\x01\x01\x06\x02\x02'},
> {ENCODED => 21cdc09d13ae1ecefc6531786229f2ec, NAME =>
> 'X,\x01\x01\x06\x02\x03,1558718898305.21cdc09d13ae1ecefc6531786229f2ec.',
> STARTKEY => '\x01\x01\x06\x02\x03', ENDKEY => '\x01\x01\x07\x01\x01'}]
> org.apache.hadoop.hbase.exceptions.MergeRegionException: Unable to merge
> non-adjacent or non-overlapping regions 50b9f911320f64d0ab54a7606a6cdb77,
> 15877a8df3987176b12a2e2c4712c95f when force=false
> at
> org.apache.hadoop.hbase.master.assignment.MergeTableRegionsProcedure.checkRegionsToMerge(MergeTableRegionsProcedure.java:140)
> at
> org.apache.hadoop.hbase.master.assignment.MergeTableRegionsProcedure.(MergeTableRegionsProcedure.java:105)
> at org.apache.hadoop.hbase.master.HMaster$2.run(HMaster.java:1961)
> at
> org.apache.hadoop.hbase.master.procedure.MasterProcedureUtil.submitProcedure(MasterProcedureUtil.java:134)
> at
> org.apache.hadoop.hbase.master.HMaster.mergeRegions(HMaster.java:1955)
> at
> org.apache.hadoop.hbase.master.MetaFixer.fixOverlaps(MetaFixer.java:221)
> at
[jira] [Resolved] (HBASE-24276) hbase spark connector doesn't support writing to table not in default namespace
[
https://issues.apache.org/jira/browse/HBASE-24276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Balazs Meszaros resolved HBASE-24276.
-
Fix Version/s: connector-1.0.1
Resolution: Fixed
> hbase spark connector doesn't support writing to table not in default
> namespace
> ---
>
> Key: HBASE-24276
> URL: https://issues.apache.org/jira/browse/HBASE-24276
> Project: HBase
> Issue Type: Bug
> Components: hbase-connectors, spark
>Affects Versions: connector-1.0.0
> Environment: - HBase 2.2.4
> - Hadoop 2.10.0
> - Spark 2.4.5
>Reporter: Naitree Zhu
>Priority: Major
> Fix For: connector-1.0.1
>
>
> Defining the following table catalog:
> {code:java}
> val catalog = """{
> |"table": {"namespace": "ns1", "name": "test1"},
> |"rowkey": "id",
> |"columns": {
> |"id": {"cf": "rowkey", "col": "id", "type": "string"},
> |"x": {"cf": "d", "col": "xxx", "type": "int"}
> |}
> |}""".stripMargin
> {code}
> Try to write some test data to {{ns1:test1}} table using spark:
> {code:java}
> val df = Seq(("abc", 1), ("def", 2)).toDF("id", "x")
> df.write.options(Map(HBaseTableCatalog.tableCatalog -> catalog,
> "hbase.spark.use.hbasecontext" -> "false", HBaseTableCatalog.newTable->
> "5")).format("org.apache.hadoop.hbase.spark").save()
> {code}
> After executing the code above, I found out that the test data was written to
> {{default:test1}}, rather than {{ns1:test1}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
The hbase-thirdparty 3.3.0RC1 vote is up. The only difference is the update in RELEASENOTE.md. For reference see HBASE-24279. Thanks, Peter On Tue, Apr 28, 2020 at 7:06 PM Peter Somogyi wrote: > I'm rolling a new RC now with changing the RELEASENOTES only. > > On Tue, Apr 28, 2020 at 7:05 PM Sean Busbey wrote: > >> I'm +1 as is. >> >> If we're going to fix the release notes I'd rather we stage RC1 with that >> change in place and then vote again. just set a small voting period (like >> until a couple hours after we get 3 binding +1s) >> >> On Sat, Apr 25, 2020 at 9:58 AM Peter Somogyi >> wrote: >> >> > Please vote on this Apache hbase thirdparty release candidate, >> > hbase-thirdparty-3.3.0RC0 >> > >> > The VOTE will remain open for at least 72 hours. >> > >> > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 >> > [ ] -1 Do not release this package because ... >> > >> > The tag to be voted on is 3.3.0RC0: >> > >> > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 >> > >> > The release files, including signatures, digests, as well as CHANGES.md >> > and RELEASENOTES.md included in this RC can be found at: >> > >> > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ >> > >> > Maven artifacts are available in a staging repository at: >> > >> > >> https://repository.apache.org/content/repositories/orgapachehbase-1388/ >> > >> > Artifacts were signed with the psomo...@apache.org key which can be >> found >> > in: >> > >> > https://dist.apache.org/repos/dist/release/hbase/KEYS >> > >> > To learn more about apache hbase thirdparty, please see >> > http://hbase.apache.org/ >> > >> > Thanks, >> > Your HBase Release Manager >> > >> >
[VOTE] Please vote on the second hbase-thirdparty-3.3.0 release candidate
Please vote on this Apache hbase thirdparty release candidate, hbase-thirdparty-3.3.0RC1 The second release candidate only differs in the RELEASENOTES.md update compared to RC0. The VOTE will remain open until there are at least the required voting majority [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 [ ] -1 Do not release this package because ... The tag to be voted on is 3.3.0RC1: https://github.com/apache/hbase-thirdparty/tree/3.3.0RC1 The release files, including signatures, digests, as well as CHANGES.md and RELEASENOTES.md included in this RC can be found at: https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC1/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1389/ Artifacts were signed with the psomo...@apache.org key which can be found in: https://dist.apache.org/repos/dist/release/hbase/KEYS To learn more about apache hbase thirdparty, please see http://hbase.apache.org/ Thanks, Your HBase Release Manager
[jira] [Resolved] (HBASE-24279) Fix thirdparty-3.2.0 release notes
[ https://issues.apache.org/jira/browse/HBASE-24279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Somogyi resolved HBASE-24279. --- Resolution: Fixed Fixed release notes for hbase-thirdparty 3.2.0 and filled RN for this ticket mentioning the incorrect gson RN. > Fix thirdparty-3.2.0 release notes > -- > > Key: HBASE-24279 > URL: https://issues.apache.org/jira/browse/HBASE-24279 > Project: HBase > Issue Type: Bug > Components: thirdparty >Affects Versions: thirdparty-3.2.0 >Reporter: Peter Somogyi >Assignee: Peter Somogyi >Priority: Trivial > Fix For: thirdparty-3.3.0 > > > The RELEASENOTES for hbase-thirdparty-3.2.0 contains gson upgrade which was > reverted before the release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
I'm rolling a new RC now with changing the RELEASENOTES only. On Tue, Apr 28, 2020 at 7:05 PM Sean Busbey wrote: > I'm +1 as is. > > If we're going to fix the release notes I'd rather we stage RC1 with that > change in place and then vote again. just set a small voting period (like > until a couple hours after we get 3 binding +1s) > > On Sat, Apr 25, 2020 at 9:58 AM Peter Somogyi wrote: > > > Please vote on this Apache hbase thirdparty release candidate, > > hbase-thirdparty-3.3.0RC0 > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > > [ ] -1 Do not release this package because ... > > > > The tag to be voted on is 3.3.0RC0: > > > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > > > The release files, including signatures, digests, as well as CHANGES.md > > and RELEASENOTES.md included in this RC can be found at: > > > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > > > Maven artifacts are available in a staging repository at: > > > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > > > Artifacts were signed with the psomo...@apache.org key which can be > found > > in: > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > To learn more about apache hbase thirdparty, please see > > http://hbase.apache.org/ > > > > Thanks, > > Your HBase Release Manager > > >
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
I'm +1 as is. If we're going to fix the release notes I'd rather we stage RC1 with that change in place and then vote again. just set a small voting period (like until a couple hours after we get 3 binding +1s) On Sat, Apr 25, 2020 at 9:58 AM Peter Somogyi wrote: > Please vote on this Apache hbase thirdparty release candidate, > hbase-thirdparty-3.3.0RC0 > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 3.3.0RC0: > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > The release files, including signatures, digests, as well as CHANGES.md > and RELEASENOTES.md included in this RC can be found at: > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > Artifacts were signed with the psomo...@apache.org key which can be found > in: > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > To learn more about apache hbase thirdparty, please see > http://hbase.apache.org/ > > Thanks, > Your HBase Release Manager >
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
Had a brief tangent with Peter in backchat about branch-2.2 and how it's not on current thirdparty releases, but, now that I understand where we are, I'm good with rc0. * Sigs/xsums good * rat-check fine * running dev-tests w/o issue against branch-2 (since Duo built master) * tried to build phoenix too, but ran into other issues (see aforementioned tangent) I'm OK with this as it is, but am also OK if we fix releasenotes. IMO, we could just fix releasenotes.md when doing copy from dist/dev to dist/release (don't need new jars -- they aren't changing). +1 (binding) On 4/25/20 10:58 AM, Peter Somogyi wrote: Please vote on this Apache hbase thirdparty release candidate, hbase-thirdparty-3.3.0RC0 The VOTE will remain open for at least 72 hours. [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 [ ] -1 Do not release this package because ... The tag to be voted on is 3.3.0RC0: https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 The release files, including signatures, digests, as well as CHANGES.md and RELEASENOTES.md included in this RC can be found at: https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ Maven artifacts are available in a staging repository at: https://repository.apache.org/content/repositories/orgapachehbase-1388/ Artifacts were signed with the psomo...@apache.org key which can be found in: https://dist.apache.org/repos/dist/release/hbase/KEYS To learn more about apache hbase thirdparty, please see http://hbase.apache.org/ Thanks, Your HBase Release Manager
[jira] [Created] (HBASE-24279) Fix thirdparty-3.2.0 release notes
Peter Somogyi created HBASE-24279: - Summary: Fix thirdparty-3.2.0 release notes Key: HBASE-24279 URL: https://issues.apache.org/jira/browse/HBASE-24279 Project: HBase Issue Type: Bug Components: thirdparty Affects Versions: thirdparty-3.2.0 Reporter: Peter Somogyi Assignee: Peter Somogyi Fix For: thirdparty-3.3.0 The RELEASENOTES for hbase-thirdparty-3.2.0 contains gson upgrade which was reverted before the release. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24278) The Java doc for minFilesToCompact is wrong
Junhong Xu created HBASE-24278: -- Summary: The Java doc for minFilesToCompact is wrong Key: HBASE-24278 URL: https://issues.apache.org/jira/browse/HBASE-24278 Project: HBase Issue Type: Improvement Reporter: Junhong Xu Assignee: Junhong Xu It is the lower bound, not the upper bound on number of files to be included in minor compactions, its name reveals that clearly. I think it is a slip of the pen -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24277) TestZooKeeper is flaky
Duo Zhang created HBASE-24277: - Summary: TestZooKeeper is flaky Key: HBASE-24277 URL: https://issues.apache.org/jira/browse/HBASE-24277 Project: HBase Issue Type: Bug Components: test, Zookeeper Reporter: Duo Zhang After checking the code, the problem is that, when creating table during master shutdown, it is easy to hit MasterStoppedException or other strange exceptions which make the creation fail. In general I think this should be a test issue, need to learn why we do not have the problem on branch-2.x. -- This message was sent by Atlassian Jira (v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
I ran OWASP dependency-check and found no known CVEs. Nit: The NOTICE.txt states "Copyright 2018". Should it update to "Copyright 2018-2020"? On Tue, Apr 28, 2020 at 8:03 AM 张铎(Duo Zhang) wrote: > Just change the releasenote.md and make a RC1? We can not republish 3.2.0 > but since the release note for 3.3.0 contains the release note of 3.2.0, we > can fix it. > > Peter Somogyi 于2020年4月28日周二 下午6:04写道： > > > What is your suggestion to fix the release notes for 3.2.0? That release > > was already shipped and unfortunately this issue was not noticed on its > > vote process. > > > > On Tue, Apr 28, 2020 at 9:58 AM 张铎(Duo Zhang) > > wrote: > > > > > The release note of the hbase-thirdparty-3.2.0 section has a mistake > > > > > > * [HBASE-23718](https://issues.apache.org/jira/browse/HBASE-23718) | > > > *Major* | **[hbase-thirdparty] Update libs; pb from 3.9 to 3.11, > > > etc.** > > > > > > gson: 2.8.5 =\> 2.8.6 > > > guava: 28.1-jre =\> 28.2-jre > > > error\_prone: 2.3.3 =\> 2.3.4 > > > netty: 4.1.42.Final =\> 4.1.44.Final > > > protobuf: 3.9.2 =\> 3.11.1 > > > maven-assembly-plugin: 3.1.1 =\> 3.2.0 > > > > > > > > > Actually we reverted gson back to 2.8.5, and now the release note on > jira > > > is > > > > > > guava: 28.1-jre => 28.2-jre > > > error_prone: 2.3.3 => 2.3.4 > > > netty: 4.1.42.Final => 4.1.44.Final > > > protobuf: 3.9.2 => 3.11.1 > > > maven-assembly-plugin: 3.1.1 => 3.2.0 > > > > > > > > > Peter Somogyi 于2020年4月25日周六 下午10:58写道： > > > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > > hbase-thirdparty-3.3.0RC0 > > > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > > > > [ ] -1 Do not release this package because ... > > > > > > > > The tag to be voted on is 3.3.0RC0: > > > > > > > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > > > > > > > The release files, including signatures, digests, as well as > CHANGES.md > > > > and RELEASENOTES.md included in this RC can be found at: > > > > > > > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > > > > > > > Artifacts were signed with the psomo...@apache.org key which can be > > > found > > > > in: > > > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > > > > > To learn more about apache hbase thirdparty, please see > > > > http://hbase.apache.org/ > > > > > > > > Thanks, > > > > Your HBase Release Manager > > > > > > > > > >
[jira] [Resolved] (HBASE-24272) Backport "Implement proxyuser/doAs mechanism for hbase-http" to 2.1.x
[ https://issues.apache.org/jira/browse/HBASE-24272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Elser resolved HBASE-24272. Resolution: Won't Fix Crap. Thanks, Peter. Sorry for the time sink, Istvan. > Backport "Implement proxyuser/doAs mechanism for hbase-http" to 2.1.x > - > > Key: HBASE-24272 > URL: https://issues.apache.org/jira/browse/HBASE-24272 > Project: HBase > Issue Type: Sub-task >Reporter: Josh Elser >Assignee: Istvan Toth >Priority: Major > Fix For: 2.1.10 > > > Could you make the modification to your change for branch-2.1 please, > [~stoty]? > If not, let me know and I'll dig in and fix it. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (HBASE-24275) shell命令扫描无法使用
[
https://issues.apache.org/jira/browse/HBASE-24275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Elser resolved HBASE-24275.
Resolution: Invalid
Sorry for not being competent enough to reply in Chinese.
It sounds like you need some help using the HBase shell and converting String
and byte[]. We reserve Jira for concrete changes to HBase. Your question is
something best served using the user mailing lists. If you didn't know, there
is also a user...@hbase.apache.org which is designated for communication in
Chinese. Please ask your for assistance there. Thank you.
https://lists.apache.org/list.html?user...@hbase.apache.org
> shell命令扫描无法使用
> -
>
> Key: HBASE-24275
> URL: https://issues.apache.org/jira/browse/HBASE-24275
> Project: HBase
> Issue Type: Bug
> Components: shell
>Affects Versions: 1.2.1
> Environment: hbase(main):001:0> scan
> 'bill_2_20200216',\{LIMIT=>1,COLUMN=>['info:content:(org.apache.hadoop.hbase.util.Bytes).toString']}
> ROW COLUMN+CELL
> 18675205573_200A9992000603031_1 column=info:content,
> timestamp=1584028631493, value=\xE4\xB8\xBB\xE4\xBB\xBB\xEF\xBC\x8C\xE6\x82
> _021623344100823069
> \xA8\xE5\xA5\xBD\xE3\x80\x82\xE6\x82\xA8\xE6\x98\x8E\xE5\xA4\xA9\xEF\xBC\x882\xE6\x9C\x8817\xE6\
>
> x97\xA5\xE6\x98\x9F\xE6\x9C\x9F\xE4\xB8\x80\xEF\xBC\x89\xE4\xB8\x8A\xE5\x8D\x88\xE7\x9A\x84\xE8\
>
> xA1\x8C\xE7\xA8\x8B\xE5\xAE\x89\xE6\x8E\x92\xE5\xA6\x82\xE4\xB8\x8B\xEF\xBC\x9A\x0A9:30\xE6\x97\
>
> xB6\xEF\xBC\x8C\xE5\x9C\xA8\xE5\xB8\x82\xE5\x95\x86\xE5\x8A\xA1\xE5\xB1\x805\xE6\xA5\xBC\xE5\xA4
>
> \xA7\xE4\xBC\x9A\xE8\xAE\xAE\xE5\xAE\xA4\xEF\xBC\x8C\xE6\x94\xB6\xE5\x90\xAC\xE6\x94\xB6\xE7\x9C
>
> \x8B\xE7\x9C\x81\xE6\x8E\xA8\xE8\xBF\x9B\xE5\xA4\x96\xE8\xB4\xB8\xE4\xBC\x81\xE4\xB8\x9A\xE5\xA4
>
> \x8D\xE5\xB7\xA5\xE5\xA4\x8D\xE4\xBA\xA7\xE4\xBC\x9A\xE8\xAE\xAE\xE6\x9A\xA8\xE5\xA4\x96\xE8\xB4
>
> \xB8\xE5\xBD\xA2\xE5\x8A\xBF\xE7\xA0\x94\xE5\x88\xA4\xE4\xBC\x9A\xE3\x80\x82\x0A\xE8\xAF\xB7\xE6
>
> \x82\xA8\xE7\x9F\xA5\xE6\x82\x89\xE5\xB9\xB6\xE5\x8F\x82\xE5\x8A\xA0\xEF\xBC\x8C\xE8\xB0\xA2\xE8
>
> \xB0\xA2\xE3\x80\x82\xEF\xBC\x88\xE8\x81\x94\xE7\xB3\xBB\xE4\xBA\xBA\xEF\xBC\x9A\xE6\x9D\xA8\xE4
>
> \xBC\x9F\xE5\xBC\xBA\xEF\xBC\x8C\xE8\x81\x94\xE7\xB3\xBB\xE7\x94\xB5\xE8\xAF\x9D\xEF\xBC\x9A1831
> 8286014\xEF\xBC\x89
> 1 row(s) in 0.4480 seconds
> hbase(main):002:0> get
> 'bill_2_20200216','910010_13436291012_1_021617402200563234','info:content:toString'
> COLUMN CELL
> 0 row(s) in 0.0610 seconds
> hbase(main):003:0> get
> 'bill_2_20200216','18675205573_200A9992000603031_1_021623344100823069','info:content:toString'
> COLUMN CELL
> 0 row(s) in 0.0170 seconds
> hbase(main):004:0> get 'bill_2_20200216','
> 18675205573_200A9992000603031_1_021623344100823069','info:content:toString'
> COLUMN CELL
> info:content timestamp=1584028631493, value=主任，您好。您明天（2月17日星期一）上午的行
> 安排如下：
> 9:30时，在市商务局5楼大会议室，收听收看省推进外贸企业
> 工复产会议暨外贸形势研判会。
> 请您知悉并参加，谢谢。（联系人：杨
> ¼强，联系电话：18318286014）
>Reporter: lacsar
>Priority: Minor
>
> 在shell命令行查询字段值的时候想将byte转为string，用scan命令查询后没有效果，结果还是byte，但是get命令可以转为string
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
Just change the releasenote.md and make a RC1? We can not republish 3.2.0 but since the release note for 3.3.0 contains the release note of 3.2.0, we can fix it. Peter Somogyi 于2020年4月28日周二 下午6:04写道： > What is your suggestion to fix the release notes for 3.2.0? That release > was already shipped and unfortunately this issue was not noticed on its > vote process. > > On Tue, Apr 28, 2020 at 9:58 AM 张铎(Duo Zhang) > wrote: > > > The release note of the hbase-thirdparty-3.2.0 section has a mistake > > > > * [HBASE-23718](https://issues.apache.org/jira/browse/HBASE-23718) | > > *Major* | **[hbase-thirdparty] Update libs; pb from 3.9 to 3.11, > > etc.** > > > > gson: 2.8.5 =\> 2.8.6 > > guava: 28.1-jre =\> 28.2-jre > > error\_prone: 2.3.3 =\> 2.3.4 > > netty: 4.1.42.Final =\> 4.1.44.Final > > protobuf: 3.9.2 =\> 3.11.1 > > maven-assembly-plugin: 3.1.1 =\> 3.2.0 > > > > > > Actually we reverted gson back to 2.8.5, and now the release note on jira > > is > > > > guava: 28.1-jre => 28.2-jre > > error_prone: 2.3.3 => 2.3.4 > > netty: 4.1.42.Final => 4.1.44.Final > > protobuf: 3.9.2 => 3.11.1 > > maven-assembly-plugin: 3.1.1 => 3.2.0 > > > > > > Peter Somogyi 于2020年4月25日周六 下午10:58写道： > > > > > Please vote on this Apache hbase thirdparty release candidate, > > > hbase-thirdparty-3.3.0RC0 > > > > > > The VOTE will remain open for at least 72 hours. > > > > > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > > > [ ] -1 Do not release this package because ... > > > > > > The tag to be voted on is 3.3.0RC0: > > > > > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > > > > > The release files, including signatures, digests, as well as CHANGES.md > > > and RELEASENOTES.md included in this RC can be found at: > > > > > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > > > > > Maven artifacts are available in a staging repository at: > > > > > > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > > > > > Artifacts were signed with the psomo...@apache.org key which can be > > found > > > in: > > > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > > > To learn more about apache hbase thirdparty, please see > > > http://hbase.apache.org/ > > > > > > Thanks, > > > Your HBase Release Manager > > > > > >
[jira] [Created] (HBASE-24276) hbase spark connector doesn't support writing to table not in default namespace
Naitree Zhu created HBASE-24276:
---
Summary: hbase spark connector doesn't support writing to table
not in default namespace
Key: HBASE-24276
URL: https://issues.apache.org/jira/browse/HBASE-24276
Project: HBase
Issue Type: Bug
Components: hbase-connectors, spark
Affects Versions: connector-1.0.0
Environment: - HBase 2.2.4
- Hadoop 2.10.0
- Spark 2.4.5
Reporter: Naitree Zhu
Defining the following table catalog:
{code:java}
val catalog = """{
|"table": {"namespace": "ns1", "name": "test1"},
|"rowkey": "id",
|"columns": {
|"id": {"cf": "rowkey", "col": "id", "type": "string"},
|"x": {"cf": "d", "col": "xxx", "type": "int"}
|}
|}""".stripMargin
{code}
Try to write some test data to {{ns1:test1}} table using spark:
{code:java}
val df = Seq(("abc", 1), ("def", 2)).toDF("id", "x")
df.write.options(Map(HBaseTableCatalog.tableCatalog -> catalog,
"hbase.spark.use.hbasecontext" -> "false", HBaseTableCatalog.newTable->
"5")).format("org.apache.hadoop.hbase.spark").save()
{code}
After executing the code above, I found out that the test data was written to
{{default:test1}}, rather than {{ns1:test1}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
What is your suggestion to fix the release notes for 3.2.0? That release was already shipped and unfortunately this issue was not noticed on its vote process. On Tue, Apr 28, 2020 at 9:58 AM 张铎(Duo Zhang) wrote: > The release note of the hbase-thirdparty-3.2.0 section has a mistake > > * [HBASE-23718](https://issues.apache.org/jira/browse/HBASE-23718) | > *Major* | **[hbase-thirdparty] Update libs; pb from 3.9 to 3.11, > etc.** > > gson: 2.8.5 =\> 2.8.6 > guava: 28.1-jre =\> 28.2-jre > error\_prone: 2.3.3 =\> 2.3.4 > netty: 4.1.42.Final =\> 4.1.44.Final > protobuf: 3.9.2 =\> 3.11.1 > maven-assembly-plugin: 3.1.1 =\> 3.2.0 > > > Actually we reverted gson back to 2.8.5, and now the release note on jira > is > > guava: 28.1-jre => 28.2-jre > error_prone: 2.3.3 => 2.3.4 > netty: 4.1.42.Final => 4.1.44.Final > protobuf: 3.9.2 => 3.11.1 > maven-assembly-plugin: 3.1.1 => 3.2.0 > > > Peter Somogyi 于2020年4月25日周六 下午10:58写道： > > > Please vote on this Apache hbase thirdparty release candidate, > > hbase-thirdparty-3.3.0RC0 > > > > The VOTE will remain open for at least 72 hours. > > > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > > [ ] -1 Do not release this package because ... > > > > The tag to be voted on is 3.3.0RC0: > > > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > > > The release files, including signatures, digests, as well as CHANGES.md > > and RELEASENOTES.md included in this RC can be found at: > > > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > > > Maven artifacts are available in a staging repository at: > > > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > > > Artifacts were signed with the psomo...@apache.org key which can be > found > > in: > > > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > > > To learn more about apache hbase thirdparty, please see > > http://hbase.apache.org/ > > > > Thanks, > > Your HBase Release Manager > > >
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
For other part it is OK. Built hbase master with hbase-thirdparty-3.3.0, passed. 张铎(Duo Zhang) 于2020年4月28日周二 下午3:58写道： > The release note of the hbase-thirdparty-3.2.0 section has a mistake > > * [HBASE-23718](https://issues.apache.org/jira/browse/HBASE-23718) | *Major* > | **[hbase-thirdparty] Update libs; pb from 3.9 to 3.11, etc.** > > gson: 2.8.5 =\> 2.8.6 > guava: 28.1-jre =\> 28.2-jre > error\_prone: 2.3.3 =\> 2.3.4 > netty: 4.1.42.Final =\> 4.1.44.Final > protobuf: 3.9.2 =\> 3.11.1 > maven-assembly-plugin: 3.1.1 =\> 3.2.0 > > > Actually we reverted gson back to 2.8.5, and now the release note on jira > is > > guava: 28.1-jre => 28.2-jre > error_prone: 2.3.3 => 2.3.4 > netty: 4.1.42.Final => 4.1.44.Final > protobuf: 3.9.2 => 3.11.1 > maven-assembly-plugin: 3.1.1 => 3.2.0 > > > Peter Somogyi 于2020年4月25日周六 下午10:58写道： > >> Please vote on this Apache hbase thirdparty release candidate, >> hbase-thirdparty-3.3.0RC0 >> >> The VOTE will remain open for at least 72 hours. >> >> [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 >> [ ] -1 Do not release this package because ... >> >> The tag to be voted on is 3.3.0RC0: >> >> https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 >> >> The release files, including signatures, digests, as well as CHANGES.md >> and RELEASENOTES.md included in this RC can be found at: >> >> https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ >> >> Maven artifacts are available in a staging repository at: >> >> https://repository.apache.org/content/repositories/orgapachehbase-1388/ >> >> Artifacts were signed with the psomo...@apache.org key which can be found >> in: >> >> https://dist.apache.org/repos/dist/release/hbase/KEYS >> >> To learn more about apache hbase thirdparty, please see >> http://hbase.apache.org/ >> >> Thanks, >> Your HBase Release Manager >> >
[jira] [Resolved] (HBASE-24267) Add limit support for scan in rest api
[ https://issues.apache.org/jira/browse/HBASE-24267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wellington Chevreuil resolved HBASE-24267. -- Resolution: Fixed Thanks for the contribution [~Qi Zhu], had merged it into master branch. Since this changes the REST API, I don;t think we should backport it to previous versions. > Add limit support for scan in rest api > -- > > Key: HBASE-24267 > URL: https://issues.apache.org/jira/browse/HBASE-24267 > Project: HBase > Issue Type: New Feature >Affects Versions: 3.0.0 >Reporter: zhuqi >Assignee: zhuqi >Priority: Major > Fix For: 3.0.0 > > > rest scan api currently does not support limit. > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (HBASE-24275) shell命令扫描无法使用
lacsar created HBASE-24275:
--
Summary: shell命令扫描无法使用
Key: HBASE-24275
URL: https://issues.apache.org/jira/browse/HBASE-24275
Project: HBase
Issue Type: Bug
Components: shell
Affects Versions: 1.2.1
Environment: hbase(main):001:0> scan
'bill_2_20200216',\{LIMIT=>1,COLUMN=>['info:content:(org.apache.hadoop.hbase.util.Bytes).toString']}
ROW COLUMN+CELL
18675205573_200A9992000603031_1 column=info:content, timestamp=1584028631493,
value=\xE4\xB8\xBB\xE4\xBB\xBB\xEF\xBC\x8C\xE6\x82
_021623344100823069
\xA8\xE5\xA5\xBD\xE3\x80\x82\xE6\x82\xA8\xE6\x98\x8E\xE5\xA4\xA9\xEF\xBC\x882\xE6\x9C\x8817\xE6\
x97\xA5\xE6\x98\x9F\xE6\x9C\x9F\xE4\xB8\x80\xEF\xBC\x89\xE4\xB8\x8A\xE5\x8D\x88\xE7\x9A\x84\xE8\
xA1\x8C\xE7\xA8\x8B\xE5\xAE\x89\xE6\x8E\x92\xE5\xA6\x82\xE4\xB8\x8B\xEF\xBC\x9A\x0A9:30\xE6\x97\
xB6\xEF\xBC\x8C\xE5\x9C\xA8\xE5\xB8\x82\xE5\x95\x86\xE5\x8A\xA1\xE5\xB1\x805\xE6\xA5\xBC\xE5\xA4
\xA7\xE4\xBC\x9A\xE8\xAE\xAE\xE5\xAE\xA4\xEF\xBC\x8C\xE6\x94\xB6\xE5\x90\xAC\xE6\x94\xB6\xE7\x9C
\x8B\xE7\x9C\x81\xE6\x8E\xA8\xE8\xBF\x9B\xE5\xA4\x96\xE8\xB4\xB8\xE4\xBC\x81\xE4\xB8\x9A\xE5\xA4
\x8D\xE5\xB7\xA5\xE5\xA4\x8D\xE4\xBA\xA7\xE4\xBC\x9A\xE8\xAE\xAE\xE6\x9A\xA8\xE5\xA4\x96\xE8\xB4
\xB8\xE5\xBD\xA2\xE5\x8A\xBF\xE7\xA0\x94\xE5\x88\xA4\xE4\xBC\x9A\xE3\x80\x82\x0A\xE8\xAF\xB7\xE6
\x82\xA8\xE7\x9F\xA5\xE6\x82\x89\xE5\xB9\xB6\xE5\x8F\x82\xE5\x8A\xA0\xEF\xBC\x8C\xE8\xB0\xA2\xE8
\xB0\xA2\xE3\x80\x82\xEF\xBC\x88\xE8\x81\x94\xE7\xB3\xBB\xE4\xBA\xBA\xEF\xBC\x9A\xE6\x9D\xA8\xE4
\xBC\x9F\xE5\xBC\xBA\xEF\xBC\x8C\xE8\x81\x94\xE7\xB3\xBB\xE7\x94\xB5\xE8\xAF\x9D\xEF\xBC\x9A1831
8286014\xEF\xBC\x89
1 row(s) in 0.4480 seconds
hbase(main):002:0> get
'bill_2_20200216','910010_13436291012_1_021617402200563234','info:content:toString'
COLUMN CELL
0 row(s) in 0.0610 seconds
hbase(main):003:0> get
'bill_2_20200216','18675205573_200A9992000603031_1_021623344100823069','info:content:toString'
COLUMN CELL
0 row(s) in 0.0170 seconds
hbase(main):004:0> get 'bill_2_20200216','
18675205573_200A9992000603031_1_021623344100823069','info:content:toString'
COLUMN CELL
info:content timestamp=1584028631493, value=主任，您好。您明天（2月17日星期一）上午的行
安排如下：
9:30时，在市商务局5楼大会议室，收听收看省推进外贸企业
工复产会议暨外贸形势研判会。
请您知悉并参加，谢谢。（联系人：杨
¼强，联系电话：18318286014）
Reporter: lacsar
在shell命令行查询字段值的时候想将byte转为string，用scan命令查询后没有效果，结果还是byte，但是get命令可以转为string
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Re: [VOTE] Please vote on the first hbase-thirdparty-3.3.0 release candidate
The release note of the hbase-thirdparty-3.2.0 section has a mistake * [HBASE-23718](https://issues.apache.org/jira/browse/HBASE-23718) | *Major* | **[hbase-thirdparty] Update libs; pb from 3.9 to 3.11, etc.** gson: 2.8.5 =\> 2.8.6 guava: 28.1-jre =\> 28.2-jre error\_prone: 2.3.3 =\> 2.3.4 netty: 4.1.42.Final =\> 4.1.44.Final protobuf: 3.9.2 =\> 3.11.1 maven-assembly-plugin: 3.1.1 =\> 3.2.0 Actually we reverted gson back to 2.8.5, and now the release note on jira is guava: 28.1-jre => 28.2-jre error_prone: 2.3.3 => 2.3.4 netty: 4.1.42.Final => 4.1.44.Final protobuf: 3.9.2 => 3.11.1 maven-assembly-plugin: 3.1.1 => 3.2.0 Peter Somogyi 于2020年4月25日周六 下午10:58写道： > Please vote on this Apache hbase thirdparty release candidate, > hbase-thirdparty-3.3.0RC0 > > The VOTE will remain open for at least 72 hours. > > [ ] +1 Release this package as Apache hbase thirdparty 3.3.0 > [ ] -1 Do not release this package because ... > > The tag to be voted on is 3.3.0RC0: > > https://github.com/apache/hbase-thirdparty/tree/3.3.0RC0 > > The release files, including signatures, digests, as well as CHANGES.md > and RELEASENOTES.md included in this RC can be found at: > > https://dist.apache.org/repos/dist/dev/hbase/3.3.0RC0/ > > Maven artifacts are available in a staging repository at: > > https://repository.apache.org/content/repositories/orgapachehbase-1388/ > > Artifacts were signed with the psomo...@apache.org key which can be found > in: > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > To learn more about apache hbase thirdparty, please see > http://hbase.apache.org/ > > Thanks, > Your HBase Release Manager >
Re: DISCUSS: Move hbase-thrift and hbase-rest out of core to hbase-connectors project?
I think we only need to depend on hbase-client for hbase-rest and hbase-thrift? No? Sean Busbey 于2020年4月28日周二 下午1:44写道： > Can't we adjust the REST server to not need YARN? > > On Mon, Apr 27, 2020 at 5:21 PM Josh Elser wrote: > > > I'd think we'd want to approach that the other way around. Shade what > > Jersey we need for REST, and (continue to) let Hadoop run wild. > > > > Locking ourselves to specific upstream YARN jars worries me. > > > > On 4/27/20 5:05 PM, Nick Dimiduk wrote: > > > I suppose an alternative is to provide a shaded version of the YARN > jars > > > needed by hbase-rest in hbase-thirdparty. We'd need these for both > > hadoop2 > > > and hadoop3, to pull them in via profile, and to exclude the originals > > > wherever they appear as transitive deps (though they shouldn't, right?) > > > > > > On Mon, Apr 27, 2020 at 11:24 AM Josh Elser wrote: > > > > > >> > > >> > > >> On 4/27/20 1:52 PM, Nick Dimiduk wrote: > > >>> On Mon, Apr 27, 2020 at 10:11 Stack wrote: > > >>> > > On Mon, Apr 27, 2020 at 9:44 AM Josh Elser > wrote: > > > > > +1 to the idea, -0 to the implied execution > > > > > > I agree hbase-connectors is a better place for REST and thrift, > long > > term. > > > My concern is that I read this thread as suggesting: > > > > > > 1. Remove rest/thrift from 2.3 > > > 1a. Proceed with 2.3.0 rc's > > > 2. Add rest/thrift to hbase-connectors > > > ... > > > n. Release hbase-connectors > > > > > > I'm not a fan of removing anything which was previously there until > > > there is are new releases and documentation to tell me how to do > it. > > >> I'm > > > still trying to help dig out another project who did the 'remove > and > > > then migrate" and left a pile of busted. > > > > > > If that's not what you were suggesting, let me shirk back into the > > > shadows;) > > > > > > > Ha ha. Not what I was suggesting but that could for sure happen. > > > > S > > > > P.S. I'm having trouble w/ REST jersey1 vs jersey2 vs Hadoop3 > > transitive > > includes++. Thrift has sporadic test failures that seem inherent to > > >> thrift > > rather of our manufacture. The discussion here was provoked by a > > >> daydream > > that bringing forward this inevitable migration of REST+thrift would > > 'solve' my immediate pain. Wasn't giving too much mind to the amount > > of > > work needed on the other side. > > >>> > > >>> I’m not clear on how moving the module out will resolve the class > path > > >>> issues. Whether it’s built from the main repo or from the side repo, > > >> yarn’s > > >>> transitive hull is still present... > > >>> > > >> > > >> Yeah, understandable :) > > >> > > >> I think working with "something" for REST/Thrift in connectors (punt > on > > >> H3 to start?) is reasonable. You shouldn't be stuck with the baggage > of > > >> Jersey dependencies if that's not the problem you're trying to solve. > > >> > > > > > >
