-1 on 0.3.1 RC2 due to HBase 0.96 compatibility issue.
On 11/11/13 9:59 AM, Kevin Minder wrote:
I filed KNOX-199. On 11/11/13 9:47 AM, Vladimir Tkhir wrote:Empty column qualifier syntax: 0.95: family1: and family1 0.96: family1: Currently if column name is empty HBase DSL produces family name without colon . It should be updated to generate family qualifier with colon in such cases.If fix for this will be included in 0.3.1 than Knox will support HBase 0.94and later. Should I fill jira for this? Thanks, VladimirOn Mon, Nov 11, 2013 at 4:24 PM, Vladimir Tkhir <[email protected]>wrote:I'm trying to check reverse compatibility for this issue now. Already haveDSL fix for a 0.96. Ideally fix should work in 0.95 and later versions. Will provide the details soon.Also noticed that name of example script in book is outdated. In book itis ExampleHBaseUseCase.groovy in distribution ExampleHBase.groovy On Mon, Nov 11, 2013 at 4:17 PM, Kevin Minder < [email protected]> wrote:Vladimir,Is the fix straight forward such that it could be created quickly? If so I personally would like to include it in 0.3.1 and therefore this would require another RC. We should also update the user's guide to indicate that Knox works with HBase 0.96 and not 0.95. I'm holding off on my votefor now. Kevin. On 11/11/13 9:09 AM, Vladimir Tkhir wrote:Issue is in HBase client DSL code. HBase groovy example on Knox 0.3.0 also fails on Sandbox GA. In https://issues.apache.org/jira/browse/HBASE-9549 syntax for empty column qualifiers was updated. In Sandbox Beta HBase 0.95 was used. In Sandbox GA it was updated to 0.96. So client HBase DSL should be updated to address this change. On Mon, Nov 11, 2013 at 3:51 PM, Kevin Minder <[email protected]>wrote: I don't understand this perspective. Any new user that attempts todownload and try Knox will, as our user's guide documents, use Sandbox2 GA. If this won't be solved in 0.3.1 then will we quickly work towards a 0.3.2? On 11/8/13 8:53 PM, larry mccay wrote:I just tested with 0.3.1 with Sandbox 2 Beta - which is what I tested0.3.0 with and it works fine. In my mind, this is sufficient when releasing a patch release. Do we want to consider whether we want it to be compatible with the 2.0 GA Sandbox?It seems possible that the REST API has been changed for HBase since0.3.0 was release. On Fri, Nov 8, 2013 at 5:38 PM, Kevin Minder <[email protected]>wrote: I did the same testing with 0.3.0 and did not see this error.There were other intermittent errors that did require HBase restartbut I was always able to get a full run.HBase could have changed between Sandbox 2.0 BETA when I did my 0.3.0testing and now with Sandbox 2.0 GA. On 11/8/13 5:06 PM, larry mccay wrote:Was there an issue with sandbox that made us have to restart HBaseafterlaunch? On Fri, Nov 8, 2013 at 4:58 PM, Dilli Arumugam < [email protected] wrote:I have seen the HBase problem in the trunk as well.ThanksDilliOn Fri, Nov 8, 2013 at 1:08 PM, larry mccay <[email protected]>wrote: I have to assume that this is related to testing against a different Hadoop deployment than testing for previous release.There is no way that the one line change made in that commit couldcause aregression here.Should we make sure that we test against the same Hadoop versionNOTICE: This message is intended for the use of the individual orthat 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.groovyat org.apache.hadoop.gateway.launcher.Command.run(Command.with0.3.1. Everything else I tried checked out fine but I did not runHive 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 BadRequest org.apache.hadoop.gateway.shell.HadoopException:org.apache.hadoop.gateway.shell.ErrorResponse: HTTP/1.1 400 BadRequestat 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)java:101)at org.apache.hadoop.gateway.launcher.Launcher.run( Launcher.java:70)atorg.apache.hadoop.gateway.launcher.Launcher.main(Launcher.java:49) Caused by: org.apache.hadoop.gateway.shell.ErrorResponse: HTTP/1.1400 Bad Requestat org.apache.hadoop.gateway.shell.AbstractRequest.execute(at org.apache.hadoop.gateway.shell.Hadoop.executeNow( Hadoop.java:107)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 isavailable at:https://dist.apache.org/repos/dist/dev/incubator/knox/knox- incubating-0.3.1/The vote is open for the next 72 hours and passes if a majorityThe 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.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 asmuch aspossible within this 72 hour period and cast your vote.[ ] +1 Release this package as Apache Knox (Incubator) 0.3.1NOTICE: This message is intended for the use of the individual or[ ] -1 Do not release this package because... Thanks! --larry -- CONFIDENTIALITY NOTICEentityto which it is addressed and may contain information that is confidential,privileged and exempt from disclosure under applicable law. Ifthereaderof this message is not the intended recipient, you are hereby notified thatany printing, copying, dissemination, distribution, disclosure orforwarding of this communication is strictly prohibited. If youhavereceived this communication in error, please contact the senderimmediatelyand delete it from your system. Thank You.-- CONFIDENTIALITY NOTICEentity to which it is addressed and may contain information that is confidential,privileged and exempt from disclosure under applicable law. If thereader of this message is not the intended recipient, you are hereby notified thatany printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you havereceived this communication in error, please contact the sender immediately and delete it from your system. Thank You. --CONFIDENTIALITY NOTICENOTICE: 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 readerof this message is not the intended recipient, you are hereby notifiedthat any printing, copying, dissemination, distribution, disclosure orforwarding of this communication is strictly prohibited. If you havereceived this communication in error, please contact the sender immediately and delete it from your system. Thank You. --CONFIDENTIALITY NOTICENOTICE: This message is intended for the use of the individual or entityto which it is addressed and may contain information that is confidential, privileged and exempt from disclosure under applicable law. If the readerof this message is not the intended recipient, you are hereby notifiedthat 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.-- CONFIDENTIALITY NOTICENOTICE: 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 thatany printing, copying, dissemination, distribution, disclosure or forwarding of this communication is strictly prohibited. If you havereceived this communication in error, please contact the sender immediatelyand delete it from your system. Thank You.
-- CONFIDENTIALITY NOTICENOTICE: 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.
