Set encoding and blooms on meta as default. Also shutdown access to the
initial meta schema creating method; get from TableDescriptors if you
need access to schema or edit it as you would any other table if you
want to edit it.
`CallDroppedException` can be thrown with `CallRunner.drop()` by queue implementations that decide to drop calls to groom the RPC call backlog. The LifoCoDel queue does this I believe and with Pluggable queue it's possible for 3rd party queue implementations to be using `drop()` for similar reasons. It would be nice for the server to be tracking these exceptions in metrics since otherwise you might have to do some extra lifting on the client side.
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Reviewed-by: Bryan Beaudreault <bbeaudreault@hubspot.com>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Josh Elser <elserj@apache.org>
(Re-application of HBASE-26147 with the correct author metadata)
Adds an upstream caller to the RequestHeader of hbase requests, and makes that available in RpcCallContext
One can inject an upstream caller by setting the conf `hbase.upstream.caller.impl` to a fully qualified class name of a class with a public constructor that implements `org.apache.hadoop.hbase.ipc.UpstreamCaller`
Upstream callers will be available via `RpcCallContext#getUpstreamCaller` or `RpcCallContext#getRequestUserName`. The latter combines the real username and upstream caller to create a fully qualified name like `<upstreamCaller>.via.<user>`
- Our branch version munging script set-maven-versions can't parse the pom.xml due to unicode, remove it.
- Our build adds build.json files to the jars. Allowlist those files in jar content verification.
We could potentially try to upstream generic versions changes of these at some point
This uses our standard buildpack, but each module must get a custom .blazar.yaml to pass in required
properties to the build. One can distribute that .blazar.yaml using build-scripts/copy_blazar_yaml.sh.
In order to minimize the duplication, most of the customizations are consolidated in
build-scripts/prepare_environment.sh.
The RPM build is hooked into the standard build hbase-assembly, as a post-build step. The RPM build
scripts in hbase-assembly/rpm-build handle turning the assembled tar.gz into multiple RPMs. We required
some minor changes to the descriptor in hbase-assembly to account for the fact that our build processes
each module independently instead of as a single reactor build. As a result, moduleSet does not work, so
moduleSet usages were converted to dependencySet.
Signed-off-by: Andrew Purtell <apurtell@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Conflicts:
hbase-mapreduce/src/test/java/org/apache/hadoop/hbase/mapreduce/TestWALRecordReader.java
Our logs have as a fairly common occurrence: 2021-03-05 22:24:31,034 WARN
[StoreFileOpener-foo-1] hfile.BlockCacheUtil: Caching an already cached
block: blah.bub. This is harmless and can happen in rare cases (see HBASE-8547)
Because it is harmless, log at DEBUG level, not WARN.
Signed-off-by: Baiqiang Zhao <zhaobaiqiang@apache.org>
Signed-off-by: Duo Zhang <zhangduo@apache.org>
Signed-off-by: Viraj Jasani <vjasani@apache.org>
Reviewed-by: Rushabh Shah <rushabh.shah@salesforce.com>
Bryan Beaudreault
Xiaolin Ha
Michael Stack
Baiqiang Zhao
Wei-Chiu Chuang
Charles Connell
Charles Connell
Bri Augenreich
Briana Augenreich
chenglei
Richard Marscher
Bryan Beaudreault
Richard Marscher
GeorryHuang
Duo Zhang
richardantal
clarax
Andrew Purtell
Rushabh Shah
XinSun
bitterfox
keyserbrian1
Pankaj