sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Venkat Ranganathan <vranganat...@hortonworks.com>
Subject Re: [VOTE] Include High Performance Oracle Connector in Sqoop
Date Sat, 25 Jan 2014 05:21:13 GMT
+1

Thanks
Venkat


On Fri, Jan 24, 2014 at 5:12 PM, Abhijeet Gaikwad <abygaikwad17@gmail.com>wrote:

> +1
>
> Best Regards,
> Abhijeet
>
>
> On 1/24/2014 6:18 PM, Jarek Jarcec Cecho wrote:
>
>> +1!
>>
>> Jarcec
>>
>> On Fri, Jan 24, 2014 at 04:06:10PM -0800, Kathleen Ting wrote:
>>
>>> +1
>>>
>>> Thanks David and Jarcec! The OraOop Connector will be a momentous
>>> addition to the Apache Sqoop codebase.
>>>
>>> On Fri, Jan 24, 2014 at 3:45 PM, Hari Shreedharan
>>> <hshreedharan@cloudera.com> wrote:
>>>
>>>> +1.
>>>>
>>>> I am unsure why a vote is required for a code contribution - really
>>>> just having it attached to a jira, and a committer pushing it should be
>>>> enough. Either way, a big +1!
>>>>
>>>>
>>>> Thanks,
>>>> Hari
>>>>
>>>>
>>>> On Friday, January 24, 2014 at 3:38 PM, David Robson wrote:
>>>>
>>>>  Based on the recent discussion this is a vote thread to determine if
>>>>> we should include the Oracle connector into the core Sqoop code. I will
be
>>>>> doing the bulk of the work to migrate it into the Sqoop codebase - and
>>>>> Jarcec has said he will assist me where required.
>>>>>
>>>>> Please vote
>>>>>
>>>>> [] +1 Yes - Oracle connector code should be moved into Sqoop code
>>>>> [] +0 Abstain - I don't have a preference
>>>>> [] -1 No - Oracle connector should remain separate from Sqoop
>>>>>
>>>>>
>>>>>
>>>>
>

-- 
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.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message