Hi Hari and Venkat,
I'm excited to hear that you are both interested in becoming Release managers.
Whereas previous experience with doing release might be helpful, it's
definitely not a requirement. I believe that one of the main reasons for
driving release this way is to help the community
Hi Jarcec
Thanks for the thoughtful comments. I think it would be good for someone with
RM experience to work on the release management tasks for something like a
1.4.3 release as there is a large installed base of customers. I believe that
will make the release smoother.
While I can
Hi guys,
Thanks for giving me this opportunity. I'd definitely like to do Sqoop 1.4.3. I
would also gladly help Venkatesan if he would want to be the RM for Sqoop
1.99.2 (if the Sqoop PMC agrees, of course).
Thanks
Hari
--
Hari Shreedharan
On Monday, February 4, 2013 at 4:09 PM,
Thanks Hari.Thanks for agreeing to do this release management work
Venkat
Date: Mon, 4 Feb 2013 16:34:34 -0800
From: hshreedha...@cloudera.com
To: dev@sqoop.apache.org
Subject: Re: Release planning for 1.4.3
Hi guys,
Thanks for giving me this opportunity. I'd definitely like to do
David Robson created SQOOP-862:
--
Summary: Hbase import fails if there is a row where all columns
are null
Key: SQOOP-862
URL: https://issues.apache.org/jira/browse/SQOOP-862
Project: Sqoop
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/9300/
---
Review request for Sqoop.
Description
---
Added defensive code to skip the
[
https://issues.apache.org/jira/browse/SQOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Robson updated SQOOP-862:
---
Attachment: SQOOP-862.patch
Hbase import fails if there is a row where all columns are null
[
https://issues.apache.org/jira/browse/SQOOP-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571013#comment-13571013
]
David Robson commented on SQOOP-862:
Added defensive code to skip the HBase put and
