regression here.
Should we make sure that we test against the same Hadoop version that
was
used for vetting 0.3.0 when we are testing a patch for that release?
Not sure what our policy should be in that regard.
On Fri, Nov 8, 2013 at 3:26 PM, Kevin Minder
<[email protected]>wrote:
Hi Everyone,
I hit the error below when running the samples/ExampleHBase.groovy with
0.3.1. Everything else I tried checked out fine but I did not run Hive
sample.
Maksim & Vladimir,
Can you check out HBase and Hive in 0.3.1.
Inserting data into table...
Caught: org.apache.hadoop.gateway.shell.HadoopException:
org.apache.hadoop.gateway.shell.ErrorResponse: HTTP/1.1 400 Bad
Request
org.apache.hadoop.gateway.shell.HadoopException:
org.apache.hadoop.gateway.shell.ErrorResponse: HTTP/1.1 400 Bad
Request
at org.apache.hadoop.gateway.shell.AbstractRequest.now(
AbstractRequest.java:72)
at org.apache.hadoop.gateway.shell.AbstractRequest$now.
call(Unknown
Source)
at org.apache.hadoop.gateway.shell.hbase.ExampleHBase.run(
ExampleHBase.groovy:81)
at org.apache.hadoop.gateway.shell.Shell.main(Shell.java:40)
at org.apache.hadoop.gateway.launcher.Invoker.
invokeMainMethod(Invoker.java:64)
at
org.apache.hadoop.gateway.launcher.Invoker.invoke(Invoker.java:37)
at org.apache.hadoop.gateway.launcher.Command.run(Command.
java:101)
at
org.apache.hadoop.gateway.launcher.Launcher.run(Launcher.java:70)
at
org.apache.hadoop.gateway.launcher.Launcher.main(Launcher.java:49)
Caused by: org.apache.hadoop.gateway.shell.ErrorResponse: HTTP/1.1 400
Bad Request
at
org.apache.hadoop.gateway.shell.Hadoop.executeNow(Hadoop.java:107)
at org.apache.hadoop.gateway.shell.AbstractRequest.execute(
AbstractRequest.java:47)
at org.apache.hadoop.gateway.shell.hbase.table.row.
StoreRow$Request.access$400(StoreRow.java:47)
at org.apache.hadoop.gateway.shell.hbase.table.row.
StoreRow$Request$1.call(StoreRow.java:116)
at org.apache.hadoop.gateway.shell.hbase.table.row.
StoreRow$Request$1.call(StoreRow.java:77)
at org.apache.hadoop.gateway.shell.AbstractRequest.now(
AbstractRequest.java:70)
... 8 more
On 11/7/13 10:12 AM, larry mccay wrote:
Hi Everyone,
A candidate for the Apache Knox (Incubator) 0.3.1 release is available
at:
https://dist.apache.org/repos/dist/dev/incubator/knox/knox-
incubating-0.3.1/
The release candidate is a zip archive of the sources in:
https://git-wip-us.apache.org/repos/asf/incubator-knox.git
Branch v0.3.1 (git checkout -b v0.3.1)
The SHA1 checksum of the archive
is cc998fefbb1bf7c683cdd9e82e8f3527d1fe5792.
Please vote on releasing this package as Apache Knox (Incubator)
0.3.1.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Apache Knox (Incubator) PMC votes are cast.
We have a single bug fix in this patch release candidate.
The fix is for an issue that would adversely affect a load balanced
cluster
of Knox Gateway instances and therefore an issue for HA deployment
scenarios.
There are no known outstanding functional issues. Please test as much
as
possible within this 72 hour period and cast your vote.
[ ] +1 Release this package as Apache Knox (Incubator) 0.3.1
[ ] -1 Do not release this package because...
Thanks!
--larry
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or
entity
to which it is addressed and may contain information that is
confidential,
privileged and exempt from disclosure under applicable law. If the
reader
of this message is not the intended recipient, you are hereby notified
that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender
immediately
and delete it from your system. Thank You.
--